Condition
Split the run into up to 12 segments plus None, checked top to bottom — the first segment whose conditions all pass wins.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Condition.
- In the first segment, click + Add condition and pick a field, how to compare it, and a value.
- With two or more conditions, choose all match (AND) or any matches (OR); click + Add segment for more segments.
- None is for contacts who match no segment — put steps there, or leave it empty; it is always there.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- If an earlier step in this run adds a tag or changes a saved contact field, no later Condition in that run sees the change.
- The one exception is the contact's marketing consent, which is always checked fresh.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Condition under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing it is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- Nothing outside Inchat has to be connected. A condition only reads fields the run already has — from the trigger, an earlier step's answer, or an HTTP Request's saved response.
Set up
- Open the workflow and click + where the split belongs.
- Pick Condition.
- Name the first segment (optional — it defaults to Segment 1) and add one or more conditions to it. With more than one condition, choose all match (AND) or any matches (OR).
- Click + Add segment for each further segment. Segments are checked in order, so put the narrowest one first.
- Leave None's steps for contacts that match nothing; it always exists and cannot be removed.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Segment
- One segment: a label, up to 10 conditions, and its own steps. The first segment (top to bottom) whose conditions all pass is the one that runs.
- Limits: Up to 12 segments, each with up to 10 conditions — saving refuses more than either, even though Configure step itself does not stop you adding them. The last remaining segment cannot be deleted — a Condition step always keeps at least one.
- all match (AND) / any matches (OR)
- How a segment's own conditions combine when it has more than one. Shown only once a segment has two or more conditions.
- Default: all match (AND)
- None segment
- Runs when no segment's conditions matched. Always present, and not one of the segments you add.
How it works
- Segments are checked top to bottom. The first segment whose conditions all pass — or, with any matches, at least one condition passes — is the one that runs. Every segment after it is skipped, even if it would also have matched.
- A condition compares one field to one typed value, using an operator: equals, contains, exists, greater/less than, between, or a tag check such as has any, has all or has none.
- Capital letters and spaces at either end are ignored, so
VIPandvipcount as the same tag. - Almost every field is the value the run captured when its trigger fired, or that a later step wrote into it. It does not re-read the database the moment the Condition step runs.
- contact.marketing_consent is the one exception: it is re-read from the contact's current record immediately before the check.
- So a customer who changes their answer during a wait is judged on the fresh answer, not a stale snapshot.
- If a field is missing — the trigger that started this run never set it — it reads as not present. Equals and contains do not match; exists is false and not exists is true.
- A Condition step where nothing matches simply takes None and carries on — nothing else needs to run first.
- The same logic also runs as a plain two-way branch action — all conditions must pass, Then or Else — an older step type with no entry of its own in Add Steps.
- It still exists in the workflow and can appear on a canvas the AI builder wrote, or one built before Condition existed.
- There is no way to add a fresh one from Add Steps — Condition is what an operator always gets there.
When it fails
- A Condition step cannot fail the way a send or a lookup can — it always resolves to some segment, even when that segment is None.
- There is no error state to read for it in the Activity tab on its own.
- If a condition's own check breaks unexpectedly — an earlier step saved something in an unexpected format, for instance — that one segment is treated as not matching, not as stopping the run.
- Checking continues on the remaining segments, so the step still resolves to whichever one matches, or to None if none do.
Limits
- A field written straight to the database — a tag, a saved contact field, a lifecycle stage — is not refreshed once the run has its own copy of it.
- contact.marketing_consent is the one exception: it is always read live.
- A tag added by an earlier step in the same run is not visible to a later Condition step, because tagging writes straight to the contact's record.
- A field a step writes directly into the run itself — an HTTP Request's saved response, a Randomizer's
split.lane, an answered question — has no such lag. - It is visible to a later Condition step in the same run the moment it is written, because those steps write into the run's own data, not the database.
- Saving refuses more than 12 segments, or more than 10 conditions on one segment.
- Configure step itself does not stop you adding more than either while you build — only saving does.
- A Condition step only chooses a segment — it sends nothing to the customer and changes nothing about the conversation by itself.
- Whatever effect a segment has comes from the steps placed inside it.
- Reordering or deleting a segment changes which contacts take it on every future run, but does not touch anything about a run already in progress or finished.
Best practices
- Put the narrowest, most specific segment first — the first match wins.
- A broad segment placed early can quietly take contacts meant for a more specific one further down.
- Give every segment a real label once there is more than one — Segment 2 tells nobody, months later, what that segment was for.
- Leave None with something in it, even a single tag, so a contact matching nothing is still visible later, not quietly dropped from the workflow.
Use cases
- A segment for Contact lifecycle stage equals Hot Lead routes to a priority path; every other lifecycle stage falls to None and gets a standard reply.
- One segment checks contact.marketing_consent equals true, for contacts who agreed; the other catches everyone else — so a chase still respects a withdrawal made mid-wait.
- A segment checks an HTTP Request step's saved status field, branching on whether a courier lookup succeeded, with a fallback segment for a failed or empty response.
FAQ and troubleshooting
- What happens if two segments could both match the same contact?
- Only the first one, in the order they are listed. Reorder the segments to change which one wins.
- Does a field I never set for this trigger just fail the condition?
- It reads as not present — an “equals” or “contains” condition on it does not match, and an “exists” condition on it is false.
- I see a “branch” step type mentioned in places — is that the same as Condition?
- It is the same all-conditions logic with only two paths — Then and Else — and no entry of its own in Add Steps. You cannot add a fresh one there; Condition is what you always get.
Reading this with an AI assistant? Plain Markdown version.