Automation Flows
The Automation Flow allows you to create automatic sequences of actions within the platform, organizing customer communication in an intelligent, scalable, and standardized way.
It can be used to send automatic messages, route to departments, apply tags, update custom fields, integrate with channels such as WhatsApp and Instagram, among other actions.
π What is an Automation Flow?
It is a visual structure (in block format) where you define:
Triggers (when the flow starts)
Conditions (decision rules)
Actions (what the system should execute)
Logical and control blocks
It works like a βdecision mapβ, allowing you to create personalized journeys for your contacts.
π What is it for?
You can use the Automation Flow to:
Initial automatic support
Automatic distribution by department
Application of strategic tags
Updating custom fields
Sending messages outside business hours
Lead qualification
CRM integration
Contact nurturing
Lead volume control
βοΈ How to access
You can access it in two ways:
Menu >> Relate >> Automation Flow
or
Type Automation Flow in the field Find services.
βΆοΈ Ways to start a Flow
There are several ways to start an Automation Flow, such as:
Segment
Manually
Via automation (SAC, CRM, Chatbot, Extra Webhook Actions and Form)
π To learn about all the available ways, access the specific article here:
Automation Flow - Triggering Methodsπ Where can the Flow run?
The Automation Flow can act directly in the following modules:
Contact
Tasks
Opportunities
Support tickets
To correctly define where the flow will be executed, we use the Automatic Selector, which determines the context of the automation.
π Learn more about how to configure the Automatic Selector in this article:
Automatic Selectorsπ§© Flow Structure
1οΈβ£ Entry Trigger
Defines when the flow will start.
2οΈβ£ Conditions (If / Then)
Allow branching in the flow.
Example:
If message contains βbudgetβ
If channel is WhatsApp
If contact already has a certain tag
If custom field has a certain value
π Conditionals with AND and OR
Within the Automation Flow, you can combine multiple conditions using the logical operators AND and OR.
Understanding the difference between them is essential to create correct rules.
πΉ Conditional with AND
The condition will be true only if ALL rules are met at the same time.
In other words, everything must be true for the flow to proceed.
π Example:
If:
Channel is WhatsApp AND
Message contains the word βbudgetβ
π The flow will only continue if both conditions happen together.
If only one of them is true, the flow will not follow that path.
πΉ Conditional with OR
The condition will be true if at least one of the rules is met.
In other words, one condition is enough for the flow to proceed.
π Example:
If:
Message contains βbudgetβ OR
Message contains βpriceβ
π The flow will continue if the customer writes any of these words.
π― Practical comparison
Situation
Result with AND
Result with OR
Two true conditions
Executes
Executes
Only one true condition
β Does not execute
β Executes
None true
β Does not execute
β Does not execute
π§ When to use each one?
Use AND when:
Need more specific rules
Want to avoid improper executions
Are qualifying leads with multiple criteria
Use OR when:
Want to expand possibilities
Work with word variations
Are creating more flexible filters
π οΈ Combined example
You can also mix rules.
Example:
Channel = WhatsApp
AND
Message contains βbudgetβ
OR
Message contains βproposalβ
In this case: The channel must be WhatsApp AND, within that, it can contain βbudgetβ or βproposalβ.
This allows you to create smarter and more strategic flows.
3οΈβ£ Actions
They are the tasks performed automatically:
Send message
Send template (when necessary within the 24-hour WhatsApp window)
Apply or remove tag
Change department
Update custom field
Close support ticket
Assign owner
π§ Special Flow Blocks
In addition to the standard actions, the Automation Flow has strategic blocks that increase the control and intelligence of the journey:
πΉ Field Value
Allows you to check or use the value of a custom field as a condition in the flow.
Example:
If the field Client Type is βActiveβ, proceed to priority support.
If the field Interest is βPremium Planβ, route to the specific sales team.
πΉ Switcher
Used to distribute support interactions alternately between users or teams.
Example:
Automatically alternate between salespeople A, B and C.
Distribute leads evenly (round-robin model).
This prevents overload on a single agent.
πΉ Time Limiter
The Time Limiter controls the flow execution volume over time.
A time limiter can:
Delay the passage of Leads
Allow only a limited number of executions
Release new executions every X hours or X days
Practical example:
Allow only 10 leads per day for a certain salesperson
Release 5 opportunities every 2 hours
Control distribution to avoid an excess of simultaneous demands
This block is ideal for:
βοΈ Control lead volume βοΈ Avoid team overload βοΈ Create a strategic distribution cadence βοΈ Maintain operational balance
β° Automation and the WhatsApp 24-hour Window
When using the WhatsApp channel, it is important to remember:
Within the 24-hour window: it is possible to send free-form messages.
Outside the window: it is mandatory to use Approved Message Template by Meta.
Otherwise, sending will be blocked.
π οΈ Practical example
Scenario: Customer sends a message via WhatsApp with the word βbudgetβ.
Flow:
Trigger: New message received
Condition: Message contains βbudgetβ
Action:
Apply tag βBudget Interestβ
Check Field Value βRegionβ
Use Switcher to distribute between salespeople
Apply Time Limiter to control daily volume
Send automatic message
Route to Sales Department
Result: service organized automatically, with intelligent distribution and volume control.
π― Best practices
βοΈ Start with simple flows βοΈ Name each step well βοΈ Use tags to organize your database βοΈ Always test before publishing βοΈ Avoid very long and confusing flows βοΈ Document the internal logic
Last updated
Was this helpful?