CRM
Inbound Lead Dedupe Gate with Postgres Match and Slack Escalation
Intercepts every inbound lead webhook, checks it against a Postgres contacts store for an existing match, and either enriches the existing record, creates a new one.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound lead webhook receivedHTTP webhook
- ActionQuery Postgres for exact match on email or phonePostgres
- LogicBranch: exact match, no match, or fuzzy near-match
- ActionEscalate near-match comparison to Slack for survivorship callSlack
- ActionWrite resolved contact state to PostgresPostgres
- OutputReturn resolved contact id to webhook caller
What it does
It sits in front of lead capture and prevents duplicates from ever entering the database. Each new lead is matched against your Postgres contacts table; exact matches update in place, clean misses become new records, and ambiguous near-matches are paused for human judgment.
When to use it
Use it when leads arrive from forms, ads, or partners and you want to stop duplicates at the door rather than cleaning them up later. Ideal when your system of record is a Postgres database you control directly.
How it works
- 1An inbound lead webhook triggers the flow.
- 2The flow queries Postgres for an exact match on email or phone.
- 3A logic branch routes the lead: exact match, no match, or fuzzy near-match.
- 4Exact matches enrich the existing row with any new non-empty fields; clean misses insert a new contact.
- 5Fuzzy near-matches post a side-by-side comparison to Slack with Merge or Keep Separate actions.
- 6The reviewer's choice writes the final state back to Postgres and the webhook caller gets the resolved contact id.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More CRM workflows
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.
Weekly Dormant-Anniversary Cohort Digest
Every week, groups dormant Attio accounts by which last-touch anniversary they hit that week, builds a prioritized digest.
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.
Backfill Intercom conversation topics onto stale HubSpot contacts
Finds HubSpot contacts with no recent Intercom topic, pulls their conversation history from Intercom, classifies the dominant topic with OpenAI.
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.
Tag closed Intercom conversations onto Salesforce contacts in real time
On each Intercom conversation close, classifies the topic with OpenAI and appends it to the matching Salesforce contact's activity timeline so the topic never goes stale…
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.