Conditional logic is a block that splits your flow based on a value: the button someone tapped, a variable stored earlier, or a field from an API response. You set a condition (“status is shipped”), connect the yes and no exits to different blocks, and the flow picks the right path by itself.
What you can decide with it
Anything the flow knows, you can test against. That turns a single flow into a conversation that runs differently for a new customer than for an existing one.
- Choices from buttons and list messages
- Variables you stored earlier in the conversation
- Fields from an API response, such as order status or stock
- Combinations: the customer is known and the order hasn't shipped yet
Keep it readable
Every condition branch is a branch you have to maintain. Two or three branches per flow is fine; if it gets out of hand, split it into several flows with a clear entry point.
Frequently asked questions
Can I combine multiple conditions?
Yes. You can chain conditions or test several fields at once, so a path is only taken when everything checks out.
What happens when none of the conditions are true?
Then the flow takes the default exit. Always fill that in with a friendly fallback, such as handing the conversation to a team member.
Can I test whether my conditions are right?
Yes. In test mode you see, step by step, which values are known and which path gets taken, so you find mistakes before your customers do.