MARKETING

Send a tier-based multi-day nurture drip to webinar attendees

On a daily schedule, advances scored webinar contacts through a multi-step email drip whose content varies by engagement tier, stopping early once a contact books a meeting.

CategoryMarketing
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionQuery contacts due for next drip stepHubSpotHubSpot
  • LogicBranch on tier and step to pick template
  • ActionSend drip email and advance step counterGmailGmail
  • OutputPost daily send summary to SlackSlack

What it does

Runs a staged follow-up campaign in the days after a webinar, sending different email content to Hot, Warm, and Cold contacts. Hot contacts get a meeting-booking push, Warm contacts get a case study and a soft CTA, and Cold contacts get lighter educational content. The sequence checks each contact's progress daily and stops sending once they book a meeting.

When to use it

Use this to keep a structured, behavior-aware nurture running without manual sends. It assumes contacts already carry an engagement tier from the scoring template and a 'last drip step' property in HubSpot.

How it works

  1. 1A daily schedule triggers the flow each morning.
  2. 2The flow queries HubSpot for webinar contacts who are due for their next drip step and have not booked a meeting.
  3. 3A logic step branches on engagement tier and current step to pick the right email template and copy.
  4. 4It sends the selected message through Gmail and advances the contact's 'last drip step' counter in HubSpot.
  5. 5The final output posts a daily send summary by tier to Slack.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.