Automation
Automation lets your business react to events without doing everything by hand. A workflow is a set of rules: when something happens (a trigger), optionally check some conditions, then run one or more actions.
Verified from product architecture
This article describes workflows conceptually. The exact triggers, actions, and builder controls available in your workspace depend on your plan and the current version of the application.
The building blocks
- Triggers — what starts the workflow, such as a new conversation, a new lead, or a tag being added.
- Conditions — checks that decide whether to continue, for example “only if the customer has a certain tag”.
- Branches — different paths depending on the conditions, so one workflow can handle several cases.
- Delays — wait a set time before the next step (for example, follow up after a day).
- Actions — what the workflow does, such as sending a message, adding a tag, assigning a teammate, or updating a customer.
Execution
When a trigger fires, WazBot runs the workflow step by step. A single workflow can touch several areas — it might message the customer, update their CRM record, and route the conversation to a team.
Versioning and safe re-runs
As you edit a workflow, the application keeps your changes consistent so in-flight runs behave predictably. Well-designed automations are also idempotent where it matters — meaning a step that happens to run twice should not create duplicate side effects such as sending the same message repeatedly.
Availability
The set of triggers, conditions, and actions you can use depends on your plan. Some advanced steps may only be available on higher plans or when related features (such as campaigns) are enabled.
How automation relates to other areas
- Customers & CRM — workflows can tag, qualify, or update customers.
- Conversations — workflows can respond to or route chats.
- Campaigns — automation can follow up after a broadcast.
Related articles
Was this article helpful?