Guide
How to connect Attio to Shmor with an access token
By Lev Perlman3 min read
Shmor writes the people you meet into Attio: people, companies, notes, follow-up tasks and, on Pro, deals. The simplest way to connect it is a workspace access token, which an Attio admin creates in a minute. This guide covers creating the token, giving it the right scopes and checking the result.
Before you start
- You need to be an admin of the Attio workspace, because only admins can create access tokens.1 If you are not, ask an admin to do steps 1 and 2.
- You need a Shmor account. If you have only just signed up, Shmor is using ShmorCRM; connecting Attio switches new captures to Attio.
Step 1: create the token in Attio
- In Attio, open the dropdown next to your workspace name and click Workspace settings.
- Open the Developers tab.
- Click + New access token and name it Shmor.1
Step 2: give it these scopes
Shmor asks for what it uses, and nothing more:
| Scope | Access | Why Shmor needs it |
|---|---|---|
| Records | Read-write | Find and create people and companies, and update them |
| Object configuration | Read-write | Add the Met via, Met at and Needs info attributes to People |
| Notes | Read-write | Add the note about your conversation |
| Tasks | Read-write | Create the follow-up task |
| User management | Read | Assign tasks and deals to you |
Create the token and copy it. Attio treats tokens like passwords, so paste it straight into Shmor rather than into a chat or a document.1
Step 3: paste it into Shmor
- In Shmor, open Integrations (or the Choose your CRM step of set-up).
- On the Attio card, open Connect with an access key.
- Paste the token into Attio access key and click Connect Attio.
Shmor checks the token and adds its attributes to People before saving anything. If the token does not work, the connection you already had is kept. When it succeeds, you see: "Connected. Shmor added its fields to Attio, and new captures go there now."
If you see an error:
- "Attio did not accept that key": the token was not copied in full, or it has been deleted. Copy it again.
- "That key is missing permissions": edit the token in Attio, add the scopes the message lists, then try again.
Step 4: send a test capture
Send the bot on Telegram a screenshot of a profile, or forward an email to in@emails.useshmor.com, with a line such as "met at the fintech breakfast, follow up Friday". Then open Attio and check:
- the company, found by web domain then by name, or created;
- the person, found by email, then LinkedIn URL, then name and company, and linked to the company;
- Met via and Met at filled in on the person;
- a note with your context and the original message;
- a task due on Friday, linked to the person.2
If Shmor cannot tell which workspace member you are, tasks and deals are created unassigned.
Signing in with Attio instead
Where Shmor's Attio app is set up, the Attio card also shows a Connect Attio button that uses Attio's own sign-in page instead of a token. Both connect the same way; the token route works without the app.
Disconnecting
Click Disconnect on the Attio card in Shmor. Shmor stops writing contacts until you connect a CRM again, and nothing in Attio is deleted. To revoke access completely, delete the token on the Developers page in Attio.1