Marketing Automation Workflows: A Library of Patterns for Capture, Nurture, Reactivation and Post-Sale

Marketing automation workflows are rule-based sequences that act on a contact, company or deal record without a person pressing send: they enrol the record when a trigger fires, run actions such as emails, property updates and tasks, and unenrol it when a condition is met. The tool is not the interesting part. The rules are.

HubSpot's documentation describes the parts plainly: enrolment triggers decide who goes in, actions decide what happens, and unenrolment settings decide who comes out. Other platforms use different names for the same three pieces. If you can write a workflow as three sentences on paper (who enters, what happens, who leaves), you can build it in nearly any tool. If you cannot, the tool will not rescue it.

HubSpot offers event-based triggers (such as a form submission), filter-criteria triggers (a property reaches a value), schedule-based triggers, webhook triggers (which its documentation limits to Data Hub) and manual enrolment. By default a record enrols only the first time it meets the trigger, and re-enrolment is something you switch on deliberately. That default protects you from sending the same welcome series every time a contact fills in another form, so switch re-enrolment on only where repeating the sequence makes sense, such as a renewal reminder.

Exit rules do more to protect your reputation than any email copy. A workflow can unenrol records through goal criteria and suppression segments: HubSpot's documentation says a contact who is already enrolled and joins a suppression segment is removed immediately and does not receive further actions. Write both rules before you launch. Typical exits are a booked meeting, a closed deal, a reply, an unsubscribe, or a status that makes the sequence irrelevant.

The first pattern runs the moment someone raises a hand. The trigger is a form submission or a booked-meeting event. The actions are to set the lifecycle stage and lead source, assign an owner by a simple rule (territory, service line or round robin), create a task for a human follow-up with a time limit, and send a short confirmation that says what happens next. The exit is a logged sales activity or a meeting booked.

The measure of success is time to first human contact, not email opens. Illustrative example: a services firm routes enquiries by service line. A contact submits the contract-review form, the workflow assigns the contract team's queue, creates a task due within the hour during working time, and sends a plain confirmation. If the task is still open at the deadline, a second action notifies the team lead. The fallback owner matters: a record that matches no rule needs a named person, or it will wait unseen.

Nurture serves people who are interested but not ready. Its trigger is a content or interest signal, its actions are a few relevant emails spaced out, and its exit is a sales conversation or a clear disinterest signal. Length is the typical mistake. Five useful messages beat fifteen, and a nurture track with no end becomes a newsletter in disguise. Reactivation targets dormant contacts and former opportunities: the trigger is a period without activity, the actions are one or two direct messages and a final chance to stay, and the exit is either re-engagement or removal from mailing. The removal step protects deliverability, which our email deliverability guide covers.

Post-sale workflows get the least attention and often earn the most. Triggered by a closed deal or a completed purchase, they handle onboarding messages, a check-in task for the account owner, a review or feedback request at a point you choose, and renewal reminders that use schedule-based enrolment from a date property. The post-sale pattern also acts as a suppression feeder: closing a deal should immediately remove the contact from every prospecting sequence.

Build it paused, enrol a few internal test records, and trace each branch with a record that should take it. Check what your platform does with timing: delays, send windows and time zones can make a sequence fire at midnight or collapse several emails into one morning. Then check suppression by enrolling a test record that should be excluded, such as an existing customer or an unsubscribed address, and confirming that nothing is sent.

Write down a test plan as a short table before you start: one row per branch, the record you will use, the result you expect and the result you saw. Illustrative example: a lead-routing workflow with three territories and a fallback owner has at least four branches, plus a suppression case, so five test records. The exercise feels pedantic until the day the fallback branch turns out to be empty and a whole region's enquiries sit unassigned. It also gives whoever inherits the workflow something to rerun after changing it.

Launch to a small slice first if the platform lets you. HubSpot gives you options for manual enrolment as well as filters, which makes a small first batch practical. Read the first week of enrolments by hand: are the right records going in, and are any going in twice? HubSpot also publishes troubleshooting guidance for records that fail to enrol, which is worth reading before you spend an afternoon guessing.

A live workflow needs an owner, a review date and a short log of changes. HubSpot keeps enrolment history and action logs for a limited period (its documentation gives 90 days for action logs and six months for enrolment history), so review them before the data ages out and look for records waiting at one action. Review three things on a schedule: how many records entered and left, whether the goal is being met, and whether any action has started to fail. A monthly review is enough for stable workflows; look weekly during the first quarter.

Treat changes with the same care as the first build. Editing a live workflow may alter what happens to records already inside it, so check how your platform behaves and note in your change log what you edited, when, and whether records already enrolled were affected. A common slow failure is a property rename or a deleted list that a workflow still depends on: the trigger quietly stops matching anyone, and the first sign is a quiet month. A monthly check that every live workflow has enrolled at least one record recently catches this early.

Who this is not for: if your database is a few hundred contacts and one person sells to them, a workflow library is more machinery than the job needs. A saved list, a task reminder and a good template will serve you for longer. Automation earns its place when the same action must happen reliably, many times, without anyone remembering.