Chain Triggers

A trigger decides when an executable Chain starts. It never supplies missing instructions, Bit execution sources, admission, or authority.

Supported trigger types are manual, cron, and event. Event triggers subscribe to supported domain events such as chain.created or connector events; historical progress-counter events are not supported.

Method	Path
`GET`	`/chains/automation/policy`
`POST`	`/chains/:chainId/triggers`
`GET`	`/chains/:chainId/triggers`
`PATCH`	`/chains/:chainId/triggers/:triggerId`
`POST`	`/chains/:chainId/triggers/:triggerId/deactivate`

json

{
  "trigger_type": "cron",
  "triggerConfig": { "expression": "0 9 * * 1", "timezone": "Europe/Istanbul" },
  "cooldownMinutes": 60,
  "maxRunsPerDay": 1
}

The scheduler enters the same Chain runtime as a manual request. Digest admission, grants, Bit sources, idempotency and final outcome checks therefore cannot be bypassed by scheduling.

Chain Triggers ​

Chain Triggers