Automation Builds
Implementing marketing automation from an approved campaign plan
Turn an approved campaign plan into workflow rules, checks and a controlled launch, with clear ownership for exceptions and results.
An approved campaign plan becomes a working automation when its audience, actions, timing and exclusions are written as checkable rules. Start from the approved version and write a workflow specification before configuring the platform.
Record the decisions the workflow must follow
Record the campaign ID and approved version. Name the audience, channel, creative, offer, send window and exclusions. Identify who can change each item and which changes need renewed approval. Resolve any open decision with the campaign owner before building that branch.
Describe the journey in plain language. Use this pattern: when this happens, check these conditions, take this action, then record the outcome.
Campaign decision / Workflow specification
- Who enters
- Start event or scheduled selection, required data and eligible audience
- Who stays out
- Suppressions, prior completion and other exclusions
- What happens
- Approved message or internal action, with its version
- When it happens
- Timezone, delay, send window and expiry
- What stops it
- Objective reached, withdrawal, cancellation or exception
- Who responds
- Owner for failed, ambiguous or overdue work
Map the specification to workflow objects
Choose the workflow object type that matches the records in the approved audience. HubSpot supports workflows for different object types, but some types have specific subscription requirements; quote- or contract-based workflows, for example, require particular subscriptions. Confirm the required access before building, rather than discovering a limitation at launch.
In the workflow editor, add the specified actions and workflow settings. Actions can include sending a marketing email or assigning an enrolled contact to a user; a workflow can also update an associated record, such as the contact's company.
For a larger workflow, use the editor's minimap to review its overall architecture. Check that the branches and actions there match the approved workflow specification, not merely a technically possible sequence.
End-to-End Workflow Lifecycle in HubSpot (Australia)
- PlanApproved campaign with defined audience, message, timing, and exclusions.
- DesignTranslate plan into workflow specification using plain-language logic.
- BuildConfigure triggers, conditions, actions, and exits in HubSpot workflow editor.
- TestRun simulated enrolments using HubSpot’s built-in testing tool.
- Review & ApproveConfirm access rights and ownership of exceptions and outcomes.
- LaunchActivate workflow with monitoring owner assigned.
- ReconcileCompare actual results against plan post-campaign; document gaps.
Build the complete path
Define how the workflow starts and how the complete path runs. In the workflow editor, add the enrolment triggers and configure re-enrolment and unenrolment settings.
A form submission, a property meeting a condition and a scheduled selection are different starts. HubSpot supports manual enrolment, enrolment based on a set frequency, or specific enrolment triggers, with availability and actions subject to account and subscription limits. Check that the chosen platform can express the approved rule.
Put eligibility checks before consequential actions. Check again after a delay if eligibility could change. Where Australian spam rules may apply, include a compliance check before sending and consult current ACMA guidance.
Give each branch a result, including a route for missing or conflicting information. Assign an owner to decide an ambiguous case. Keep decisions that require judgement with an authorised person.
HubSpot Workflow Start Triggers: Options and Limitations
- Form SubmissionTriggers enrolment when a contact submits a form; requires form setup and property mapping.
- Property ConditionEnrols contacts when a specific property meets a condition (e.g., region = 'NSW'); subject to account limits.
- Scheduled SelectionRuns at set intervals (daily, weekly); useful for recurring campaigns or lead nurturing.
- Manual EnrolmentAllows staff to add contacts manually; limited to users with appropriate permissions.
- Re-enrolmentMust be explicitly configured; otherwise, completed records do not re-enter.
Decide when records leave or return
Specify what happens when a record reaches the campaign objective, becomes ineligible or passes the useful send window. Decide separately whether a later event should start another run. Repeated submissions and scheduled checks can otherwise trigger an unintended action.
In HubSpot, re-enrolment must be configured. A previously completed record may not enrol again if re-enrolment is off. The launch review also offers a choice about records that already meet the criteria.
Check the configuration against the plan
Write expected outcomes for controlled scenarios: an eligible record, an excluded record, a missing field, eligibility changing during a delay and a repeated trigger. State both the action that should happen and the action that must not happen. Compare the configured audience and creative with the approved versions.
Review the configured route through branches. Compare it against the expected outcomes.
Before activation, assign a monitoring owner. Check the treatment of already eligible records, the timezone, the expiry rule and the first run's expected volume. Record the campaign and workflow versions together.
Pre-Launch Workflow Validation Checklist
- Eligible record scenarioShould trigger correct action and follow approved path.
- Excluded record scenarioMust not be enrolled or actioned; check suppression rules.
- Missing field scenarioWorkflow should handle gracefully with fallback or error routing.
- Eligibility changes during delayRe-check eligibility after delay to prevent invalid actions.
- Repeated trigger scenarioAvoid duplicate actions via re-enrolment settings.
- Compliance with Australian spam rulesInclude opt-out mechanism and consent check before sending.
Include a launch workflow test
HubSpot provides a workflow test that simulates how a record enrols and moves through the workflow. Use it as one launch check against the current workflow version, alongside the controlled scenarios above; if a connected destination matters, arrange a separate controlled check there before launch.
Release and reconcile
Activate the workflow after reviewing its positive and negative paths. Inspect early enrolments, exclusions and action outcomes against the specification. If an external result is uncertain, pause further affected actions while it is investigated.
After the campaign window, compare starts, completed actions, exceptions and the agreed success measure with the plan. Record any gap for correction.
Key Compliance & Performance Metrics for Australian Marketing Automation
- ACMA Spam ComplianceMandatory opt-out link and consent verification required for all emails sent in Australia.
- CRM Integration PlatformsSalesforce and HubSpot lead in CRM-integrated marketing automation for Australian SMEs.
Confirm build and publish access
In HubSpot, creating or editing a workflow requires Edit permissions for workflows or Super Admin permissions. Publishing requires Publish permissions. Confirm that the people responsible for configuration and release have the relevant access before the planned launch.
HubSpot workflows can be created from scratch. They can also be created from a template or with AI.
In this guide
- Turning a campaign brief into trigger rulesTranslate a campaign brief into a clear start, eligibility conditions, exclusions, repeat rules and testable edge cases.
- Choosing what should remain manual in a marketing workflowDecide which marketing workflow steps need human judgement, how to route them and when automation must wait.
- Defining success before automating a marketing taskSet a measurable task outcome, denominator, evidence source and review rule before building a marketing automation.
