How to set up marketing automation: do the plumbing first

Short answer: Set up marketing automation in this order: write the workflow on paper, authenticate your sending domain with SPF, DKIM and DMARC, import contacts with their consent status attached rather than as one list, connect every place an enquiry can arrive, build one workflow, then test it as a fake customer before a real lead ever sees it. Most first automations fail in this plumbing, not in the workflow logic itself.

Plenty of guides tell you which platform to buy and which task to automate first. Fewer explain why the automation you eventually build does not work the way it looked in the demo. Usually it is not the workflow. It is that the email was never authenticated on your own domain and landed in spam, the contacts were imported without a consent record attached, or the enquiry form was never actually connected, so the workflow had nothing to fire from.

This is the hands-on build, in order, for a first marketing automation for Australian small business. If you have not decided whether the return is worth the setup time, work through the break-even sum first. This article assumes you have, and takes you from a blank platform to one tested, working automation.

Write the workflow before you touch the software

Open a blank document, not the platform, and answer five questions about the one workflow you are building.

What is the trigger? A form submitted, a quote sent, a booking made. Pick one, not three.

What is the first message, and what does it say? Write the actual wording, not a description of it.

Who gets alerted, and how? A text to the owner’s mobile is more reliable than an email nobody checks between jobs.

How long does it wait before the next step, and what happens then?

What stops it? Booked, replied, unsubscribed, and anything else that means the workflow has done its job.

Doing this on paper first catches the gaps a platform’s drag-and-drop builder hides, such as never saying what happens if they do not reply.

Authenticate your email before you send a single automated message

This is the step people skip because it does not feel like marketing, and it is the one that decides whether anything you send actually arrives.

Set up SPF, DKIM and DMARC records for your sending domain at your domain host, or ask whoever manages your website hosting or DNS to do it. These three records tell Gmail, Yahoo and everyone else that your automation platform is genuinely allowed to send mail as your business, rather than something pretending to be you.

Since February 2024, every sender to Gmail and Yahoo has needed to authenticate with SPF or DKIM at a minimum. If you send around 5,000 or more messages a day to Gmail addresses, the bar is higher: you need SPF, DKIM and DMARC all in place, a one-click unsubscribe, and a spam complaint rate kept under 0.3%. Rules like this tend to tighten rather than loosen over time, so check the current requirements before you rely on anything written here.

Whatever your volume, do not run automated marketing from a free webmail address or your internet provider’s email service. You cannot authenticate a domain you do not control.

Import contacts with their consent, not as one big list

The temptation with a new platform is to upload your whole contact list in one go and start automating against all of it. Do not. The Spam Act 2003 requires consent, express or reasonably inferred from an existing relationship, before you send a commercial electronic message, and that obligation follows each contact individually, not the list as a whole.

Before you import anyone, tag them with where their consent came from and when. A named form, a checkout step, a quote request, a verbal yes written down at the time. If you cannot say where a contact’s consent came from, treat them as not marketable until they opt in again through a form that captures it properly. Old contacts and uncertain ones are the ones that create risk later, not the recent, clearly sourced ones.

Never import a bought or scraped list. A platform cannot repair missing consent, and this is exactly the pattern the Spam Act was written to catch. The edges of what counts as inferred consent move as guidance is updated, so check the current position from the Australian Communications and Media Authority rather than assuming last year’s rule still applies. For the full Spam Act and Privacy Act picture, including what a defensible consent record actually contains, see the pillar guide and the section on where your data is stored in our platform comparison.

Also resist the platform’s own template library and sample sequences at this stage. They are written for a generic business elsewhere, and switching them on before your consent tags are sorted just means broken messages go out faster.

Connect every place an enquiry can land

A workflow can only fire from something it can see. Before you build it, connect every channel an enquiry might actually arrive through: your website contact form, Facebook and Instagram lead ads if you run them, and any booking tool you use for appointments.

While you are connecting each one, add a field that records where that enquiry came from. It is the difference between knowing in three months which channel actually produces customers and guessing. A contact from a Facebook lead form and one from your website should carry that source into the automation, not get flattened into one undifferentiated list.

Test each connection on its own before moving on. Submit the website form and confirm the contact appears in the platform, then do the same for the Facebook lead form and any booking tool. A connection that looks configured in the settings screen is not the same as one that has actually passed a real submission through.

Build the one workflow that matters first

With the plumbing in place, build the workflow you wrote out on paper. For most small businesses that is an instant acknowledgement to a new enquiry, an alert to the owner, a short wait, one follow-up, and a set of exit rules.

The acknowledgement should go out within minutes and say something specific: what was received, and roughly when a proper reply is coming. The owner alert should land somewhere they will actually see it while working, which for many trades and clinics is a text message rather than an email buried in an inbox.

Exit rules matter as much as the messages themselves. The workflow should stop the moment someone books, replies or unsubscribes. A workflow that keeps messaging a customer who has already booked is worse than no workflow, because it tells them your systems do not talk to each other. For how many follow-up messages to include and how far apart to space them once this first workflow is proven, see our guide to lead nurture sequence length rather than guessing at a number here.

Test it as if you were the customer

Before a real lead touches this workflow, become one. Submit your own form using a spare email address, once from a phone and once from a desktop, since the two can behave differently depending on your platform and email provider.

Watch where the reply lands. If it drops into Promotions or Spam rather than the primary inbox, revisit your authentication setup or the wording of the message, rather than ignoring it because it still arrived. Click the unsubscribe link and confirm it works. Reply to the automated message and confirm the sequence stops, because an exit rule that has never been tested is not a rule, it is a hope. Check the owner alert arrives somewhere a real person will notice it too.

A worked example. A physio clinic in Hobart connects its online booking form and its Facebook lead ads to a new platform. The owner writes the workflow on paper first: instant confirmation, a text alert to the front desk, a follow-up two days later if the appointment has not been confirmed, and an exit the moment someone books or replies. Before switching it on for real patients, the owner books a test appointment from their own phone, checks the confirmation lands in their main inbox rather than spam, replies to it, and confirms the follow-up never arrives. Only once all of that checks out does the workflow go live for actual enquiries.

Name things and write down what it does

Once the workflow is tested and live, spend ten minutes writing a one-page note: what the automation does, what triggers it, what it sends, when it stops, and who owns it if something needs fixing. Give the workflow itself a plain name in the platform too, rather than leaving it as “Untitled” or a default label, so it is recognisable in six months when someone else looks at the account.

This matters more than it sounds. A working automation often quietly breaks because the person who built it is the only one who understood it, and a new staff member cannot tell what it does without opening every step to check.

The first 30 days: what to check, and what to leave alone

For the first month, check the workflow weekly rather than daily. Look at bounces, since a rising bounce rate usually points to a data or authentication problem rather than a content one. Look at spam complaints, which should stay close to zero if consent and authentication are sound. And look at replies and bookings that actually come through the workflow, not opens, since an open can be recorded without anyone reading the message.

Resist adding a second workflow during this month, even if the first one is clearly working. A workflow that has run for a week has not met the awkward real enquiries yet: the person who replies at 11pm, the one who books elsewhere and never says so, the one whose email bounces silently. Give it the full month before deciding it is solid enough to build on.

Frequently asked questions

What order should I set up marketing automation in?

Write the workflow on paper first, then authenticate your sending domain with SPF, DKIM and DMARC, then import contacts with their consent status attached, then connect every place an enquiry can arrive, then build one workflow, then test it as a fake customer. Skipping straight to building the workflow is the most common reason a first automation misfires, because the plumbing underneath it was never checked.

Do I need to authenticate my email domain before sending automated messages?

Yes, at a minimum. Since February 2024, every sender to Gmail and Yahoo has needed to authenticate with SPF or DKIM, and if you send around 5,000 or more messages a day to Gmail, SPF, DKIM and DMARC are all required, along with a one-click unsubscribe and a spam complaint rate under 0.3%. Setting up all three from the outset is good practice at any volume. Set these records up at your domain host before you send your first automated email, and do not send marketing from a free webmail or ISP address, because you cannot authenticate a domain you do not control.

Can I import my existing contact list into a new automation platform?

Only the part of it you can show consent for. Tag each contact with where and when their consent came from, and treat anyone old or uncertain as not marketable until they opt in again. Never import a bought or scraped list into a marketing automation platform, because the Spam Act 2003 requires consent before you send, not after someone complains.

How do I test a marketing automation workflow before it goes live?

Submit your own form as a customer would, on both a phone and a desktop, and watch which inbox tab the reply lands in. Click the unsubscribe link and confirm it works. Reply to the automated message and confirm the sequence actually stops. Check that the owner alert arrives somewhere someone will see it. Do all of this before a real enquiry touches the workflow.

How long should I wait before adding a second automation workflow?

About a month. Run the first workflow for thirty days, checking bounces, spam complaints and whether replies and bookings are actually coming through it, before you build anything else. A second workflow built on top of a first one nobody has properly watched tends to multiply whatever was already going wrong, rather than add value on its own.

---

Want a second pair of eyes on the plumbing before real leads touch it? Get a free audit and we will check your authentication, your consent tags and whether your form actually connects to your workflow.