Automation platforms — n8n, Make, Zapier

RezolveIT plugs into any automation platform through two building blocks it already ships with: webhooks push events out the moment a record changes, and the REST API lets the platform read and write records on demand. If a tool can receive an HTTP call and make one — n8n, Make, Zapier, Power Automate, Workato, or your own scripts — it can drive RezolveIT end to end.

The integration pattern

Every recipe below follows the same shape:

1. Trigger (RezolveIT → platform): register the platform’s inbound URL as a webhook endpoint in Admin Studio → Webhooks, scoped to a table and condition (for example incident where priority = P1). RezolveIT POSTs a signed JSON payload on every matching event.
2. Act (platform → RezolveIT): the platform calls the REST API with a service-account token to create, update or query records. The token is bound by the same roles, ACLs and row-level security as any user — an automation can never see or touch more than its service account allows.

RezolveIT ──(webhook: incident.updated)──▶ n8n / Make / Zapier
RezolveIT ◀──(REST: PATCH /api/v1/records/incident/…)── n8n / Make / Zapier

Before you start, create a service account with only the roles the flow needs, and issue it an API token (Admin Studio → Service accounts). Use one account per integration so the audit trail tells you exactly which flow changed what.

n8n

n8n’s Webhook and HTTP Request nodes map one-to-one onto the pattern:

1. Add a Webhook node (method: POST). Copy its production URL into a RezolveIT webhook subscription — e.g. table incident, condition state = new.
2. Branch on the payload with an IF node — the body carries event, record and changed, so {{$json.record.priority}} routes P1s to PagerDuty and everything else to Slack.
3. Close the loop with an HTTP Request node: method PATCH, URL https://<your-instance>/api/v1/records/incident/{{$json.record.number}}, an Authorization: Bearer <token> header (store the token in an n8n credential, not in the node), and a JSON body such as { "work_notes": "Paged on-call via n8n" }.

Because n8n is self-hostable, this pairing suits teams that want the whole automation path — RezolveIT included — on their own infrastructure.

Make

1. Create a scenario starting with a Custom webhook module and paste the generated address into a RezolveIT webhook subscription. Run the scenario once so Make learns the payload structure from a live event.
2. Add HTTP → Make a request modules for the RezolveIT side: GET /api/v1/records/… to enrich the event with related data (the linked CI, the caller’s department), POST/PATCH to write back.
3. Use Make’s routers and filters on payload fields (event, changed) the same way you would in n8n.

Zapier

1. Start a Zap with Webhooks by Zapier → Catch Hook and register the hook URL in RezolveIT. The fields of record become Zap fields you can map into any of Zapier’s apps.
2. To act on RezolveIT, add Webhooks by Zapier → Custom Request with the REST endpoint, the bearer token in the headers, and a JSON body.
3. Typical Zaps: create an incident from a Typeform submission, post approved changes to a Google Calendar, or append resolved-incident rows to a Google Sheet for reporting.

Other tools & plain scripts

The same two endpoints work for anything else — Power Automate (“When an HTTP request is received” + “HTTP” actions), Workato, Pipedream, or a cron job with curl. There is no SDK to install and no proprietary connector required: if it speaks HTTP and JSON, it integrates.

Reliability tips

• Verify signatures on incoming webhooks (see Webhooks — security and reliability) before trusting a payload.
• Expect retries. Delivery is retried with backoff, so make flows idempotent — key on record.number + event rather than assuming exactly-once.
• Filter at the source. A webhook condition in RezolveIT (priority = P1) is cheaper than filtering inside the platform, and keeps your run quotas down on metered tools like Zapier and Make.
• Least privilege. One service account per flow, holding only the roles it needs — the audit trail then reads like a log of your automations.

Enterprise plans add prebuilt Slack, Teams, PagerDuty and Jira integrations plus SMS/WhatsApp notifications on top of these building blocks — see Editions.