Send chatbot leads to Attio
A record on any object in your workspace
A lead from the chat becomes a record on the Attio object you pick, standard or one of your own, with each attribute written the way Attio reads it back rather than as a flat string.
What it does
Your objects, including the ones you invented
The picker reads the workspace's objects, so a custom object is as connectable as People or Companies.
Values with the right shape
An email address, a phone number and a name are each stored as a structured value in Attio. A name is split into its halves, a domain is stripped to its host.
Attributes read from the object
The mapper offers the attributes that exist and leaves out the ones pointing at other records, which a lead answer can never fill.
How to connect it
Read the full guide- 1
Create an access token
Attio, Workspace settings, Developers, then Access tokens.
- 2
Connect Attio
Paste the token. We verify it and name the workspace.
- 3
Create a route
Choose which leads it takes and which object they become.
- 4
Map the attributes
Auto-map, then check it. Anything we cannot shape is named in the dispatch log rather than silently skipped.
Questions people ask
Which scopes does it need?
Record read-write to create, and object configuration read so the mapper can offer attributes that exist.
Will it match an existing person?
Not yet. It creates a record. Attio can assert on a matching attribute, and which attribute that should be is a decision we would rather ask for.
What about select attributes?
The option is sent by title. One the object does not have is left out rather than created.
What teams use it for
Upload your documents, get answers that cite them
One knowledge base, an AI chat or an Ask AI search on any site, and every answer with the passage it came from. Free for 14 days.