Marketing Automation Workflow Architecture
Marketing automation platforms — GoHighLevel, HubSpot, Make, Zapier — are only as good as the workflows running inside them. Most businesses underuse their platform because they have not defined what workflows they need. This framework identifies six workflow types that cover 90% of business marketing automation requirements and defines the design principles that make them work reliably over time.
Design Principles
Inbound Lead Capture Workflow
The first response to any inbound inquiry. Speed matters here — every minute of delay measurably reduces conversion rates.
Trigger: Form submission, Facebook Lead Ad, Google Lead Form Extension, or website chat
Steps
- 1Create or update contact record in CRM with source tag
- 2Create opportunity in correct pipeline with deal stage "New Lead"
- 3Send internal notification to assigned rep (SMS + email, simultaneously)
- 4Send acknowledgment to contact within 2 minutes (SMS preferred for speed; email as backup)
- 5Assign internal task to rep with follow-up deadline
- 6If rep does not log activity within X hours, escalate notification to manager
Design Note
The acknowledgment to the contact is not a nurture email — it is a confirmation that their inquiry was received. It should be brief, specific, and promise a human response within a stated timeframe. "Thanks for reaching out about [service]. We will get back to you by 5 PM today." Vague acknowledgments ("We will be in touch soon") reduce confidence.
Lead Qualification & Routing Workflow
Not all leads are equal. This workflow separates qualified leads from unqualified ones and routes each to the appropriate next step.
Trigger: New contact or opportunity created; or qualification fields populated
Steps
- 1Evaluate qualification criteria: budget range, service area, timeline, specific product/service interest
- 2Apply conditional branching: qualified → assign to senior rep; unqualified → enroll in nurture sequence; wrong territory → route to regional rep or refer out
- 3Move opportunity to appropriate pipeline stage based on qualification outcome
- 4If qualified: notify rep with qualification summary, trigger discovery call booking sequence
- 5If unqualified: tag for re-engagement trigger at appropriate interval (e.g., 90 days)
Design Note
The qualification criteria need to be defined before building this workflow, not during. "Qualified" must have an explicit definition that everyone in the business agrees on. A workflow built on ambiguous criteria will route incorrectly and silently — the system will process the contact, the stage will move, and nobody will notice the misrouting for weeks.
Lead Nurture Sequence
Sustained outreach to contacts who have not yet converted. The goal is to remain present and relevant until the contact is ready to move forward.
Trigger: Contact enters a specific list, pipeline stage, or has been inactive for a defined number of days
Steps
- 1Email 1 (Day 1): Value-specific to the contact's stated interest or source
- 2Email 2 (Day 4): Case study, case example, or relevant content — not a pitch
- 3SMS touch (Day 7): Brief, direct, human-sounding. "Wanted to follow up on the [topic] question — happy to answer any questions."
- 4Email 3 (Day 12): Question-based email designed to elicit a reply
- 5Final step (Day 21): "Moving on" email — honest acknowledgment that you will stop reaching out, option to re-engage
Design Note
Reply detection is non-negotiable. If a contact replies to any step in the sequence, they must be immediately removed from the sequence and a task must be assigned to the rep. Running a nurture sequence on a contact who is actively in conversation with your team destroys trust and signals that your system does not know its own data.
Appointment Booking Workflow
The workflow that runs from initial booking confirmation through post-appointment follow-up. Reduces no-shows and creates a consistent client experience.
Trigger: Calendar booking confirmed in GHL, Calendly, or Google Calendar (via webhook)
Steps
- 1Booking confirmation: immediate SMS and email with appointment details, address or video link, and what to expect
- 224-hour reminder: SMS with appointment time and a "reply RESCHEDULE if you need to change" prompt
- 31-hour reminder: brief SMS — appointment time and location only
- 4Post-appointment: if appointment marked attended → trigger post-service workflow or next-step sequence; if not marked attended within 2 hours of appointment time → trigger no-show re-engagement
- 5No-show re-engagement: SMS within 30 minutes ("Looks like we missed each other — want to rebook?") → if no response in 24 hours → re-enroll in nurture at appropriate stage
Design Note
The no-show workflow is often omitted because it feels confrontational. It should not be. A contact who no-shows a discovery call is not necessarily a bad lead — life happens. A brief, non-judgmental re-engagement message recovers a meaningful percentage of no-shows. Leaving no-shows in a "pending" pipeline stage with no automated follow-up is lost revenue.
Post-Service Reputation Workflow
The workflow that generates Google reviews at scale without manual outreach. Triggered by job or service completion.
Trigger: Opportunity moved to Closed Won, or job status field set to "Complete" in CRM
Steps
- 1Wait 24 hours after completion trigger (give the client time to experience the outcome before asking for feedback)
- 2SMS review request: "Thank you for working with us on [project]. If you have a moment, a Google review would mean a lot: [direct Google review link]"
- 3If no review after 72 hours: email follow-up with same link
- 4If negative sentiment detected (contact replies with complaint): remove from review sequence, flag for manual follow-up, assign task to owner
- 5Log review request in contact record with date
Design Note
The Google review link should go directly to the review form, not to the business profile. A direct link (format: g.page/[business-name]/review) requires one fewer click and meaningfully increases completion rates. Test the link before deploying the workflow — expired or misconfigured links silently kill the program.
Operational Workflows
The category that most businesses under-invest in. Internal processes that, when automated, save significant time and reduce error rates.
Trigger: Various — contract signed, payment received, project milestone, weekly schedule
Steps
- 1Client onboarding: signed contract → folder creation in Google Drive → welcome email → onboarding form delivery → task creation for team members → calendar invite for kickoff
- 2Reporting aggregation: weekly scheduled trigger → pull data from GA4, HubSpot, and Google Sheets → format into Looker Studio or Google Sheets summary → deliver to Slack or email by Monday morning
- 3Invoice follow-up: invoice sent → if unpaid after 7 days → automated reminder → if unpaid after 14 days → escalation email with payment link → task assigned to account manager
- 4New lead source notification: lead from specific source (e.g., Google LSA) → immediate Slack channel notification with contact name, phone, and inquiry type
Design Note
Operational workflows have the highest ROI of any automation category because they run silently at high frequency. A weekly reporting workflow that saves 45 minutes of manual work saves 39 hours per year. The client onboarding workflow that eliminates four manual steps removes the failure modes those steps introduce. The ROI is not dramatic — it accumulates.
Building a Stack, Not a Collection of Workflows
These six workflow types are not independent modules — they share contact records, pipeline stages, and tags. A contact who completes a Lead Capture Workflow enters a Qualification Workflow, which routes them to either a Nurture Sequence or a Booking Workflow. A contact who completes a booked appointment triggers a Post-Service Workflow after the job closes.
The integration between workflow types is where most automation programs break down. Workflows are built in isolation, without shared tag naming conventions or consistent contact state definitions. The result is contacts who are enrolled in multiple sequences simultaneously, or contacts who fall through gaps between workflows.
Building a stack means defining the contact state model first: the set of tags, pipeline stages, and custom field values that describe where a contact is in the customer journey at any given moment. Each workflow type operates on contacts in specific states and transitions them to new states. When that model is explicit, the workflows compose predictably.
Gian McCoy
Marketing Technology professional based in Los Angeles. GoHighLevel builds, Make and Zapier workflow architecture, HubSpot automation, and full-stack marketing automation across 20+ years of client delivery.