Your automation was working, and now nothing arrives at your endpoint. Nothing downstream updates, and the webhook still looks correctly configured in Claap. Here is how to find out where the chain breaks, in the order that eliminates the most possibilities fastest.
Test the connection first
Before investigating anything else, fire a test event.
Go to your workspace settings, then API & Webhooks, open the Webhooks tab, click the three dots next to the webhook and choose Send test event. This sends a payload built from your last recording straight to your endpoint.
The result splits the problem in two. If the test arrives, the connection between Claap and your endpoint is fine and the issue is either with which recordings trigger events, or with what your automation does once it receives them. If the test doesn't arrive, the problem is the endpoint or the URL.
If the test event doesn't arrive
Check the URL first, character for character, especially if anything was recently redeployed. A changed path or an expired tunnel URL is the most common cause.
Then check how your endpoint answers. It has to return HTTP 200 within five seconds. If it doesn't, Claap retries immediately, then after one minute, then after five minutes, and then discards the event. An endpoint that does heavy work before responding will fail this even though the code itself is correct. Acknowledge with a 200 first, process afterwards.
If the test event arrives but real recordings don't
Then events aren't being triggered, and there are two usual reasons.
The recordings are private. Private recordings do not trigger recording_added or recording_updated at all. A recording produces events when it is accessible to workspace members and visible in global search, or sits in a folder that is. This is the single most common cause of a webhook that looks broken and isn't, and it often appears after someone changes a folder's visibility rather than after any change to the webhook.
The recording hasn't finished processing. recording_added fires only once the recording has been transcoded, transcribed and analysed. If you are testing immediately after a call ends, wait a few minutes.
Also worth confirming: the event type your automation listens for matches the one the webhook sends. A webhook registered on recording_added only will never fire when an existing recording is updated.
If events arrive but nothing changes downstream
Then Claap has done its part and the problem is inside your automation. Check the execution history in your automation tool rather than the webhook. In practice this is where multi step chains fail, because the payload arrives and a later step silently errors.
If your calls are meant to reach a third tool at the end of the chain, check that something in the chain actually forwards them. A webhook pointing at your automation platform delivers there, not to whatever sits after it.