Skip to main content
Condition and Prioritize by group are the two built-in branching nodes on the workflow canvas. Unlike the steps documented elsewhere in this reference, they aren’t blocks you configure with a fixed set of settings — they split the flow into multiple paths based on the data available at that point, so different records can take different routes through the rest of the workflow.

Condition

Branch the workflow depending on the data available at this step. A Condition node splits the flow into branches based on rules over the fields of the contacts or companies passing through it. Each branch is a rule comparing a field — equals, contains, starts with, greater/less than (including dates), is one of a set of values, is within the last N days, or is empty/not empty — or a group of rules combined with AND/OR. You can also add a random-split branch that routes a percentage of records regardless of their data, useful for A/B testing a downstream path. Rules aren’t limited to the record’s own fields. Contacts can also be split by engagement: whether they replied, viewed an email, clicked an email link, or viewed a LinkedIn message — each optionally scoped to specific campaigns or sending identities. You can add as many branches as you need. Records that don’t match any branch’s rule always fall through a built-in default branch, so every record leaving a Condition node has somewhere to go. Use it whenever contacts or companies need to take different paths based on their data — for example, splitting records by company size, by whether they have a verified email, or by which type of LinkedIn activity brought them in.

Prioritize by group

Prioritize a fixed number of records from every group, then route the remaining records separately. A Prioritize by group node groups the contacts or companies passing through it by a field you choose — for example, company id, to group contacts from the same company together — then sorts each group by the formula field you select. Lower values are prioritized first, records without a value come last, and the configured number of records from every group follows the Prioritized branch. Ties do not expand that number. Every other record follows Remaining. Use it to enforce an exact per-group cap before continuing — for example, prioritizing up to 10 contacts per company for a campaign and routing the rest to a review or nurture list. When grouping by a website or domain field, Match domains regardless of suffix groups variants with the same domain name, such as .com and .io.