Start a workflow from Trello card events

Trello triggers start a run from what happens on a board:

• Trello · New card — When a card is added to a board.
• Trello · Card moved to a list — When a card moves to another list.
• Trello · Card updated — When a card on a board changes.
• Trello · New comment — When someone comments on a card.
• Trello · Card due soon — When a card's due date is near.

The first four are instant — Trello tells Bizomate the moment it happens, and publishing adds a webhook to the board for you; see How instant triggers work. Card due soon checks the board every 15 minutes, on every plan.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the trigger and its status but cannot change it.

Before you start

A Trello connection — see Connect Trello — whose account is a member of the board. The instant triggers use the connection's API secret to check that each event is Trello's.

Steps

Set up an instant trigger:

1. Open the workflow in the designer and open the trigger picker — Browse all triggers on an empty workflow, or select the trigger and Change how it starts.
2. Under Trello, select the event. The instant ones read Trello · instant. Or type Trello in Search triggers.
3. In Connection, choose your Trello connection.
4. In Board, choose the board — for example Consulace clients. For New card: A card made, copied, emailed in or turned from a checklist item starts one run. For Card updated: Any change to a card — its name, description, due date, list, or archiving it — starts one run.
5. For New card: optional, in Only in this list, a list — Empty: any list.
6. For Card moved to a list: optional, in Moved to, the list — Only cards moved into this list. Empty: a move to any list. For example Done.
7. The panel reads Publishing sets this up in Trello, and every publish sets it up again. It stays while the workflow is published — switched off, what arrives is ignored — and is taken away when the workflow is deleted or starts another way.
8. Add the steps, then Publish. Bizomate adds a webhook to the board, and the panel reads Waiting for the first event — Make one happen; it appears here within seconds.

Test with a real event:

1. Make the event happen on the board — add a card, or move one to Done.
2. Within seconds the panel reads Listening — instant — Last event 10:45 · Card moved to Done · Onboard Northwind Logistics.
3. On Output, select Use the last event, then Test run.

Set up Card due soon:

1. Under Trello, select Card due soon, and choose the Connection.
2. In Board, choose the board — Checked every 15 minutes. Each card starts one run as its due date nears — again only if the date changes.
3. Optional: in Only in this list, a list — Empty: the whole board.
4. In Due within, how near counts as soon — 1 hour, 24 hours (the default), 2 days or 7 days. Cards marked done, and archived ones, never start a run.
5. On Output, select Fetch a sample. The next card due comes in — or, with none ahead, the one due most recently — and Test run starts with it.
6. Add the steps, test, then Publish.

What the trigger gives

The card, read back from Trello as the Trello steps read it — id, name, description, url, listId, listName, boardId, boardName, dueDate, dueComplete, labels, members, closed — and user, the full name of whoever did it (empty for Card due soon, which nobody does). Also:

• Card moved to a list: previousListName — the list it came from, To do.
• New comment: commentId and text — Contract signed.

What happens next

• Each event starts one run of the live version, in Production, named after it — New card · Onboard Northwind Logistics, Card moved to Done · Onboard Northwind Logistics, New comment · Onboard Northwind Logistics, Card due soon · Onboard Northwind Logistics.
• Each workflow has its own webhook on the board. Every publish sets it up again; changing to another trigger or board and publishing, or deleting the workflow, removes it.
• Card due soon starts one run per card as its due date comes within the window — even when the date passed between two checks. Changing the due date starts another when the new date comes near.
• Card due soon's first check only notes what is already due soon, and starts nothing. Up to 100 cards start runs in one check; the rest wait for the next. The panel shows Checking every 15 minutes — Last checked 10:45 · next 11:00.

How Bizomate knows an event is Trello's

Trello signs every event with your Power-Up's API secret (the X-Trello-Webhook header), and Bizomate works the signature out again with the secret kept on the connection. An event whose signature does not match is answered 401 — The signature does not match. — and starts nothing.

Good to know

• Card updated hears changes to the card itself — its name, description, due date, list, position, and archiving it. Adding a label, a member, an attachment or a checklist item is not one of them, and nor is a comment.
• Moving a card is also an update. Workflows on both triggers both run.
• New card with Only in this list runs only for cards added straight to that list. A card added elsewhere and moved there later is a job for Card moved to a list.
• A card deleted before Bizomate reads it still starts its run, with what Trello's event says about it.
• Card due soon checks every 15 minutes whatever the plan, so a run can start up to 15 minutes after the card comes within the window. It has no Checks choice.

If something goes wrong

Related

• How instant triggers work
• Connect Trello
• Create, update or move a Trello card
• When an app trigger stops checking
• Change how a workflow starts