Attio CRMEvery chatbot lead, in your Attio pipeline
Authorise Attio once and the leads your chatbot captures arrive as people, with the conversation that produced them attached as a deal and a note. No CSV exports, no second inbox to watch, and no duplicate contacts to clean up afterwards.
- A WhisperChat chatbot on a plan that includes integrations — the Attio card is a premium feature.
- An Attio workspace, and permission in it to authorise a third-party app.
- The standard People and Deals objects in that workspace — a lead becomes a person, and the conversation becomes a deal with a note.
- A chatbot that asks for contact details: a conversation with no email address is never synced.
Set it up in seven steps
Everything below happens in two places: your Account settings in WhisperChat, and Attio's own authorise screen.
- 1
Open your account integrations
In your WhisperChat dashboard, go to Account settings → Integrations. Attio is connected once for your whole account, not per chatbot.
Account settings → Integrations - 2
Press Connect
You are sent to Attio's authorise screen, signed in as yourself. Pick the workspace the leads should land in — that choice is what the connection is bound to.
- 3
Approve the access WhisperChat asks for
WhisperChat requests record read-write, object configuration read and note read-write. Approving returns you to WhisperChat with the workspace name shown next to a green Connected badge.
- 4
Check the connection
Use Test connection on the same screen. It calls Attio with your token and reports back, which is the quickest way to confirm the authorisation actually stuck.
- 5
Open the Attio card on Deploy
Open a chatbot, go to Deploy and press Manage on the Attio CRM card. It shows the connected workspace and the controls for that chatbot.
- 6
Backfill the leads you already have
Press Sync All to push every lead this chatbot has already captured into Attio. The result — how many of how many synced — is shown under the button.
New leads do not need this. Once your account is connected, they are pushed to Attio as they are captured.
- 7
Look at the result in Attio
Open the person record in Attio: you will find the lead's details, a linked deal for the conversation, and the transcript attached to that deal as a note.
What lands in your workspace
A synced lead arrives as a record your team can work with immediately, not as a row of raw fields.
People, not duplicates
Leads are matched on email address, so a returning visitor updates the person you already have instead of creating a second one.
A deal per conversation
Each synced conversation becomes a deal at the Lead stage, linked to the person, so it enters your pipeline where you can work it.
The whole transcript
The conversation is attached to the deal as a note, so whoever picks it up can read what the visitor actually asked.
Owned by a real member
Deals are created with the workspace member who authorised the connection as the owner, rather than landing unassigned.
One connection, every chatbot
Connect Attio once for your account and every chatbot you own can feed the same workspace.
Backfill on demand
Sync All pushes the leads a chatbot captured before you connected, so you do not start from an empty pipeline.
Worth knowing: the email address is what identifies a person in Attio. Conversations that never leave one stay in WhisperChat and are not synced.
How it works
Useful if you are reviewing the integration before authorising it, or working out why a lead did not appear.
What lands in Attio, in order
- A person record is created or updated, matched on email address, with the name, phone number and country the chatbot captured.
- The person's description records which chatbot captured the lead and when.
- If the conversation has messages, a deal named “WhisperChat Lead – <name or email>” is created at the Lead stage and linked to that person.
- The transcript is then attached to that deal as a plain-text note, titled with the date of the conversation.
No email, no sync
- The email address is the matching key, so a conversation that never left one is skipped — nothing partial is written.
- If you want more conversations to reach Attio, ask for contact details earlier in the chat rather than at the end.
Access and tokens
- The connection is OAuth: WhisperChat stores the tokens Attio issues and never sees your Attio password.
- Access tokens are refreshed automatically, so a working connection keeps working without you reauthorising it.
- The scopes cover records, object configuration and notes — enough to write a person, a deal and a note, and nothing else.
Disconnecting
- Disconnect from Account settings → Integrations. The stored tokens are cleared and syncing stops immediately.
- People, deals and notes already in Attio stay exactly as they are — disconnecting never deletes anything in your workspace.
- Your leads remain in WhisperChat either way; Attio is a destination, not the record of truth.
What WhisperChat asks Attio for
- Read and write records, so a lead can become a person and a deal.
- Read your object configuration, so records are written against the right objects.
- Read and write notes, so the conversation can be attached to the deal.