Automation Webhooks and External Updates

Automation rules can talk to systems outside Equip. The Notify an external system (webhook) action sends candidate details to a URL you choose, and the An external system sends an update trigger lets that system report back, for example when a background check clears.

These webhooks are set per rule, on a pipeline stage. For team-wide notifications when a candidate completes an assessment or AI interview, see Webhooks instead.

Add a Webhook Action

Open the rule

In the job’s Settings, under Candidate Pipeline, open the stage’s Automation dialog and create or expand a rule.

Add the action

Click Add action and choose Notify an external system (webhook).

Enter the method, URL, and headers

Pick the method and enter your endpoint, which must start with https://. Expand Headers to add any your endpoint needs, such as an Authorization header, then click Save.

Expanded rule Tell the ATS when they move on, with the trigger Candidate leaves this stage, no conditions, and the action Notify an external system (webhook) set to POST https://ats.example.com/hooks/equip/stage-left. Headers 2 is expanded, listing Content-Type application/json and Authorization Bearer followed by a token, with Add header and Add action links below — A webhook action with its method, URL and two headers

Header values are stored with the rule and are visible to every recruiter on your team who opens it. Use a token that is scoped to this integration only.

The Payload

Every webhook sends the same JSON structure. There is no payload editor; if your system needs more detail, it can fetch it with the Equip API.

{
  "event": "stage_automation.rule_fired",
  "rule": { "id": "…", "name": "Send for background check" },
  "team_id": 135,
  "job_opening": { "id": 9875, "label": "CT1YNM", "title": "Product Designer" },
  "stage": { "config_id": 9990, "type": "ASSESSMENT", "name": "Assessment 1", "status": "GRADED" },
  "subject": { "type": "job_application", "id": 12345, "uuid": "…", "label": null },
  "candidate": { "first_name": "…", "last_name": "…", "email": "…" },
  "stage_progress_id": 777,
  "signals": { "overall": { "value": 84, "label": "Strong" } },
  "links": { "api": "…" },
  "callback_url": "…",
  "sent_at": "2026-09-09T10:00:00Z"
}

Field	Description
`event`	Always `stage_automation.rule_fired`.
`stage`	The stage’s type, name, and the candidate’s current status in it.
`signals`	The stage’s scores, such as the overall score for an assessment.
`links.api`	The API address of the candidate’s application.
`callback_url`	The address your system uses to send an update back.
`sent_at`	When the webhook was sent, in UTC.

Send an Update Back

To report a result to Equip, your system sends a POST request to the callback_url it received in the webhook.

{
  "status": "BACKGROUND_CHECK_CLEARED",
  "data": { "reference": "BC-20417" }
}

Field	What Equip does with it
`status`	Sets the candidate’s status in the stage. Use a status ID that exists on the stage.
`data`	Stored with the candidate’s progress in the stage, replacing any earlier update.

Two kinds of rule can react to the update. A rule with the An external system sends an update trigger runs when the update arrives, and a rule with Status changes to runs when the status becomes the one you picked.

The external update trigger can only be used on a stage where some rule fires a webhook. The webhook is how the external system receives its callback address.

The callback address needs no other login, expires, and can be used once. Treat it as a secret, and send text or references in data, not files or media.

Example: A Background Check Stage

A Custom stage with its own statuses can run a full hand-off without anyone clicking a button.

Rule	Trigger	Action
Request the check	Candidate enters this stage	Notify an external system (webhook)
Move cleared candidates on	Status changes to Background check cleared	Move candidate to Next Stage
Flag problems	Status changes to Background check failed	Reassign to a team member

The background check provider receives the webhook, runs the check, and posts the matching status to the callback address. To set up the statuses, see Automation Triggers, Conditions, and Actions.

Stage Automation - Create and manage automation rules
Automation Triggers, Conditions, and Actions - Every trigger, condition, and action, plus custom statuses
Webhooks - Team-level notifications for completed assessments and interviews
API Integrations - Fetch more detail about a candidate from your own systems

ATS

Assessments

AI Interviews

Candidate Experience

Account & Billing

Automation Webhooks and External Updates

Add a Webhook Action

The Payload

Send an Update Back

Example: A Background Check Stage

​Add a Webhook Action

​The Payload

​Send an Update Back

​Example: A Background Check Stage

​Related Resources

Add a Webhook Action

The Payload

Send an Update Back

Example: A Background Check Stage

Related Resources