CRM
Pre-Create Duplicate Block via Webhook with Survivorship Enrichment
Receives new-contact payloads on a webhook before they hit the CRM, checks HubSpot for an existing match.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook receives inbound contact payloadHTTP webhook
- ActionSearch HubSpot for an existing matchHubSpot
- LogicBranch: enrich existing vs create new
- ActionApply survivorship enrichment to HubSpot recordHubSpot
- ActionCreate new HubSpot contact when no matchHubSpot
- OutputRecord intake decision in PostgresPostgres
What it does
This workflow stops duplicates at the front door. Inbound contact data (from a form handler, lead vendor, or integration) is posted to a webhook first. The flow checks HubSpot for an existing match; if one exists, it enriches that record using survivorship rules (only filling or upgrading fields where the new source outranks the stored one) instead of creating a duplicate. If no match exists, it creates a clean new contact.
When to use it
Use it when you control the intake pipeline and want to prevent duplicates rather than clean them up later. Best for high-volume lead capture where every new submission risks re-creating an existing contact.
How it works
- 1A webhook receives the incoming contact payload.
- 2The flow searches HubSpot for an existing contact by email and phone.
- 3A logic branch decides enrich-existing versus create-new based on whether a match was found.
- 4On a match, it applies survivorship rules and updates only the fields where the inbound source wins, in HubSpot.
- 5On no match, it creates a new HubSpot contact.
- 6The decision (matched/enriched or created, with winning fields and sources) is recorded in Postgres.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect HubSpotCRM, deals, marketing, support.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.