Webhooks

Webhooks let RezolveIT notify other systems the moment something changes — an incident opens, a change is approved, an asset is retired.

Subscribe to events

Register an endpoint and the events it should receive (by table and condition). When a matching event fires, RezolveIT POSTs a JSON payload describing the record and what changed.

Payload

POST https://your-app.example.com/hooks/rezolveit
{
  "event": "incident.updated",
  "record": { "number": "INC0012345", "state": "resolved" },
  "changed": ["state", "resolution_notes"],
  "at": "2026-07-26T09:00:00Z"
}

Security and reliability

Payloads are signed so you can verify they came from your instance. Delivery is retried with backoff on failure, and you can inspect delivery history to debug.

Webhooks vs. the API

Use webhooks to react to changes (push), and the REST API to fetch or change data on demand (pull). Most integrations use both.

Works with n8n, Make, Zapier and more

Webhooks are the trigger side of every automation platform: point a subscription at n8n’s Webhook node, Make’s custom webhook, or Zapier’s Catch Hook, and the platform picks up RezolveIT events in real time. Step-by-step recipes for each tool are in Automation platforms.