CRM
Block duplicate Attio records when a new Stripe customer signs up
On each new Stripe customer, fuzzy-matches the customer's email domain against existing Attio companies and either links the new customer to the matched record or creates a fresh…
How it runs
The automated pipeline, trigger to output.
- TriggerStripe customer.created webhookStripe
- LogicNormalize email domain
- ActionSearch Attio for fuzzy domain matchAttio
- LogicBranch: strong match, no match, or ambiguous
- ActionLink or create Attio companyAttio
- OutputQueue ambiguous ties to PostgresPostgres
What it does
Acts as a real-time guard at the moment a customer starts paying. When Stripe creates a new customer, it checks whether that company already exists in Attio by fuzzy domain match, then links the billing record to the existing company instead of letting a duplicate appear.
When to use it
Use it if self-serve signups in Stripe routinely create CRM duplicates because the buyer's email domain already exists in Attio under a slightly different spelling or a sales-created record.
How it works
A Stripe `customer.created` webhook fires the flow. The workflow extracts and normalizes the customer's email domain, then searches Attio for companies with a similar normalized domain above a confidence threshold. A branch decides the outcome: a strong single match updates that Attio company with the new Stripe customer ID and billing status; no match creates a new Attio company seeded from Stripe data; multiple weak matches are written to a Postgres review queue so a human resolves the tie. The result is recorded for audit.
Set it up
What you configure once, before turning it on.
- 1Connect StripeCustomers, subscriptions, payments.
- 2Connect AttioReal-time CRM with structured data + powerful views.
- 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.