LEAD GENERATION

Post net-new conference accounts to Slack for SDR claim

Watches the reconciled attendee table for accounts with no CRM owner and posts each one to a Slack claim channel with a one-click button.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNet-new row added in AirtableAirtableAirtable
  • LogicFilter out already-claimed accounts
  • ActionFormat Slack claim card
  • ActionPost card with Claim button to SlackSlack
  • OutputWrite claiming SDR back as owner in AirtableAirtableAirtable

What it does

Monitors your reconciled attendee table for net-new accounts — companies that appeared at the event but have no existing owner in the CRM. For each one it posts a claim card to a Slack channel showing company, attendee, title, and a deep link, plus a Claim button. The first SDR to click is written back as the owner so no two reps chase the same lead.

When to use it

Use it right after badge reconciliation finishes, when you want sales to self-serve the fresh pipeline instead of a manager hand-assigning rows. Ideal for high-volume booth events where speed-to-claim matters.

How it works

  1. 1A new or updated row in the Airtable reconciled table flagged Net-new triggers the flow.
  2. 2A filter drops anything already claimed or owned to avoid double-posting.
  3. 3The attendee and company details are formatted into a Slack claim card.
  4. 4The card posts to the SDR claim channel with an interactive Claim action.
  5. 5When a rep clicks, their identity is captured and written back to Airtable as the account owner, and the card updates to show it as claimed.

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.