What happens after a run goes wrong, and what happens when you point a flow at eleven thousand old rows. Which errors get retried and which never will, how a queue looks different from a failure, and the backfill settings worth checking twice.
beginner
7:12
Build your first flow: Gmail to Trello
Start with an empty account and finish with labelled support email landing on a Trello board as cards. Covers both connections, the Gmail search that keeps the rest of the mailbox out, the four field mappings that matter, and a live test on a real message.
Video placeholder
Split frame. Left side a Gmail list filtered to label:support with three unread threads. Right side a Trello list called New with three fresh cards. A thin arrow between them carrying the Syncline mark. Light background, no faces, no stock photography.
Chapters
From the transcript
Right, empty account, nothing built yet. I want every email that gets the support label to show up as a card on our triage board, and I want it done before this coffee goes cold. First is the trigger, because a flow always starts with the thing that happens. I pick Gmail, then New labeled email, and Syncline sends me off to sign in. Notice it only asks for read and send on this one account, and it shows you the exact search it will run. Mine is label:support and nothing else, so the rest of that mailbox stays out of this entirely. Now the action. Trello, create a card, board is Support Triage, list is New. The field map is the part people worry about and it takes about ninety seconds: subject goes to card name, the sender address goes into the description, received at goes to the due date. Hit test. There it is, a real card from a real email, with a link back to the thread.
More videos
One trigger, three actions, and the order decides whether the result is usable. A first payment creates the contact, moves the deal and opens the onboarding card, each step handing its output to the next, with a clean stop when the first one fails.
The flow is rarely broken. One record is failing over and over, and the history names it in about thirty seconds. Sort by failed, read the two columns beside the error rather than the error itself, fix the mapping, replay the backlog in one pass.