Use this guide when events from a TimelinesAI webhook don't reach your system, or when you get a webhook warning email. In most cases the problem is on the receiving side: the endpoint URL, the tool behind it or its server. For setup and the list of events, see Webhooks Integration on TimelinesAI.
How webhook delivery works
Each event is sent as an HTTP POST request with a JSON body to your endpoint URL.
A call is successful when your endpoint replies with a 2xx status (for example, 200) within 5 seconds. A slower reply is cut off and counted as failed.
If your endpoint replies with 429 or a 5xx error, TimelinesAI tries again up to 2 more times within a few seconds. Other errors and timeouts are not retried, so that event is not sent again.
Requests are sent without authentication or custom headers, so your endpoint must accept them as they are.
No events are sent from a deactivated endpoint or from a workspace on an unpaid plan.
Signs that a webhook has a problem
Data is missing in your system. For example, WhatsApp messages appear in TimelinesAI but not in your CRM or spreadsheet.
You got a warning. Workspace owners and admins get an email and an in-app notification when an endpoint keeps failing.
The Webhooks page shows errors. The Error rate is above 0% or the Last response is not a 2xx status.
When you get a warning
TimelinesAI warns you when an endpoint:
fails 5 times in a row, or
fails in 30% or more of its last 50 calls, or
takes longer than 5 seconds in 40% or more of its last 50 calls.
The warning names the reason, the endpoint URL and the event type.
Note: TimelinesAI doesn't disable the endpoint. It stays active and events keep being sent to it. Fix the endpoint, or deactivate it if you no longer need it.
How to find the cause
Open Integrations → Webhooks.
Find the endpoint and check its Error rate and Last response.
Click Download Log next to it. The log lists the latest calls, the response code your endpoint returned, how long it took and what it replied.
Match the response code with the list below.
Common errors
404 Not Found: the URL is wrong or no longer exists, for example the Make scenario or Zap was deleted. Copy a fresh webhook URL from your tool and paste it into the endpoint with Edit.
401 or 403: the endpoint requires a login, token or header. TimelinesAI can't send those, so use a URL that accepts requests without authentication.
429 Too Many Requests: your system limits how many requests it accepts. Raise the limit on the receiving side.
5xx (500, 502, 503…): the receiving server had an error or was down. Check that system or ask its provider.
Response code 0 or a timeout: no reply within 5 seconds, or the server couldn't be reached. Make sure the server is online and replies right away. If it needs more time, it should reply first and process the data afterwards.
Make, Zapier or other tools: make sure the scenario or Zap is turned on and still uses the same webhook URL.
What to do next
Fix the issue on the receiving side, or contact its provider (your CRM vendor, automation tool or server admin) and share the error from the log.
If you no longer need the endpoint, deactivate or delete it to stop the warnings.
Still stuck? Contact TimelinesAI support with the endpoint URL, the event type and the downloaded log.
Tip: after a fix, trigger the event once (for example, send a test message) and check that Last response shows a 2xx status.