How can I increase the timeout for an api call?

:bullseye: What is your goal?

Hi,
I am using the Claude module, and the runtime seems to be limited to one minute.
As a result, most of my API calls time out. How can I increase this duration?

:thinking: What is the problem & what have you tried?

tried to extend the time

1 Like

Hi @Davy1,

That seems odd, which endpoint are you using?

Are there any settings in the endpoint to help extend the timeout?

Unless I’m missing something, it seems like this setup will not work in this case because if one call take longer than a minute, then exact same call up to 300 seconds later is still likely to take longer than a minute to complete.

2 Likes

Yes, exactly that’s a Node issue, not a flow issue.
An alternative I considered was using the HTTP module; however, I’m running into an issue generating an API-safe request body (I need to submit an HTML).
Do you know what I could use in terms of filters to generate an API-safe body?

1 Like

Hello,

You should use a Create JSON module.

That will allow you to define fields and handle encoding for you.

Which API endpoint are you using?

Hi @Davy1 ,

This happens due to a timeout error , which occurs when the module does not receive an API response within the allowed time limit.

To handle this, you have two possible approaches:

  • You can use the HTTP module to run the Claude API and configure the Timeout option available in the Advanced settings of the HTTP module as shown in the screenshot, instead of using the native Claude module . Or,

  • You will need to manage the issue using a Break error handler in the scenario.

I’m also attaching a related thread for your reference - please review it as it explains the behavior in more detail.

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation

API timeouts in Make can be tricky because not every module lets you tweak them directly. I’ve handled slow endpoints by splitting requests, adding retries, or switching to webhooks where possible. Sometimes the real fix is optimizing the API itself, not waiting longer. If responses regularly hit the limit, that usually signals a deeper performance or design issue.