Build your first flow in 15 minutes

<h2>What you need before you start</h2><p>A flow moves a record from one app into another. To build one you need two connected accounts, a place in the source app where new records show up, and about fifteen minutes of quiet. Most people build their first flow between a task board and a chat channel, because both are easy to look at while you work.</p><p>If you have not connected any accounts yet, do that first. The builder will send you to the connection screen anyway, and coming back part way through loses the draft you had started.</p><h2>Build the flow</h2><ol><li><strong>Open the builder.</strong> Click <em>New flow</em> on the dashboard. Name it after what it does, something like <em>New Trello card to Slack</em>, so the run history still reads clearly in three months when somebody else opens it.</li><li><strong>Pick the trigger app and account.</strong> Choose the app where the record starts, then the connected account. If your workspace holds two accounts for the same app, the account label appears under each option so you do not have to guess.</li><li><strong>Pick the trigger event.</strong> Each app offers between four and six events. A narrow event saves you a filter later: <em>Item enters a status</em> fires far less often than <em>Page property updated</em>, and both can end up doing the same job.</li><li><strong>Load a sample record.</strong> Click <em>Fetch sample</em>. Syncline pulls the three most recent matching records so you can map against real values rather than placeholder names. Nothing is written anywhere at this point.</li><li><strong>Add the action.</strong> Choose the destination app, the account and the action. The builder now shows two columns: source fields on the left, destination fields on the right.</li><li><strong>Map the fields.</strong> Drag a source field onto a destination field, or type a fixed value into it. Required destination fields carry a marker, and the flow refuses to save while one of them is empty.</li><li><strong>Run the test.</strong> <em>Test flow</em> sends one sample record through for real. Open the destination app and look at what arrived before you go any further.</li><li><strong>Turn it on.</strong> Flip the switch at the top right. The first scheduled check runs within three minutes on a paid plan and within fifteen minutes on the free plan.</li></ol><blockquote><p>Note: a test run writes a real record into the destination app. Point the first test at a scratch board, a quiet channel or a draft database, then switch the destination once the mapping looks right.</p></blockquote><h2>Reading the test result</h2><p>The test panel returns one of four outcomes, and each one has a different next move.</p><table><thead><tr><th>Result</th><th>What it means</th><th>What to do next</th></tr></thead><tbody><tr><td>Delivered</td><td>The destination app accepted the record and returned an ID.</td><td>Check the record by eye, then enable the flow.</td></tr><tr><td>Skipped by filter</td><td>Your sample did not match the conditions you set.</td><td>Fetch a different sample, or loosen the filter and test again.</td></tr><tr><td>Field rejected</td><td>One value was the wrong shape for the destination field.</td><td>Open the mapping, fix that single field, test again.</td></tr><tr><td>Connection error</td><td>The account was refused before any record moved.</td><td>Reconnect the account, then rerun the test.</td></tr></tbody></table><h3>After the first day</h3><p>Come back the next morning and open the run history. You are looking for two things: that the number of runs matches roughly what you expected, and that nothing sits in a failed state. A first flow that runs forty times in a night usually means the trigger event was too broad, and one filter fixes it.</p>