Marketing automation
Send the next message because something happened.
I build marketing workflows around customer and lead data — connecting forms, CRM, email and other systems so communication and follow-up happen because of real behaviour, status or business rules.
Beyond scheduled email
Marketing automation starts with a trigger.
A campaign that goes out because it is Tuesday is scheduling. Marketing automation sends something, or does something, because a meaningful event happened: a form, a status change, a period of silence, new data from another system.
What follows the trigger is a workflow, not a single send. It can select an audience, check conditions, send a message, update the CRM, create a task, notify Sales, wait, branch, and stop once the goal is reached.
Possible triggers
- A form was submitted
- A lead entered a segment
- A lifecycle stage changed
- A meeting happened
- A customer became inactive
- A candidate reached a defined stage
- A Sales action changed CRM data
- New data arrived from another system
What the workflow can then do
- Select an audience
- Check conditions
- Send communication
- Update CRM data
- Create a task
- Notify Sales
- Wait
- Branch
- Stop when the goal is reached
The trigger, data and business rules matter more than the send button.
What it connects
From the first form to the next action.
A marketing workflow usually touches four kinds of systems. What each can do depends on the platform and the data available, so not every action is possible everywhere.
Capture
- Website forms
- Landing pages
- Newsletter forms
- Event registrations
- Capture contact information
- Record source and context
- Create or update CRM records
- Trigger the right workflow
- Route requests
CRM and customer data
- Contacts
- Companies
- Lifecycle stages
- Customer attributes
- Build segments
- Check status
- Personalise communication
- Exclude audiences it does not apply to
- Trigger lifecycle actions
Communication
- Marketing email
- Transactional email
- Follow-up
- Notifications
- Send relevant communication
- Sequence messages
- Branch on conditions
- Stop communication when appropriate
- Coordinate Marketing and Sales
Connected data
- APIs
- Operational systems
- Databases
- Webhooks
- Bring external attributes into the workflow
- Synchronise useful customer data
- Trigger communication from external events
- Send results back to other systems
- Extend the marketing platform where needed
In production
Connecting Marketing activity to Sales follow-up.
For Optimile and Mobiflow, HubSpot provides one Marketing and Sales environment across two brands. Website forms and requests feed HubSpot directly, segmentation can use the same CRM data Sales works with, and an incoming request becomes a lead with an owner in Sales and a follow-up task.
Marketing automation does not have to end with another marketing email. The useful outcome of a marketing workflow may be communication — or it may be a clear action for Sales.
Relevant parts of the implementation
- A CRM structure shared by Marketing and Sales
- Website forms and requests feeding HubSpot
- Contact and lead creation from incoming requests
- Marketing-to-Sales handover automation
- Round-robin Sales ownership and automatic follow-up tasks
- Transactional email within the HubSpot setup
- Foundations for lists, segmentation and reporting
- Sales onboarding
From website request to Sales follow-up
- 01 · CaptureA visitor submits a website request
- 02 · RecordCRM data is created or updated
- 03 · RouteThe lead is assigned to Sales
- 04 · Follow upA task gives Sales the next action
Segmentation
The workflow is only as useful as the audience logic behind it.
Before anything is automated, it has to be clear who should enter a workflow, and who should not. The data available differs per project, so segments are built from what actually exists and is reliable.
Segments may use data such as
- Country
- Language
- Customer or prospect status
- Lifecycle stage
- Role or function
- Product or service interest
- Previous activity
- Opt-in status
- CRM attributes
- Operational or customer data where available
A workflow may need to exclude
- Contacts who opted out
- Existing customers
- Contacts already handled by Sales
- Contacts in another active flow
- People who no longer meet the criteria
Good automation is often defined as much by who does not receive a message as by who does.
Lifecycle
Build communication around stages, not isolated sends.
Lifecycle automation follows a contact through a stage of the relationship rather than sending one-off messages. Which flows make sense depends on the business; these are common examples, not a standard package.
Examples of lifecycle flows
- New lead follow-up
- Nurture
- Post-meeting follow-up
- Onboarding
- Re-engagement
- Reactivating inactive customers
- Candidate re-engagement
- Event follow-up
- Transactional communication
What every flow needs
- Entry criteria
- Timing
- A message sequence
- Branch conditions
- Exit conditions
- Suppression rules
- Ownership
- A connection with the CRM state
Every flow needs a reason to start and a reason to stop.
Handover
Marketing automation should know when Marketing’s job is done.
Some workflows should not keep nurturing. When a contact is ready for a conversation, the workflow should hand the work to Sales and step back.
At Optimile and Mobiflow, an incoming request is assigned to Sales through round-robin and a follow-up task is created, so the next owner and the next step are clear. For the CRM side of these handovers, see CRM automation.
A handover can include
- Creating or updating the CRM record
- Assigning an owner
- Creating a task
- Notifying the responsible person
- Keeping the source and context
- Stopping conflicting Marketing communication where appropriate
The handover should make the next owner and next action explicit.
Architecture
The marketing platform does not need to do everything.
Three patterns cover most marketing automation. The HubSpot and n8n pages go deeper into each tool; for processes that are mostly operational, see business process automation.
- Native marketing automation
- Useful when the trigger, the audience, the communication and the conditions all live comfortably inside the marketing or CRM platform.
- Marketing platform + n8n
- Useful when external data is required, another CRM or system is involved, custom API calls are needed, files or documents need processing, or the logic crosses several platforms.
- Custom integration
- Useful when native connectors are insufficient, specialised application behaviour is required or a dedicated integration is more reliable.
Keep simple marketing logic simple. Add orchestration only when the process genuinely crosses systems.
Not every automated email is a marketing email.
Marketing communication includes newsletters, nurture, promotional follow-up and re-engagement. Transactional or service communication is triggered by an action or an operational process, such as a request or a status change.
The distinction matters in practice: the purpose differs, the audience rules differ, the sending infrastructure may differ and consent and suppression requirements may differ. The correct setup depends on the purpose of the message, the data involved and the applicable consent requirements; this is a practical distinction, not legal advice.
I have built both marketing and transactional email workflows, including transactional email within the HubSpot setup for Optimile and Mobiflow.
AI
Use AI where the input is messy. Keep business rules explicit.
AI helps where the input does not fit fixed rules: free-text form answers, replies, notes or documents. The rules that decide who receives what should stay explicit where they can be.
Where AI can help
- Extracting information
- Classification
- Summarisation
- Drafting or preparing copy
- Interpreting unstructured input
Usually kept deterministic
- Consent rules
- Segment membership based on explicit fields
- Ownership rules
- Send and stop conditions
- Fixed business logic
AI can support the workflow without becoming the workflow.
Measurement
Measure the workflow, not only the email.
Whether a workflow works depends on what it was supposed to make happen: a reply, a meeting, a handover, an update in another system. Email statistics are only part of that picture.
No tracking is complete. Privacy controls, browser restrictions and email-client behaviour all affect what can be measured; opens in particular are an unreliable signal.
What can be measured, where available
- Form submissions
- Workflow entries
- Email delivery
- Opens and clicks, where available and useful
- Replies
- Leads handed to Sales
- Tasks created
- Conversion events
- Workflow exits
- Errors
The useful metric depends on what the workflow is supposed to make happen.
Questions about marketing automation
Marketing automation, answered briefly
- What is marketing automation?
- Using data, triggers and workflows to run repetitive Marketing processes automatically, such as segmentation, lifecycle communication, lead follow-up and Marketing-to-Sales handovers.
- Is marketing automation the same as email marketing?
- No. Email can be one action inside a larger workflow. Marketing automation can also update CRM records, segment contacts, assign leads, create tasks, trigger notifications or exchange data with other systems.
- What marketing processes can be automated?
- Lead capture, segmentation, nurture, onboarding, re-engagement, event follow-up, transactional communication, lead routing and Sales follow-up. What is suitable depends on the available data and the business rules.
- Do you work with HubSpot marketing automation?
- Yes, including forms, lists and segmentation, workflows, email, CRM data and Marketing-to-Sales handover. More on the HubSpot expertise page.
- Can marketing automation connect to Salesforce?
- Yes, where the required data and interfaces are available. CRM and marketing platforms can exchange information through native integrations, APIs or an orchestration layer such as n8n, depending on the architecture. More on the Salesforce expertise page.
- Can you connect a website form to CRM and Sales follow-up?
- Yes. At Optimile and Mobiflow, a website request goes into HubSpot, is assigned to a Sales owner and creates a follow-up task.
- Can marketing automation use data from other systems?
- Often, if the system provides a reliable way to access or exchange that data: APIs, webhooks, native integrations or n8n.
- Can AI be used in marketing automation?
- Yes, particularly for unstructured input, classification, summarisation and preparing content. Important business rules and consent logic should stay explicit where appropriate.
- How do you know when someone should leave an automated flow?
- By defining exit conditions, such as the goal being reached, Sales taking ownership, a lifecycle status change, the contact no longer belonging to the audience, an opt-out or another workflow taking precedence. The exact rules depend on the process.
- Do you provide marketing automation in Belgium?
- VNCK works from Willebroek, Belgium and builds marketing automation connecting CRM, email, forms, customer data and Sales follow-up.
Marketing automation project
Build the workflow around what the customer actually did.
If your Marketing team is still moving contacts between lists, triggering follow-up manually or stitching CRM and email data together by hand, we can map the process and automate the repetitive parts.