HubSpot Drip Campaigns and Automation Workflows

HubSpot's automation engine supports a range of email sending patterns — from one-off individual emails to fully branching automated sequences. Understanding the distinctions between these modes is essential before building out any campaign.

The Three Email Sending Modes

1. One-to-One Email (from a Contact Record)

Send a single email directly from a contact's record. Logged automatically in the activity timeline. Best for personalized outreach or follow-ups.

2. Segment-Based Broadcast

Create an email, define a segment (list of contacts matching certain criteria), and send once. Useful for event follow-ups, announcements, or periodic check-ins to a defined group. This is the appropriate pattern for "stay on the radar" campaigns to inactive or disqualified leads.

3. Automated Workflow (True Drip)

Triggered by a condition or event, workflows execute a sequence of actions — emails, delays, branching logic, field updates, list changes — without manual intervention. This is the most powerful and complex mode.

Marketing vs. Informational Emails

HubSpot distinguishes between two email types with different rules:

To send marketing emails to a contact, the Marketing Contact Status field on their record must be enabled. This can be set manually or via workflow.

Building an Automated Workflow

Navigate to Automation → Workflows and create a new workflow. The core structure is:

1. Trigger — What causes enrollment? Examples:
   - Contact completes a form
   - A field value changes (e.g., Lifecycle Stage moves to "Lead")
   - Manual enrollment
   - Date-based (e.g., X days after last activity)

2. Actions — What happens next? Common actions:
   - Send an email
   - Wait (delay by days, or until a specific day/time)
   - Add/remove from a list
   - Update a contact property
   - Create a task

3. Branches — Conditional logic ("if this, then that"):
   - Did the contact open the last email? → Branch A (engaged) vs. Branch B (not engaged)
   - Is their lifecycle stage X? → Route accordingly

Example: "Not Interested" Re-engagement Sequence

Trigger: Contact property "Lead Status" set to "Not Interested"
→ Wait 90 days
→ Send Email 1: Low-pressure check-in
→ Wait 30 days
→ If Email 1 opened:
    → Update lifecycle stage → Send to active nurture sequence
  If Email 1 not opened:
    → Send Email 2: Value reminder
→ Wait 30 days
→ End / flag for manual review

Example: Lead Nurture Sequence

Trigger: Manual enrollment (or form submission)
→ Send Email 1: Welcome / intro
→ Wait 7 days (delay to Tuesday or Thursday send)
→ Send Email 2: Case study or social proof
→ Wait 7 days
→ Send Email 3: CTA / offer
→ If any email clicked → Change lifecycle stage to "Sales Qualified Lead"

Recommended Pre-Build Process: Decision Trees

Before building workflows in HubSpot, map the logic on paper or in a simple diagram tool. For each sequence, define:

• Trigger condition — what event or state change starts the workflow
• Email content — what each email says and its goal
• Timing — delays between steps; preferred send days
• Branch conditions — what behavior (open, click, no action) causes a fork
• Exit conditions — when does a contact leave the workflow

From the BluePoint session: Asymmetric recommended that Wade and Mike draft their decision trees — "if this, then that" sequences — before the next session so the team (Chris) can build them out in HubSpot. This avoids wasted configuration time and reduces errors.

Workflow Performance Monitoring

Once a workflow is live, review it under Automation → Workflows → [Workflow Name] → Analyze:

• Enrollment counts (total, last 7 days, last 30 days)
• Active contacts currently in the workflow
• Email open/click rates per step
• Opt-out rates

Check the Health tab for errors — misconfigured steps, missing email templates, or contacts failing to enroll.

Practical Tips

• Timing matters: Use delay steps to ensure emails land on preferred days (e.g., Tuesday/Thursday). Avoid Monday sends.
• Don't over-automate early: Start with a manually-triggered workflow so you control enrollment. Move to automatic triggers once the sequence is validated.
• Test before launching: Enroll a test contact and walk through the full sequence before enabling for real contacts.
• Segment first: Build the contact list/segment you intend to enroll before building the workflow. Confirm the segment logic is correct.
• Let Asymmetric build complex ones: Workflows with multiple branches and dozens of steps are time-consuming to configure correctly. Describe what you want; have the team build it.

Related

• ^[1] — client context for this session
• ^[2] — building segments for workflow enrollment
• ^[3] — field setup referenced in competitor tracking and lifecycle stage management
• ^[4] — call tracking integration discussed in same session