Anatomy of a workflow
Every automation platform draws workflows differently, but underneath the canvas the parts are the same four. A trigger is the event that starts a run: a form submission, a page view, a score crossing a line, a field changing in the CRM, a date arriving. A condition decides whether this particular contact should continue: is the country in scope, is the consent flag set, has the person already bought, is a salesperson already working the record. An action is what the workflow does: send an email, wait a period, update a field, assign an owner, add to an audience, create a task, send a message. An exit is how the run ends, and it is the part most teams forget to design: the goal was reached, a disqualifying event occurred, the sequence ran out, or a more important workflow took over.
| Part | Question it answers | Typical examples | Common failure |
|---|---|---|---|
| Trigger | What starts a run? | Form submitted, score threshold crossed, deal stage changed, cart abandoned | Fires on the wrong event, or on every edit of a field |
| Condition | Who should continue? | Consent recorded, region in scope, not a customer, no open deal | Missing suppression; the condition is checked once and never again |
| Action | What happens? | Email, wait, field update, owner assignment, task, message | Waits that ignore working days; actions with no owner |
| Exit | When does it stop? | Goal met, reply received, unsubscribe, higher-priority workflow entered | No exit, so the sequence finishes regardless of what the person did |
The reason to learn the anatomy rather than the product is that every workflow problem is a problem in one of these four parts. A lead that received a sales email after buying had a missing condition. A contact who got two sequences at once had an exit that never fired. Thinking in trigger, condition, action and exit also makes workflows reviewable by someone who was not in the room when they were built, which is the basis of the governance guide. An AI agent that decides its own steps has no such fixed anatomy to review, which is why rule-based automation vs AI agents recommends keeping sends, spend and record changes in workflows like these.
The core guides
Lead scoring — how to build a score from fit and intent signals, weight and decay the points, set thresholds that match the pipeline's stage definitions, subtract for disqualifying signals, and calibrate the whole thing against what actually closed. Scoring is the workflow that decides who is handed to sales and who stays in nurture.
Nurture sequences — the design of the sequences themselves: goals by stage of the FunnelModel of the customer journey stages., entry and exit rules, content that moves a lead forward rather than merely filling a slot, timing and channel choices, and how sales is involved before and after the hand-off. The welcome series tutorial in the email section owns the first-contact flow; nurture picks up after it.
SMS and WhatsApp automation — messaging channels under automation: the consent and opt-out rules documented by the platform and regulators cited there, message templates and approvals, the use cases that suit an interruptive channel, and quiet hours and frequency.
Automation governance — the routine that keeps a growing set of workflows safe: an inventory, naming and ownership, change control and testing, frequency and suppression rails, retention rules and an audit cadence.
The data these workflows read and write lives in the CRM, which the CRM section covers; email-specific flows such as abandoned cart live in the email automation section. The CRM and automation pillar shows how the sections fit together.
Further guides
Further guides each design or build a single workflow on that anatomy:
- Sales alerts from marketing activity — the signals worth an alert, who gets it, real-time or digest, alert fatigue, consent and measuring follow-up.
- Building a closed-won workflow — a tutorial for what runs when a deal is won: customer stage, prospect suppression, onboarding hand-over, team alerts and outcomes sent to ads.
- Automating quote follow-ups — a tutorial for following up quotes and estimates: a quote stage, messages that answer objections, consent, exits on reply or decision, and lost reasons.
- Standardising CRM field values with workflows — a tutorial for country values, job titles mapped to roles, company names, rules that avoid loops, review queues and backfills.
- Automating lifecycle stage changes — a tutorial for setting every stage by rule: one writer per stage, a date stamped on entry, forward-only moves with named exceptions, recycling, returning enquiries, imports and syncs kept out, and a backfill.
- Pausing marketing to customers with an open issue — a tutorial for a hold with a reason during a complaint, dispute or bereavement: who sets it, every send and audience checked, service messages kept and a release rule with an owner.
Workflows worth building first
Teams new to automation tend to start with the most ambitious workflow they can imagine and stall. The better order is by risk and by how much manual work each one removes.
Lead routing. When a form is submitted, check consent and region, assign an owner, create a task and notify them. It is simple, it removes the "who has this lead?" problem for good, and it forces the team to agree the fields and stage definitions that every later workflow depends on.
A single welcome or onboarding sequence. One trigger, a short series, one exit on purchase or reply. It teaches the platform's wait, condition and exit behaviour on a flow where mistakes are cheap.
Suppression and hygiene. Workflows that set a do-not-contact flag on unsubscribe or bounce, move dormant contacts into a low-frequency tier and remove customers from prospect sequences. These are unglamorous and they prevent most of the incidents the governance guide describes. The closed-won workflow does the customer removal at the moment a deal is won, together with the onboarding hand-over and the outcome sent to the ad platforms.
Scoring, then nurture. Only after the above are stable. Scoring without agreed stages produces numbers nobody trusts; nurture without suppression produces complaints. Both guides assume the foundations exist. Sales alerts belong in the same phase: the score hands over new leads, while an alert reacts to a single event on a record a seller already owns.
Quote follow-ups, where the business sends quotes. A quote is the point where a buyer has asked for a price and the business has done the work to give one, and it is where follow-up often stops. Automating quote follow-ups puts a task with the owner before any automated message and exits on reply, acceptance or decline.
A good test for "first" is whether sales and marketing would both notice if the workflow stopped. RoutingRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source. passes that test; a birthday email does not.
Testing before switching on
A workflow is code that runs against real people, and it deserves the same discipline. Four checks catch most problems.
Walk the paths with test contacts. Create contacts that match each branch: consented and not, customer and prospect, in and out of region. Enrol them, and read every message they receive in the order they receive it, including the waits.
Check the enrolment count before activation. Most platforms show how many existing contacts meet the trigger. A nurture meant for new leads that would enrol the entire database on activation is a common and expensive mistake; decide explicitly whether existing contacts should enter.
Confirm the exits fire. Trigger the goal event on a test contact mid-sequence and confirm the remaining steps are skipped. Do the same for unsubscribe and for entry into a higher-priority workflow.
Define the measure before launch. A workflow with no KPIA metric tied directly to an objective. cannot be judged later. For a nurture it is progression to the next stage; for routing it is time to first touch; for a cart flow it is recovered orders and the resulting conversion rate (CVRShare of visits or clicks that convert.) of enrolled contacts against a holdout.
A routing workflow tested before launch
A software company builds a routing workflow: on demo-request form submission, check that the consent checkbox is true and the country is in one of its two sales regions, assign a round-robin owner, create a follow-up task due in 1 working day and send an internal notification. Before activation the team creates 6 test contacts covering every branch, including one with consent false and one from an unsupported country, and submits the form as each. Two defects appear: the task is due in 1 calendar day, so Friday requests fall due on Saturday, and the unsupported-country contact is routed anyway because the condition checked the state field rather than country. Both are fixed. The platform's enrolment preview shows 1,840 historical submissions would otherwise have entered on activation; the team switches historical enrolment off and launches with a backlog of 0.
Common workflow problems
| Symptom | Usual cause | Guide |
|---|---|---|
| Sales ignores the leads marketing hands over | Score thresholds not tied to stage definitions; fit and intent mixed into one number | Lead scoring |
| Leads stall in nurture and never progress | No goal per stage; content fills slots rather than answering the next question | Nurture sequences |
| Complaints or carrier filtering on SMS | Consent not recorded for the channel; opt-out keywords unsupported; sends outside daytime hours | SMS and WhatsApp automation |
| A contact receives several sequences at once | No priority or mutual-exclusion rule; exits not designed | Automation governance |
| Nobody knows what a workflow does or who owns it | No inventory, naming convention or change log | Automation governance |
| Customers receive prospect messaging | Missing customer suppression condition at entry and during the run | Nurture sequences, Automation governance, Building a closed-won workflow |
| Prospecting ads keep chasing people who already bought | Audiences and exclusion lists not refreshed when a deal is won | Building a closed-won workflow |
| Sellers ignore marketing alerts | Alerts on every click; real-time for everything; sent to a fixed list rather than the owner | Sales alerts from marketing activity |
| Quotes go quiet and close with no reason recorded | No task for the owner; chasers with nothing new to say; no lost reason on expiry | Automating quote follow-ups |
| Routing and reports split one value into many spellings | Free text from forms, imports and lead forms; no standard list or review queue | Standardising CRM field values |
| Stage reports skip stages, or customers still show as leads | Stages changed by hand or by several writers; no date recorded on entry | Automating lifecycle stage changes |
| A customer with an open complaint keeps receiving promotions | No hold on the record; sends and audiences check permanent suppression only | Pausing marketing to customers with an open issue |
Most of these are visible in the first week after activation if someone is looking. The governance guide's audit routine makes someone look on a schedule rather than when a complaint arrives. A workflow that has already stopped enrolling or acting on records has its own diagnosis in the troubleshooting section, which starts from one record's enrolment history.
