LEAD GENERATION

Segment Event Leads into Tiered Follow-up Tracks

Scores each captured event lead against firmographic and intent rules, then files them into hot, warm, or nurture tracks in Airtable so each tier gets the right cadence.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled run after event close
  • ActionPull new lead rows from Airtable baseAirtableAirtable
  • LogicScore leads on title, company size, booth activity
  • LogicAssign Hot / Warm / Cold track
  • ActionUpdate each Airtable record with track + ownerAirtableAirtable
  • OutputPost track-count summary to SlackSlack

What it does

Reads the consolidated event-lead table and routes every lead into one of three follow-up tracks — hot (sales-ready), warm (qualified nurture), or cold (newsletter only) — based on title seniority, company size, and which booth activity they engaged with.

When to use it

Use it once leads are deduplicated and you need to decide who gets a same-day rep call versus a drip sequence. It replaces the manual triage spreadsheet most ops teams build after every show.

How it works

  1. 1A schedule fires the evening after the event closes.
  2. 2The flow pulls all new lead rows from the Airtable event-capture base.
  3. 3Each lead is scored — decision-maker titles and target-account companies weight toward hot; demo-booth visitors weight up, swag-only scans weight down.
  4. 4A branch assigns a track label (Hot / Warm / Cold) per the score thresholds.
  5. 5Each lead's Airtable record is updated with its track, score, and assigned owner.
  6. 6A summary of track counts is posted to the marketing Slack channel so reps know the day-one call volume.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  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.