HTTP Module - Error: 500 Internal Server Error

Questions
1

I am using HTTP get request module. And I have another secondary flow which catches and respond the HTTP request. The Request is simple though I am getting Error: 500 Internal Server Error sometimes. 5 out of 10 times I gives error. But it works for rest 5 request flawlessly.

And I checked the history of the flow which is catching the request that flow works everytime perfectly but there is some problem in transmission after request. HTTP module is getting in catching response again.
I hope someone can help.

Screenshot 2025-11-07 at 09.27.32
Screenshot 2025-11-07 at 09.27.32898Ă—1438 108 KB

3

Hi,

I see you want to read a Make webhook. Why do you want to use an HTTP module instead of a Make Webhook module?

Key difference is that the webhook is triggered instantly, while the HTTPs can be triggered at specific times (e.g. every 15 minutes).

500 error comes in when the webhook does not send anything, but the HTTP module runs

4

Thanks Federico,
But In my understanding there are only 2 main types of webhooks -

  1. For listening to the triggers
  2. Responding to the webhook

There is no webhook to make a request to another webhook. If so can you please elaborate which are you talking about?

Screenshot 2025-11-07 at 10.02.45
Screenshot 2025-11-07 at 10.02.45464Ă—523 24.5 KB

5

Hey, there is actually no way to “request” data to another webhook. Per se, a webhook cannot be called, it can only send data when it has something to send (an action happens on software A).

Can you please share the logic you want to create, and the software you are using?

6

I am trying to divide my main logic into small unit flows. So I can reuse those logic in other flows for flexibility. I am creating a flow A which calls another flow B. Flow B contains webhook trigger, some computations and webhook reponse. Flow A make api calls to Flow B and wait for response.

Problem is in the response transmission. Flow A get error in the HTTP module which is calling Flow B’s webhook trigger. However Flow B is working fine and successfully.
Real process is bit more complex therefore sharing small part of it!! Let me know if you need more explanation

7

That’s the thing, Flow A should catch the webhook created by Flow B when there is something, not call and endpoint via HTTP on a predetermined schedule. Hope this is clear.

If you want we can schedule a quick call to review it, here is my upwork profile: https://www.upwork.com/freelancers/federicodonati where you can book

1 Like
8

@Meet In that case you’d be better using Subscenarios.

That is specifically designed to allow reuse of scenarios as units within other scenarios.

There’s other benefits too:

  • Subscenarios can be used as Tools within Make AI Agents
  • They can be published as Tools via the Make MCP Server for use by other Agentic platforms
1 Like