Workflow process automation means a set of steps that runs by itself when something happens: a client books, a form arrives, a deal changes stage. Done well, the same thing happens every time, whoever is in the office. This article covers the mechanics. It explains the four building blocks every workflow in the platform uses, and walks through building your first one from trigger to publish, so you understand what you are switching on before you automate anything important.
The four building blocks
Every workflow is made of the same four parts.
A trigger is the event that starts it. Examples: a form is submitted, a contact gets a tag, an appointment is booked, an opportunity moves to a stage.
Actions are what the workflow does: send an email or SMS, create a task, update a field, move an opportunity, notify a colleague.
Waits pause the workflow for a set time or until a date, so a follow-up goes out three days later rather than instantly.
Conditions split the path. If the contact has a phone number, send an SMS; if not, send an email.
Understand these four and you can read any workflow, including ones somebody else built.
Before you start
Check that you have:
- Permission to create and publish workflows in Automation.
- Email and SMS sending set up in Settings, so message actions can actually send.
- A test contact record using your own email and mobile number.
- A short process to automate first. A booking confirmation and reminder is ideal.
How to set it up
- Go to the Workflows area inside the Automation section.
- Click + Create Workflow.
- Pick a recipe or template if one is close to your appointment process, or start from scratch to build it yourself.
- Choose the trigger: an appointment booked on the calendar this process covers.
- Add the actions in order: the confirmation email, a wait until the day before, the mobile number check and a reminder on each branch.
- Click Save, then run Test Workflow with your test contact before you publish.
When the test run finishes, read the contact's history rather than trusting that the workflow looked right on screen. Check the confirmation carried the correct date and time, that the reminder fired on the branch you expected, and that nothing else was sent. Only then switch it on for real bookings, and tell the team which calendar it now covers.
What it is for in a company with stalled revenue
In a 60-person firm with flat turnover, the gap between what the company says it does and what actually happens is often filled by individual effort. When those individuals are busy, clients wait. Workflow process automation closes that gap for every step that does not need judgement.
It replaces manual reminders, copy-and-paste follow-ups, and the sticky note on a monitor. It also replaces the end-of-day check where a manager scans the CRM for anything missed.
Suppose the firm books 90 discovery calls a month and about 14 end in no-shows. It adds a confirmation, a reminder the day before and a second reminder an hour before. If no-shows then settled at around 6 a month, that would be eight more calls held every month from the same bookings. A three-message workflow like this is an afternoon's build. The figures are hypothetical.
Time it takes each week
Once live, a simple workflow needs almost no time. Check its history once a week for failed steps, which takes five minutes. Complex workflows with many branches need more checking, which is one reason to keep them short.
Automating a process that does not work yet. If the manual version loses clients, automating it loses them faster. Fix the process on paper first, then build it.
When not to automate
Leave steps that need judgement to people: pricing a complex proposal, handling a complaint, deciding whether a client is a good fit. Automate the reminder to do those things, not the thing itself.
Going further
Once you are comfortable with the basics, the guide to workflow automation examples shows patterns worth copying. If you are choosing between platforms rather than building, the guide to process workflow tools covers what to check. And once your workflows are live, the guide to business process optimisation explains how to audit them for drift and duplicate messages.
Troubleshooting
The workflow did not start
The trigger probably has a filter that excluded the contact, such as a specific calendar or form. Open the trigger and check its filters against the test case.
Messages went out but merge fields were blank
The contact is missing the field, such as a first name. Add a fallback value in the message, or a condition that checks for the field first.
The same contact went through the workflow twice
Check whether re-entry is allowed. For confirmations, allow it; for one-off welcome sequences, switch it off in the workflow settings.
Reminders went out at night
Waits count real time, including nights and weekends. Set the Time Window in the workflow's settings so messages only go out in working hours.
Frequently asked questions
Do I need coding skills to build a workflow?
No. Triggers, actions, waits and conditions are chosen from menus. Coding helps only for unusual integrations using webhooks.
Can one workflow trigger another?
Yes, usually by having the first add a tag or move a stage that the second listens for. Keep chains short so they stay easy to follow.
How do I stop a workflow for one contact?
Remove them from it on the contact record, or add a condition early in the workflow that checks a tag such as do not contact.