Leveraging workflow logic: filters, conditions and branching

Workflow logic controls how a Vetta workflow makes decisions. The trigger decides when a workflow starts and the actions decide what it does; logic decides which actions run for which record, how often, and when. With it, one workflow can send a large company to your enterprise sequence and a small one to your SMB sequence without anyone choosing by hand.

You'll find the flow-control steps in the Flow tab of the action panel: Filter, If / Else, Switch, Iterator and Delay. On top of these, every step has a Continue only if section.

Filters

A Filter step limits which records continue through the workflow. It checks fields from the trigger or earlier steps, and if the conditions are not met, the workflow stops there.

Use a filter when a workflow should only apply to some records, for example one industry or one lead source.

Example: a workflow runs when a record is updated. If the industry field equals "SaaS", the contact is added to a SaaS onboarding sequence. Otherwise the workflow stops and nothing happens.

Continue only if

Any step can decide whether the workflow goes on, without a separate Filter step. Open the step and expand Continue only if. Its conditions are checked against this step's own output, right after the step runs. If they don't match, the workflow stops there.

1. Click Add first filter and build a rule, for example Email is not empty.
2. To accept either of two things, click Add rule group and switch the group to Or: job title contains Finance, or job title contains CFO.

A contact without an email now stops quietly at this step and never reaches the sequence. In Runs, the step still shows a check, but its filter icon turns red: the conditions didn't match, so the next step was skipped, and the run still counts as completed.

Narrated video · 1:05

2 linked topics

Stopping a workflow quietly when a record does not qualify. Open a step and expand Continue only if; its conditions are checked against that step's own output right after it runs, and if they do not match the workflow stops there. The example adds a rule that the email is not empty, plus a rule group set to Or for job title containing Finance or CFO. In Runs the step shows a check, its filter icon turns red, and the run still counts as completed.

Transcript

Any step can decide whether the workflow goes on. Open the step and expand Continue only if. Its conditions are checked against this step's own output, right after it runs. If they don't match, the workflow stops there. Add a rule: the email is not empty. To accept either of two things, add a rule group and switch it to Or: the job title contains Finance, or it contains CFO. Now a contact without an email stops quietly at this step, and never reaches the sequence. In Runs, that step still shows a check, but its filter icon turns red: the conditions didn't match, so the next step was skipped, and the run still counts as completed. Every Friday, Tom asks Claude to tighten who reaches outreach. Claude adds a rule and finds 31 contacts it would stop. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so start small, then give it a bigger job each week. In Vetta, test the draft, then activate it yourself.

If / Else conditions

If / Else splits the workflow into two paths based on a condition: True runs when the condition is met, False runs when it isn't.

1. Add If / Else from the Flow tab, under the trigger.
2. Build the condition from an earlier step's output, for example the new person's company Employees greater than or equal to 50. Add filter rule adds another rule or a whole group of rules.
3. Save. The step now has two outputs.
4. Add the steps for each path: the enterprise sequence under True, the sequence for smaller teams under False.

One workflow gives two journeys, and every run takes the right one on its own. Common uses include deal stage automation, lead qualification and routing by company size.

Narrated video · 1:06

2 linked topics

Sending records down two different paths. If / Else is in the Flow group of the step library; add it under the trigger and build the condition from an earlier step's output, such as the new person's company Employees greater than or equal to fifty. Add filter rule adds more rules or a group. After saving, True runs when the condition is met and False when it is not, so each branch can hold its own sequence. Use it for two journeys, such as enterprise and smaller teams.

Transcript

When different records need different handling, use If / Else. You'll find it in the Flow group of the step library: it splits the workflow into two paths based on a condition. Add it under the trigger, then build the condition from an earlier step's output. Here, the new person's company, Employees, greater than or equal to fifty. Need more than one check? Add filter rule adds another rule, or a whole group of rules. Save, and the step now has two outputs. True runs when the condition is met, so add the enterprise sequence below it. False runs when it isn't: add the sequence for smaller teams on the right. One workflow, two journeys, and every run takes the right one on its own. Every quarter, Priya asks Claude to split leads by company size. Claude builds two paths and leaves it as a draft. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so try one workflow, then give it a bigger job each week. In Vetta, test both paths, then activate it yourself.

Switch

When you need more than two paths, use Switch, also in the Flow tab. Each case has its own condition:

1. Set Case 1, for example the person's language is French.
2. Click Add case for the next one: language is Italian.
3. Save. Switch gets one path per case, plus Otherwise.
4. Add a step under each path: the French sequence under Case 1, the Italian one under Case 2, and the English sequence under Otherwise for everyone else.

Cases are checked in order and the first match wins, so put the most specific case first. Anyone who matches no case takes Otherwise, which means nobody falls through the cracks. Use Switch instead of chaining several If / Else steps whenever one value has more than two meaningful cases.

Narrated video · 1:03

1 linked topic

Branching a workflow into more than two paths. Switch is in the Flow group; each case has its own condition (for example language is French, then language is Italian), added with Add case. Cases are checked in order and the first match wins, and anything matching no case takes Otherwise. Each path then gets its own step, such as the French, Italian and English sequences. Use it instead of If / Else when you need several journeys.

Transcript

If / Else gives you two paths. When you need more, use Switch, also in the Flow group of the step library. Each case has its own condition. Case 1: the person's language is French. Add case for the next one: language is Italian. Cases are checked in order, and the first match wins. Anyone who matches no case takes Otherwise. Save, and Switch gets one path per case, plus Otherwise. Now add a step under each path. Under Case 1, the French sequence. Under Case 2, the Italian one. And under Otherwise, the English sequence for everyone else. One step, as many journeys as you need. Every Monday, Luca asks Claude to route new leads by language. Claude drafts a Switch with two cases and an Otherwise. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so repeat this for each market, then give it a bigger job. In Vetta, check each path, then activate it yourself.

Iterators

An Iterator runs the same steps once for every item in a list, such as the records returned by Search Records or Find Pipeline Records.

Example: when a deal is won, everyone at that company gets a thank-you task.

1. Add a Search Records step that finds the people at the deal's company. Raise its Limit, because it starts at 1.
2. Add an Iterator from the Flow tab and give it the list in Items to iterate over: from Search Records, all the people it found.
3. The iterator gets a loop path with an empty step on it. Click it and pick Create Task.
4. Inside the loop you can use the current item, so the task title can take each person's first name.

Everything on the loop path runs once per person, and the completed path carries on after the last one. In a run, open the task step and page through the items to see one pass per person.

Narrated video · 1:05

Running a step once for every item in a list. The example creates a thank-you task for everyone at a company when a deal is won: a Search Records step finds the people (raise its limit, it starts at one), then an Iterator from the Flow group takes All People and gives a loop path. Inside, Create Task can use the current item, such as each first name, and the completed path continues afterwards. In a run you can page through one pass per person.

Transcript

Some jobs need doing once for every item in a list. Here, when a deal is won, everyone at that company should get a thank-you task. First, a Search Records step finds the people at the deal's company. Raise its limit, because it starts at one. Then add an Iterator from the Flow group, and give it the list: from Search Records, All People. The iterator gets a loop path, with an empty step on it. Click it and pick Create Task. Inside the loop you can use the current item, so the title takes each person's first name. Everything on the loop path runs once per person, and the completed path carries on after the last one. In a run, open the task step and page through the items: one pass per person. After each win, Lena asks Claude to thank the whole account. Claude drafts a loop with one task per person. Claude, ChatGPT or any assistant you connect to Vetta works on your real workspace, so repeat this after every win, then give it a bigger job. In Vetta, test one deal, then activate it yourself.

Delay

Delay pauses the workflow before it continues. Choose After a set amount of time (in days, hours, minutes or seconds) or At a specific date or time. It is commonly used in follow-up, onboarding and reminder workflows.

Example: add to the onboarding sequence → wait 2 days → create a check-in task for the customer success manager.

Combining workflow logic

These steps work together. A workflow might filter for deals over $10,000, use Switch to branch on the opportunity stage, and enroll contacts in a different sequence or create a different task on each branch. To see which path a record actually took, open the run in Monitoring workflow runs and versions.

Common questions

Key outcome

Your workflows can now make decisions: stop for records that don't qualify, split into two or many paths, repeat steps for every item in a list, and wait for the right moment. That lets one workflow mirror how your team actually treats different leads, deals and customers.