Conditions and paths

A connection can carry conditions: rules that must match for the run to continue along it. With conditions, one workflow can do different things for different cases, such as messaging hot leads straight away and saving the rest for later.

In the course

• VCcourse → Exactly matches → JEE sends JEE enquiries to Amit. Lesson 2: Send each student to the right counsellor →
• SRbudget → (Number) Greater than picks the premium brochure. Lesson 2: The right brochure for the right budget →

Add conditions to a connection

1. Double-click the connection (the line between two steps). The Path conditions dialog opens. It reads Choose when data should continue along this connection. All conditions must match.
2. Click Add condition.
3. In Field or mapped value, pick the data to check (click Map to choose from earlier steps).
4. Choose an Operator, such as (Text) Contains.
5. Fill Compare with, for example price.
6. Click Save conditions. The connection now shows a filter label instead of Always.

autoappy.com/workflows/…Sample data

Every condition on a connection must match (AND).

×

Branching: one step, several paths

To branch, connect one step to two or more next steps, and give each connection its own conditions. For example, after the trigger:

• path A: message → (Text) Contains → price → send the price list on WhatsApp,
• path B: message → (Text) Does not contain → price → add to the CRM for a call.

Every path whose conditions match continues, so make your rules exclusive if only one should run.

All conditions must match

Conditions on one connection are combined with AND. For “this or that”, use (Text) Is in with a list of values, or draw two connections (one per rule) into the same next step and set that step to On the first active path (below).

When paths meet again

If a step has more than one incoming path, choose how it waits (in the step’s settings):

• Wait for all paths (default): run once every active incoming path has finished.
• On the first active path: run as soon as one incoming path arrives.

Operators

Group	Operators
Text	Contains · Does not contain · Exactly matches · Does not exactly match · Starts with · Does not start with · Ends with · Does not end with · Is in · Is not in · Not empty
Number	Greater than · Less than
Date/time	After · Before · Equals
Boolean	Is true · Is false
Existence	Exists · Does not exist
Type	Is Array · Is Object · Is String · Is Number · Is Boolean · Is Array or Object

Text comparisons work on the value as text. For numbers (such as an order total), use the Number operators so that 100 is greater than 25.

When a step is skipped

In History, a step that didn’t run because a condition didn’t match is listed under Steps without results. That’s expected, not an error.

Test, go Live, pause

Run history