CRM
Salesforce Pre-Insert Dedupe Guard via Postgres Canonical Index
Before a new Salesforce lead is created, checks it against a Postgres canonical-identity index and blocks the insert when a confident duplicate exists.
How it runs
The automated pipeline, trigger to output.
- TriggerInbound lead webhookHTTP webhook
- ActionQuery Postgres canonical identity indexPostgres
- LogicClassify match: exact, borderline, or new
- ActionLink to existing or create new Salesforce leadSalesforce
- ActionRegister new identity in PostgresPostgres
- OutputRoute borderline cases to Slack for decisionSlack
What it does
Acts as a guard in front of Salesforce lead creation. Each inbound lead is checked against a Postgres index of canonical contact identities. Confident duplicates are blocked and linked to the existing record; borderline matches are held for a human decision.
When to use it
Use this when you want to stop duplicates at the source rather than cleaning them up later, and you maintain a fast Postgres identity store keyed on normalized email and phone hashes.
How it works
- 1A new lead webhook from your form or enrichment tool triggers the flow.
- 2The flow normalizes the email and phone and queries the Postgres canonical index for matches.
- 3A logic step splits the result: exact or high-confidence match, fuzzy borderline, or no match.
- 4High-confidence matches are appended to the existing Salesforce record and the new insert is skipped.
- 5No-match leads are created in Salesforce and registered in the Postgres index.
- 6Borderline cases post to Slack for an approve-or-create decision before either path executes.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 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.