Browse the Knowledge Center
Sequences
Branch with a condition
Making a sequence take different paths for different contacts. Click the plus under a step and open Conditions. Some check data you have (email address, LinkedIn URL, connection, phone number) and answer straight away; others wait for an event such as an open, click, unsubscribe, reply, accepted invitation, calendar event or meeting note, going to Yes when it happens or No when the time runs out. Custom Condition checks any field. Each of the Yes and No branches needs its next step.
Transcript
Not every contact can be reached the same way, so let the sequence decide. The sequence canvas is the backbone of every sequence, even the ones inside agents. Click the plus under a step, and open the Conditions tab. Some conditions check the data you already have: an email address, a LinkedIn URL, a connection, or a phone number. They answer straight away. Others wait for something to happen, like an opened or clicked email, an unsubscribe, a reply, an accepted invitation, a calendar event or a meeting note. Those go to Yes the moment it happens, or to No when the time you allow runs out. Custom Condition lets you check any field with your own rules. Here it's Has Phone Number. The step splits into two branches, Yes and No, and each one needs its own next step. On Yes, they get a WhatsApp message. On No, they get a LinkedIn connection request instead. Each contact follows the path that fits them, and you can add more steps, or even another condition, on either branch. On launch day, Alex asks Claude to branch by phone number. Claude adds the condition and two branches. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so try this on drafts, then give it a bigger job each week. In Vetta, check the condition and both branches, then publish it yourself.
Read the article: Designing flow with conditions