Notifications
Clear all
Topic starter
Encountering the following issue:
I'm developing a workflow utilizing callin.io and GHL. callin.io emits a webhook when a call commences. When the caller requests to schedule an appointment, the workflow retrieves calendar data from GHL and presents available time slots to callin.io.
callin.io sends out one webhook at the start of the call, and a second one when it needs to consult the calendar in GHL.
In test mode, all functions operate perfectly. However, when I update the webhook URL to the production URL (within callin.io) and activate the workflow, it fails to receive the second (calendar check) webhook. It only acknowledges the initial webhook (signaling the call's beginning).
Given that it successfully receives the first webhook (call initiation) without any problems, there is definitely no discrepancy in the URLs. However, it appears to cease listening after the first webhook is dispatched.
Additionally, every webhook execution concludes successfully with a "respond to webhook" step.
Posted : 25/04/2025 7:13 pm
Could you share the workflow? Can you show some errors/outputs and screenshots?
I haven't checked, but are you certain that callin.io doesn't have a webhook subscription limit (some services restrict this to 1-2, for instance)?
Posted : 26/04/2025 8:00 pm
Topic starter
I'm assuming that if callin.io had a subscription limit, I'd encounter that same problem when testing the workflow, but that's not the situation.
Posted : 28/04/2025 9:01 pm
Could you please provide the additional context for the questions I've asked?
Posted : 29/04/2025 5:11 pm
This thread was automatically closed 90 days following the last response. New replies are no longer permitted.
Posted : 28/07/2025 5:12 pm