Fix a webhook that stopped sending

Your system stops getting messages from a webhookWebhook An address you give the hub so it can send your own systems a message whenever a feed post or comment changes.. If it stopped after failed deliveries, each Admin gets an email titled "Webhook Stopped:" and the webhook's address, saying its deliveries "have stopped, because two in a row failed." Integration › Webhooks shows Stopped under Active on its row.

Why it happens

• Two deliveries in a row failed. Your system couldn't be reached, didn't answer within 10 seconds, or answered with an error: a status of 400 or above. A delivery that works in between starts the count again. While the webhook is stopped nothing is sent to it, and what it misses isn't sent later.
• It's switched off. An inactive webhook gets nothing, and nobody is emailed. Its row shows No under Active.
• The change isn't one it sends. It sends only the events ticked under Events, and only for Feed posts and comments on them. Notes, tasks, forms, e-signs and events send nothing.

How to fix it

1. Go to Integration › Webhooks and choose the pencil icon, Edit webhook, on its row. A stopped webhook's window says "Deliveries stopped." and shows its Last delivery: when it was, and the status code your system answered. "no response" means your system never answered.
2. Fix the cause on your system. Check the URL, and that your server is up, accepts a POST and answers within 10 seconds with a status below 400.
3. Make sure Active is on and the events you need are ticked, then choose SAVE. Saving starts deliveries again, even with nothing changed. "Webhook saved" shows.
4. Post a short update on a case with no real clients on it, and check your system gets the message.

Messages from while it was stopped aren't sent later. To catch up on what changed, your developer can read the cases through the API; see Understand what the API can do.