I’m facing an issue where my webhook stops listening after processing data just once. My goal is for it to stay active continuously for real-time data capture.
Steps Tried:
Initially set up the webhook; it works for the first data trigger.
Reviewed module configurations for any obvious misconfigurations.
Problem:
The webhook becomes unresponsive after the first trigger without any error messages.
Request:
Any suggestions on how to keep the webhook active continuously?
Are there settings or adjustments within Make.com that I might be missing?
Hi @Carlo
If you could specify what the trigger is, we can provide further assistance. If you are using the webhook to monitor responses from a Google Form, there is a module available for tracking form submissions.
This is solved: the webhook does not have a visual clue that it’s running if the scenario is just always on.
The visual clue for the webhook running, as seen in the picture, is irrelevant for the status of the scenario. I just activated the scenario and then sent data to the webhook, and it works even tho there is no wheel spinning.