Webhooks

Send an alert anywhere you can accept a POST.

POST the alert to a URL of your own, with an optional bearer token. This is the escape hatch: if a tool is not on the integration list but accepts incoming requests, a webhook reaches it.

Any URL you control. Internal services, custom tooling, an automation platform, a script behind a small endpoint. If it accepts a POST, it works.
Optional bearer token. The endpoint you expose does not have to be open to anyone.
Encrypted at rest. The token you enter is encrypted at rest.

Start free All features

01 · What people build with it

The gap between a tool list and reality.

Every integration list is incomplete. This is the one that closes the gap without waiting for a feature request.

Internal tooling

Push alerts into a dashboard, database or service your team wrote, in whatever shape that system expects.

Automation platforms

Point at a platform that accepts inbound webhooks and use its own logic to route onward from there.

Unsupported chat tools

Any chat or paging service with an inbound webhook is reachable, even without a dedicated Hesklo connection type.

Logging and analytics

Feed outage events into the system where you already keep operational data, so alerting and analysis share a record.

Recovery signals

Wire a webhook to the monitor up port so a downstream system knows the service is healthy again, not just when it broke.

Not the same as an action

A webhook notify tells a system something happened. An HTTP action is the step designed to make something happen, with method, headers and body control.

Questions

Common questions

What can I use a webhook for?

Anything that accepts a POST request. Internal services, custom tooling, automation platforms, logging systems and chat tools that are not on the integration list are all reachable this way.

How do I secure the endpoint?

The connection supports an optional bearer token, so your endpoint can require authentication. Beyond that the endpoint is yours, so the usual controls apply: restrict the source, keep the handler narrow, and log what it receives.

What is the difference between a webhook and an HTTP action?

A webhook notify sends the alert to a system so it knows something happened. An HTTP action is designed to make something happen, such as restarting a service, and gives you control over the method, headers and body. Use a webhook to inform and an action to remediate.

Can a webhook fire when a service recovers?

Yes. Wire a webhook notify step to the monitor up port and the downstream system gets a recovery signal as well as an outage one.