Attio
Create and update people, companies, deals, notes, tasks and custom objects in Attio from a Surface workflow.
The card's own line: "Connect your form to your Attio CRM to create contacts, companies, notes and more."
Connecting
OAuth, from the Integrations screen. Click Authenticate on the Attio card and authorise Surface in Attio. The card then reads Disconnect, which is how you tell it is live.
You can also connect from inside the Workflow Builder: add any Attio action and it offers the same authentication.
What You Can Do with It
Eleven workflow actions, in create and update pairs:
| Action | Does |
|---|---|
| Attio Create Person · Attio Update Person | A person record |
| Attio Create Company · Attio Update Company | A company record |
| Attio Create Deal · Attio Update Deal | A deal |
| Attio Create Custom Object · Attio Update Custom Object | Any custom object you have defined |
| Attio Create Note | A note, usually against the person or company just created |
| Attio Create Task | A task |
| Attio Get Owner | Look up an owner, so a later action can assign to them |
Create actions have an update twin. If a workflow's create action would hit
an existing record, switch it for the update version rather than adding
deduplication logic: Surface pairs AttioPerson with AttioUpdatePerson,
AttioCompany with AttioUpdateCompany, AttioDeal with AttioUpdateDeal
and AttioCustomObject with AttioUpdateCustomObject.
When to Use the CRM Agent Instead
These actions write the fields you mapped, the same way every time. If the write should depend on what Attio already holds (update rather than duplicate, pick an owner), use the CRM agent step. It reads Attio first and works from written instructions.
Reading Attio Back
There is no Attio read surface over MCP today. The
hubspot tool family reads HubSpot only. To get Attio data back out, use
webhooks or Attio's own API.
Ready to Get Started?
See it on your own site, or open the app and build the first form.