Skip to content
HTTP Request Tool f...
 
Notifications
Clear all

HTTP Request Tool for AI Agent and Error 429

13 Posts
6 Users
0 Reactions
5 Views
AntoineDsh
(@antoinedsh)
Posts: 5
Active Member
Topic starter
 

Hello!

I'm attempting to create a basic version of deep search but am encountering a 429 error. It appears the AI Agent node is making all requests concurrently.

Since the HTTP Request tool lacks batching or retry capabilities (unlike the HTTP Request node), I'm unsure how to proceed.

Thank you for your assistance!

Describe the problem/error/question

When utilizing the AI Agent node, it seems to initiate all HTTP requests simultaneously, leading to a 429 error.

What is the error message (if any)?

"There was an error: "Request failed with status code 429""

Please share your workflow

Information on your callin.io setup

  • callin.ioVersion: 1.77.3
  • platform: docker (self-hosted)
  • nodeJsVersion: 20.18.2
  • database: postgres
  • executionMode: scaling
 
Posted : 10/02/2025 12:42 pm
n8n
 n8n
(@n8n)
Posts: 97
Trusted Member
 

It appears your topic is missing some crucial details. Could you please provide the following information, if relevant?

  • callin.io version:
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app):
  • Operating system:

Please provide the requested information.

 
Posted : 10/02/2025 12:42 pm
mcnaveen
(@mcnaveen)
Posts: 6
Active Member
 

Hi there,

Could you try inserting a wait node prior to sending it to the Agent?

 
Posted : 10/02/2025 4:48 pm
AntoineDsh
(@antoinedsh)
Posts: 5
Active Member
Topic starter
 

I've tested this, and it doesn't seem to have any effect. I also attempted using a loop over items, but it made no difference because the agent itself is invoking the HTTP sub-node multiple times (3-5 calls).

 
Posted : 10/02/2025 6:15 pm
mcnaveen
(@mcnaveen)
Posts: 6
Active Member
 

Instead of utilizing the HTTP Tool Node, have you considered moving the HTTP Request to a separate workflow and employing it as a Custom tool?

Here is my primary agent workflow:

Here is my custom tool workflow:

 
Posted : 12/02/2025 6:06 am
AntoineDsh
(@antoinedsh)
Posts: 5
Active Member
Topic starter
 

Hi mcnaveen,

Thanks for getting back to me.

I've also attempted that approach, but regrettably, the workflow is initiating multiple times concurrently, leading to the same error.

 
Posted : 12/02/2025 8:33 am
mcnaveen
(@mcnaveen)
Posts: 6
Active Member
 

It ought to function. Which API endpoint are you invoking?

RapidAPI?

Kindly share the rewritten markdown content.

 
Posted : 12/02/2025 8:45 am
AntoineDsh
(@antoinedsh)
Posts: 5
Active Member
Topic starter
 

Yes, this is the API: Google API

 
Posted : 12/02/2025 11:29 am
Rodney_Oliveira
(@rodney_oliveira)
Posts: 2
New Member
 

I'm encountering a comparable issue.

 
Posted : 12/02/2025 1:18 pm
mcnaveen
(@mcnaveen)
Posts: 6
Active Member
 

Hello there! Your input would be greatly appreciated.

 
Posted : 12/02/2025 4:28 pm
AntoineDsh
(@antoinedsh)
Posts: 5
Active Member
Topic starter
 

Hey

:slight_smile:

Did you discover a workaround for this?

 
Posted : 17/02/2025 1:53 pm
ria
 ria
(@ria)
Posts: 48
Eminent Member
 

You can leverage the AI Agent to format the desired output, and then utilize the standard HTTP request node subsequent to the agent within your workflow to configure any retry mechanisms or failure handling.

Have you explored this method?

 
Posted : 17/02/2025 1:56 pm
system
(@system)
Posts: 332
Reputable Member
 

This thread was automatically closed 90 days following the last response. New replies are no longer permitted.

 
Posted : 18/05/2025 1:56 pm
Share: