create_trigger
Create a trigger: it starts unpublished (nothing runs) and will check every 5 minutes once published. Reuse an existing one when it fits (see list_triggers). scope is what every playbook on it shares, in plain words; fetch is the code that reads the app (contract in get_builder_guide topic "triggers"). After creating, test_trigger then publish_trigger.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"integration": "<integration>",
"event": "<event>",
"scope": "<scope>",
"fetch": "<fetch>",
"name": "<name>"
},
"name": "create_trigger"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | A short name a person would recognise, e.g. "Candidate tickets". | |
| event | Yes | The kind of change it watches for, e.g. "ticket.updated". | |
| fetch | Yes | The fetch code: a module exporting `async function fetch({ cursor }, ctx)` and, where the app can read by time, `startFrom`. | |
| scope | Yes | What every playbook on this trigger shares, in plain words, e.g. "candidate support form, open tickets". | |
| integration | Yes | The app it watches, as list_integrations names it, e.g. "zendesk". |