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.
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.
King
Split records into ranked groups before continuing the flow.
A King node groups the contacts or companies passing through it by a field you choose — for example, domain, to group multiple contacts from the same company together — then ranks the records within each group using the score from a formula field you select. The top-ranked record(s) in each group (how many is configurable, defaulting to the single best) continue down one branch, and the rest of the group continues down the other. When grouping by a website or domain field, you can also match records that share any domain variant of the same company.
Use it to cut a batch down to the best record per group before continuing — for example, keeping only the highest-scored contact per company for outreach and routing the rest to a different path, such as a nurture list.