Automations

Automation updated

automation.updated

Fires when an automation is modified — its name, status (enabled/disabled), or trigger rules. The payload carries the automation state after the update.

HTTP request

AISAR sends a signed POST request to your webhook_url:

http

POST {webhook_url}
Content-Type: application/json
X-AISAR-Signature: sha256=...

{
  "event": "automation.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-03-26T10:00:00.000000Z",
  "company_id": 1,
  "data": {
    "automation": {
      "id": 5,
      "name": "Welcome Message (Updated)",
      "status": "inactive",
      "created_at": "2026-03-26T09:00:00.000000Z"
    }
  }
}

The X-AISAR-Signature header carries an HMAC-SHA256 signature of the request body — use it to verify the request came from AISAR.

Example payload

json

{
  "event": "automation.updated",
  "event_id": "evt_01JXXXXXXXXXXXXXXXXXXXXX",
  "timestamp": "2026-03-26T10:00:00.000000Z",
  "company_id": 1,
  "data": {
    "automation": {
      "id": 5,
      "name": "Welcome Message (Updated)",
      "status": "inactive",
      "created_at": "2026-03-26T09:00:00.000000Z"
    }
  }
}

Payload fields

Field	Type	Description
`automation.id`	`integer`	Automation ID
`automation.name`	`string`	Automation name
`automation.status`	`string`	Status: `active` or `inactive`
`automation.created_at`	`string`	ISO 8601 creation timestamp