Automations

Small trigger → action rules that take care of the busywork on your board.

An automation is a simple trigger -> action rule — for example, “when a card is moved to Done, archive it”. Rules are per project and don’t chain: an action fired by an automation never triggers another automation.

Triggers

  • card_created — a card was created in the project.
  • field_changed — a field changed to a specific option (fieldId + toOptionId), e.g. Status → Done.
  • pr_merged — fired by an inbound event through POST /projects/:id/events.

Actions

  • set_field_value — set a field to an option (optionId) or a raw value.
  • archive_card — archive the card.

Create one

In the UI, open the project’s Automations tab and fill in the guided form. Through the API or MCP, create it with one call:

{
  "name": "Archive when done",
  "trigger": { "type": "field_changed", "fieldId": "<statusFieldId>", "toOptionId": "<doneOptionId>" },
  "action": { "type": "archive_card" }
}

POST /projects/:id/automations creates it over REST; the create_automation MCP tool does the same for your agent — ask for it in plain language (“when a card lands in Done, archive it”) and the agent maps it to the tool.