The trigger object

Shape of a Trigger, webhook or schedule that fires an agent autonomously.

A Trigger is what makes an agent fire autonomously, without a user typing. Two kinds: webhook triggers (a third-party event like "new Zendesk ticket") and scheduled triggers (cron-style, e.g. "every hour").

Object shape

{
  "id": "trigger_64f1c0ef2ec711ef6dc1dcf",
  "agent_id": "agent_64f1c0...",
  "connector_id": "connector_64f1c0...",
  "connector_type": "zendesk",
  "event": "ticket.created",
  "is_active": true,
  "conditions": { "tags": ["billing"] },
  "settings": { "debounceMs": 0 },
  "schedule": null,
  "created_at": "2026-06-01T00:00:00.000Z",
  "updated_at": "2026-06-20T12:00:00.000Z"
}

Attributes

Field	Type	Notes
`id`	string	`trigger_<24 hex>`.
`agent_id`	string \| null	Which agent fires when the trigger matches.
`connector_id`	string \| null	Null for Macha custom triggers and cron-scheduled triggers (which aren't tied to a connector).
`connector_type`	string	e.g. `zendesk`, `slack`, `freshdesk`, `macha`, `scheduler`.
`event`	string	e.g. `ticket.created`, `app_mention`, `cron.scheduled`, `macha.custom_trigger`.
`is_active`	boolean	Disabled triggers don't fire. Synced with the bound agent's `is_active`.
`conditions`	object \| null	Match conditions (e.g. tag filters, status filters). Connector-specific.
`settings`	object	Debounce, batching, etc. Free-form.
`schedule`	object \| null	Set only for `cron.scheduled` triggers. See below.
`created_at`	ISO 8601
`updated_at`	ISO 8601

Schedule shape (scheduled triggers only)

{
  "cron_expression": "0 * * * *",
  "interval_hours": null,
  "next_run_at": "2026-06-24T11:00:00.000Z",
  "last_run_at": "2026-06-24T10:00:00.000Z",
  "last_run_status": "succeeded"
}

Why the webhook signing secret isn't exposed

The webhookSigningSecret field on the underlying trigger document is the customer's shared HMAC secret for verifying inbound webhooks from third parties. The dashboard shows it once at creation time; the API treats it as write-only and never returns it.

📘

Trigger writes are planned

v1 is read-only for triggers. Create / update / delete via the dashboard. The setup flow for webhook triggers requires creating webhooks in the external service (Zendesk, etc.), which has its own configuration UI.