A monitor can send a JSON message to another system — your CRM, a ticketing tool, an automation platform — when it matches, triggers or clears. Add a Send a webhook action, choose its events, send a test, and follow every delivery on the monitor's Activity tab.
Updated September 24, 2026
An alert or an email tells a person. A webhook tells another system: when the monitor matches, triggers or clears, Renable sends a JSON message to an address you choose, and that system decides what to do with it. A common setup is a CRM that turns each message into a task — someone is assigned, checks the import, cleans up the data and logs their time against it.
A webhook is an action like any other, so a monitor can send one alongside an alert and an email, or on its own.
The address has a few rules, and the field says which one it breaks:
https://name:password@…). If the receiving system needs a secret, it goes in the address's path or query instead, the way most systems hand them out.# part, and it can be at most 2,048 characters.|, [ or ] that has to be percent-encoded. Renable never trims or changes the address for you, so remove the space or encode the character.Saving doesn't contact the address — Send test is how you find out whether it works.
A monitor can carry up to 10 webhooks, each with its own address and its own events — one per system you want to tell.
Each webhook sends only the events you tick. The name in small type beside each box is the event's identifier, which is what the receiving system sees:
monitor.matched) — every import, channel run or reported event where the monitor's condition holds, whether or not the monitor has just triggered. A monitor with no condition matches every one, so with this box ticked the webhook sends a message after every import or every channel run. Not offered on a scheduled check: a schedule has no run to report, and the box says "A scheduled check has no run to report, so its webhook can't send "Matched" (monitor.matched) — choose "Triggered" or "Cleared"."monitor.triggered) — the moment the monitor triggers on a catalog or channel. Once per incident, like the email: while the monitor stays triggered, nothing more is sent.monitor.cleared) — the moment the monitor clears again on that catalog or channel.Which to pick depends on what the other side does with them:
If the webhook is all you want, leave Raise an alert off. A monitor with no condition and an alert would otherwise show as needing attention on every catalog or channel it watches, for as long as it runs.
Send test appears beside the address once the address is valid. It works on what's on the page right now — you don't need to publish first.
"test": true, and sends it once.The result shows Delivered or Failed, the HTTP status the address answered with and how long it took, the Response the receiving system sent back, and under Payload sent the exact message. A test is sent once and never retried, and tests don't show on the Activity tab. You can send up to 10 tests a minute across your organization.
Tip: No receiving system yet, or want to see exactly what Renable sends before you connect your CRM? Open webhook.site — it gives you a free, temporary https address and shows every request it receives. Paste that address into Webhook address, press Send test, and read the message and its headers there. Swap in your real address once you're done — anyone who has the webhook.site address can read what it receives.
Each event goes to each webhook that subscribes to it as one HTTPS POST with a JSON body. The message says what happened (monitor.triggered and so on), which monitor, organization and project it's about, the catalog or channel with a link to it, the import or channel run with its status and counts, and the values the monitor observed. The field-by-field description is in the Monitor webhook payload reference — hand it to whoever sets up the receiving side.
A delivery counts as done when the address answers with a 2xx status. If it can't be reached, doesn't answer within 10 seconds, or answers with a 5xx, 408 or 429 status, Renable tries again, waiting longer each time, for about an hour. Some answers can't be fixed by trying again, so they fail at once: any other 4xx status (a 404 usually means the address is wrong, a 401 or 403 that its token is), a redirect, and an address that points into a private network.
When a delivery fails for good, the monitor raises an Error alert saying the webhook delivery failed and why. It shows on the dashboard and on the monitor's Alerts tab. There's one such alert per webhook, whatever the number of failures — two webhooks to the same service, such as two Slack channels, each get their own — and it clears on its own as soon as a delivery to that webhook succeeds again. It never holds a publish, and it never marks a catalog or channel as needing attention: it's about the webhook, not about your data.
A failing webhook doesn't make the monitor Triggered — that's still about its condition. The monitor's card on the Monitoring page turns red and adds webhook delivery failing. The status line on the monitor also names the webhook and its last answer — "hooks.slack.com · webhook 2 answered 503 after 8 attempts", or "could not be reached" — beside whatever the condition says, All clear included. webhook 2 is the webhook's place among the monitor's Send a webhook actions on the Rule tab.
The monitor's Activity tab lists what the monitor did, newest first: each time it matched, triggered or cleared (Matched, Triggered, Cleared), the catalog or channel, the import, run or event it was about, and a summary of its Deliveries. Open an entry to see each delivery it made — every webhook and every email — with its status, the HTTP status the address answered, how long it Took, how many Attempts it needed, when the last attempt was and the start of the answer. Show payload shows the exact message a webhook receives.
hooks.example.com · webhook 2), so two webhooks to one service read apart. The number is its place when the delivery was made. The rest of an address often holds the receiving system's secret key, so Renable never shows it outside the webhook's own setting — not on this tab and not in an alert.The Alerts tab is different: it shows the monitor's alerts that are open right now. The Activity tab is the history.
On the monitor, or on the Monitoring page, tell Aimée what you want: "Also send a webhook to https://hooks.example.com/renable when it triggers." She adds Send a webhook to the monitor's draft with the events you asked for — and asks for the address if you didn't give one. Publish as usual, and use Send test on the Rule tab to check the address.