MARKETING

Tiered post-event follow-up email sender

After an event closes, segments captured leads into hot, warm, and cold tiers and sends each tier a tailored personalized follow-up email from Gmail.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run morning after event
  • ActionPull event leads from AirtableAirtableAirtable
  • LogicSegment each lead into hot, warm, or cold tier
  • ActionSend tier-matched personalized email via GmailGmailGmail
  • OutputWrite send status back to AirtableAirtableAirtable

What it does

Runs the day after your event ends and sends every scanned lead a follow-up email matched to their interest tier — a meeting-booking ask for hot leads, a resource roundup for warm leads, and a light newsletter opt-in for cold leads. Each send is logged so nobody gets double-mailed.

When to use it

Use it once per event, scheduled for the morning after the show closes, when you have a full lead list in Airtable and want fast, segmented outreach instead of one generic blast.

How it works

  1. 1A schedule trigger fires the morning after the event.
  2. 2The flow pulls all leads for the event from Airtable.
  3. 3A logic step routes each lead into hot, warm, or cold based on its captured score and booth notes.
  4. 4The matching email template is personalized with the lead's name, company, and the topic they discussed at the booth.
  5. 5Gmail sends each message from the rep or booth alias.
  6. 6The send result and timestamp are written back to Airtable so the sequence is idempotent and reportable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.