Deduptio

Connecting Attio

Deduptio connects to Attio through OAuth. Click Connect Attio after signing up, approve the access request in Attio, and you land back in Deduptio with the workspace connected. One Deduptio account maps to one Attio workspace.

What access we use

  • Read — objects, records, attributes, and lists, to find duplicates.
  • Read — meetings linked to the records in a duplicate group, so a rollback can rebuild them.
  • Write — only when you confirm an action: merging records, and removing or restoring duplicate list entries.

Nothing is written during scans or dry-run previews.

Reconnecting

Attio access tokens can expire or be revoked (for example if the authorizing user leaves the workspace). When that happens, actions show a Reconnect link — click it to re-authorize. Your rules, duplicate groups, and merge history are kept; nothing is lost by reconnecting.

The first time Attio refuses our access, the banner at the top of the Overview page changes from “Connected to Attio” to Attio connection expired, with the Reconnect link next to it. That banner is the reliable answer to “why has everything stopped working?”: Attio issues no refresh token, so once access is refused, scans and merges keep failing until someone reconnects. The Rules and Scan pages say the same thing where you hit it, and the Rules page still shows the rules you have saved while you are disconnected — reading a rule needs nothing from Attio, only editing one does.

When a connection attempt fails

If the round trip through Attio comes back without a connection, the Overview page says why rather than quietly showing the Connect button again. Three of these you can fix yourself in a few seconds:

  • The attempt expired. The link that starts a connection is good for ten minutes, so a consent screen left open — or an Attio login in the middle of it — outlives it. Click Connect Attio again.
  • We couldn't match the attempt to your account. Usually the same tab opened twice, a reload of the page you came back to, or a link opened out of order. Start the connection again from the Overview page.
  • You cancelled in Attio. Nothing was connected and nothing changed.

The remaining two — Attio approving the connection but declining to issue a token, or not naming the workspace it was for — are ours, not yours. Try once more, and if it keeps happening, email us: those attempts are logged on our side with the account they belong to, so we can look at the actual failure rather than guess.

Disconnecting

Disconnecton the Overview page ends the connection from Deduptio's side: scanning and merging stop until you reconnect, while your rules, duplicate groups and merge history are kept. You can also revoke access from Attio's workspace settings (Integrations) — same effect, from the other end.

Neither deletes anything in your CRM. If you want your Deduptio data deleted too, contact us — see Your account.

Who should authorise the connection

The OAuth grant is made by a person, and it inherits that person's access. Whoever clicks Connect Attio should be someone who can see every object you intend to scan — if the authorising user cannot see a custom object, Deduptio cannot see it either, and it simply will not appear in the object list when you build a rule.

The other consideration is longevity. The token is tied to the authorising user, so when that person leaves the workspace the token stops working and scans start failing with a Reconnect prompt. On a team of any size it is worth connecting with an account that is not going anywhere — an ops or admin seat rather than whoever happened to sign up first.

What a scan can and cannot see

Deduptio reads the objects, records, attributes and lists in the connected workspace. It does not read email bodies, call recordings, or notes, and it does not read anything from other workspaces on the same Attio account. Meeting records linked to a duplicate group are read for one reason only: a merge moves them onto the surviving record, and a rollback has to be able to put them back.

Working data from a scan lives in temporary tables that are dropped when the scan finishes. What persists afterwards is the minimum the product needs to show you a result: the matched fields of the records in each duplicate group, and the short-lived snapshots that back the 24-hour recovery window. Security documents the whole path, including how the token is encrypted at rest.

Common connection problems

  • An object is missing from the rule builder. Almost always a permissions gap on the authorising user rather than a Deduptio problem. Check that the user can open the object in Attio, then reconnect.
  • Actions show “Reconnect” out of nowhere.The token was revoked or expired — commonly because the authorising user left, or because someone removed the integration in Attio's settings. Clicking Reconnect restores it, and nothing is lost.
  • You want a second workspace. One Deduptio account maps to one Attio workspace. A second workspace needs a second Deduptio account; there is no way to switch a connected account from one workspace to another without disconnecting first.
  • The approval screen never appears. Usually a blocked pop-up or a session in a different Attio account than you expected. Sign in to the right Attio workspace in the same browser first, then start the connection again.

Once the workspace is connected, the next step is building a rule — see match rules and scanning.