CRM

Re-link Attio and Stripe when a company changes its domain

When an Attio company's domain is updated, re-runs fuzzy matching against Stripe to detect that the change created a new duplicate or orphaned a billing link.

CategoryCRM
Enginesim
Difficultyadvanced
Triggerwebhook
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerAttio company domain-changed webhookAttio
  • LogicNormalize old and new domains
  • ActionRe-check Stripe for previously linked customerStripeStripe
  • LogicBranch: refresh link, new duplicate, or orphan repair
  • ActionRecord new duplicate group to PostgresPostgreSQLPostgres
  • OutputPost resync action to SlackSlack

What it does

Keeps CRM and billing in sync after a company rebrands or corrects its domain. A domain edit in Attio can silently break the fuzzy link to its Stripe customer or surface a duplicate that was previously hidden by the old domain; this flow catches that the moment it happens.

When to use it

Use it if reps regularly fix or update company domains in Attio and you've been blindsided by billing records quietly detaching from the right account afterward.

How it works

An Attio webhook fires when a company's domain attribute changes. The workflow normalizes both the old and new domains and re-checks Stripe for the customer that was linked under the previous value. A branch evaluates the outcome: if the new domain still maps cleanly to the same Stripe customer it refreshes the link; if the change now collides with another Attio company it records a new duplicate group in Postgres for review; if the change orphaned the billing link it re-attaches the Stripe customer to the corrected record. The action taken is posted to Slack for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AttioReal-time CRM with structured data + powerful views.
  2. 2
    Connect StripeCustomers, subscriptions, payments.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.