Getting Started with Marketing Automation: Build Your First Workflow
Published:
Last Updated:
Category: Marketing DX, Marketing Glossary
Authors: Shusaku Yosa
Start marketing automation with one customer need and an operating process. Before selecting a long feature list, define who enters, what starts the workflow, what stops it, and who handles the next action. Those decisions determine the data and capabilities you actually need.
Understand MA, CRM, and sales automation
The categories below are a practical division of responsibilities. Products overlap, so the label on a system does not establish its complete scope.
Category | Main working role | Example information |
|---|---|---|
Marketing automation | Execute marketing actions under defined conditions | Contact eligibility, request time, and workflow state |
CRM | Manage relationships with prospects and existing customers | Identity, owner, and interaction history |
Sales force automation | Manage sales activities and opportunities | Opportunity stage, next action, and response |
HubSpot's CRM explanation includes potential as well as current customers. CRM is not restricted to post-sale work. Decide where each important field is maintained, which system supplies the current value, and who resolves conflicting or duplicate records.
Choose one trigger and one customer problem
In a fictional business service, people request an evaluation guide but then struggle to understand implementation requirements. The aim is to help them evaluate fit and find a consultation route, rather than simply generate more messages.
Enter people whose guide request is complete and whose contact eligibility has been checked. Exclude internal tests, people already in an active sales process, and people who have opted out. Keep different people at one company distinct, while preventing duplicate records for one person from causing repeated messages.
Use one-to-one relationship design to consider relevance. If the purpose is helping someone use a newly created account, define that separately as customer onboarding instead of combining it with a prospect education workflow.
Document entry, waiting, stopping, and handoff
Stage | Condition | Action | Exit or branch |
|---|---|---|---|
Entry | Request completed and eligibility checked | Provide the requested guide and record the outcome | Do not enter excluded contacts |
Wait | Three days after the first message, for this example | Recheck current conditions before sending | Stop education after an opt-out or sales engagement |
Follow-up | Still eligible, with no consultation request | Offer comparison criteria and a consultation route once | Do not treat an open as confirmed purchase intent |
Handoff | The person requests a consultation | Assign an owner and response deadline | Confirm that the owner accepted the task |
End | Planned actions finished or a stop rule applied | Record the reason | Apply a defined re-entry rule to future requests |
A condition checked at entry may become outdated during a wait. Recheck opt-outs and sales status before the next action. Set a re-entry policy for repeated requests: a different guide might justify a new workflow, while the same request could be suppressed for a defined interval. Choose that interval for the customer's situation, not as a universal benchmark.
Sending a sales notification does not prove that someone will respond. Specify an alternative owner for absences, a place for the response record, and a way to detect unaccepted tasks.
Test exceptions before expanding
Test more than a successful single request. Record the expected message count, stop reason, and handoff result for each case:
- A person submits twice or has duplicate records.
- An opt-out or active opportunity arrives during the wait.
- Contact eligibility is missing or updates arrive late.
- A delivery fails and the process is retried.
- The assigned salesperson is unavailable.
Define how unknown states are handled instead of relying on a system default. For example, hold an action when eligibility cannot be confirmed and assign someone to resolve it. Establish who can pause the workflow after a sudden increase in sends, complaints, or duplicates.
Measure people and outcomes with defined windows
Separate eligible entrants, successfully contacted people, completed consultations, and confirmed commercial outcomes. Multiple clicks by one person are still one person in a person-based measure. An open signal does not establish that someone read the content or intends to buy.
A useful operational definition could be consultation completions within fourteen days divided by entrants whose full fourteen-day window has elapsed. Explain exclusions and show the total eligible population alongside any delivery-only rate. For small samples, keep the numerator and denominator visible.
Changes in traffic mix, sales response, or other campaigns can affect results. Record those changes and avoid attributing every difference to automation. KPI progress and recovery provides a way to evaluate targets and feasible next actions.
Stabilize one workflow before adding branches
Run a workflow that its owners can explain from entry to exit. Review unresolved records, duplicate actions, delivery problems, and customer questions each week. When adding a branch, add its owner and exception tests too. A clear, maintained process makes expansion easier to assess than a large collection of unowned triggers.
