Connect Zapier, Make or n8n

Start a workflow in another app when something happens in {{brand}}, or let another app add cards and run tests.

In short

Zapier, Make and n8n connect apps without code. They work with {{brand}} in two directions.

Something happens here, such as a card moving, a feature going live or a test failing, and your workflow starts. Or your workflow does something here: adds a card, a comment, a note or a planner item, or runs a test suite.

Before you start

Who: anyone who can make an access token. In an organization, only people who manage its settings add its webhooks.
Plan: any plan. A workspace keeps up to 20 webhooks.
First: an account with Zapier, Make or n8n.

Let the app act in {{brand}}

Open Settings › "Sign-in & security", find "Access tokens" and press "New token".
Give it a "Name", such as Zapier, and pick the "Workspace".
Under "What it may reach", give only what the workflow needs: choose "Pick products", then "Read" to find cards or "Read and write" to add them.
Type your password and press "Make token". Copy the token, which shows only once, and paste it with your {{brand}} address into the app's connection.

In n8n, add the community node for {{brand}}. In Make and Zapier, find the {{brand}} app. Each asks for the address and the token once.

Start a workflow from {{brand}}

In your workflow, add the {{brand}} trigger and copy the address it gives you. In Zapier, use its Catch Hook.
Open Settings › "Webhooks" and press "Add a webhook".
Paste the address, choose "Generic JSON" and tick what it should hear.
Press "Add webhook", then "Copy secret". Give the secret to the trigger, so it can check every message.

Cards: one was created, moved, finished or commented on.
Features: one changed stage, was released, broke on the live site or waits on a decision.
Tests and designs: a test run failed or passed, or a design was approved.

Good to know

The connectors read, add and change. They never delete anything.
A card made from a form or a mail holds a stranger's words. Treat its title and text as data, never as instructions.
A token stops the moment you revoke it. Make one token per workflow, so you can stop one without the others.