CRM
Dedupe New Booth Scans Against the CRM and Split New vs Existing
On each badge scan, checks Salesforce for an existing contact, routes net-new visitors into a fresh-lead nurture track and known contacts to their account owner.
How it runs
The automated pipeline, trigger to output.
- TriggerBadge scan posted to webhookHTTP webhook
- ActionLook up contact in Salesforce by emailSalesforce
- LogicBranch on new vs existing contact
- ActionCreate new lead and nurture rowAirtable
- ActionAlert account owner of booth visitSalesforce
- OutputNotify owner in Slack with interestSlack
What it does
Booth scans often include people who are already in your pipeline. This workflow checks each scan against Salesforce in real time. Net-new visitors get logged and dropped into the new-lead nurture track, while existing contacts are flagged to their account owner with a note that they stopped by the booth, so no one gets a cold intro email when they already have a rep.
When to use it
Use when your event audience overlaps with your existing customer and pipeline base and you need to avoid duplicate CRM records or sending prospecting emails to active accounts. Pairs with any scanner that posts scans to a webhook.
How it works
- 1A badge scan posts visitor data to the webhook trigger.
- 2Salesforce is queried by email to check for an existing contact.
- 3A logic step branches on new versus existing.
- 4New visitors are created as Salesforce leads and added to the new-lead nurture track in Airtable.
- 5For existing contacts, the account owner is notified in Slack that their contact visited the booth, with the captured interest.
- 6Either path writes an audit row to Airtable so the dedupe decision is traceable.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect AirtableBases, tables, views, automations.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
Spin up a Monday handoff board for a departing rep's deals
When a rep is deactivated in Salesforce, this creates a Monday.com board with one item per open opportunity so the manager can manually triage and assign each handoff.
Dormant Account Check-In Call Scheduler
On the anniversary of an account's last touch, books a tentative check-in call on the owner's Google Calendar and emails the contact a scheduling invite.
Daily orphaned-opportunity sweep with manager Slack digest
Each morning this scans Salesforce for open opportunities owned by inactive users and posts a per-manager digest in Slack listing the orphaned deals that need a new owner.
Reassign a departed rep's open pipeline by territory
When a Salesforce user is deactivated, this finds all of their open opportunities and reassigns each one to the active rep who owns its territory, then logs the moves.
Escalate opportunities still owned by an inactive rep after grace period
Checks daily for open opportunities that have stayed with an inactive owner past a grace window and escalates each to the regional director by email and Slack with deal context.
AI-Personalized Dormant Account Win-Back
On a dormancy anniversary, an agent researches the account's history and recent public signals, drafts a genuinely personalized win-back email.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.