Use it when you have your own service or workflow tool (n8n, Zapier, an agent behind an HTTP endpoint) and it only needs to know when something happened.

How they work

Every board has Automations: rules that react when something happens, such as a card being added, moved, commented on, or coming due. One thing a rule can do is call a URL. It POSTs a JSON body with the rule, the event, the board and the card (title, link, list, priority, assignee, dates, status, health, flags and tags), or sends the same fields as query parameters if you choose GET.

It's the lightest way to connect: nothing to install, and no token to hand out, because the board calls you. It only goes one way, though. To change the board in response, the receiving end needs the API, MCP or the CLI.

Set one up

On a board you own, open Automations and pick the ready-made webhook rule, or describe what you want in your own words, for example:

when a card moves to Done, POST to https://example.com/hooks/done

The URL can include placeholders such as {{card.id}} in its path or query.

Good to know

  • Only public http and https addresses are called. Loopback, private and tailnet addresses are refused, so a webhook can't reach into the network the server runs on.
  • To have an agent work the card, rather than just hear about it, use a runner.