Memo for Attio
Memo is an AI assistant for sales teams. You tell it about a meeting in your own words, typed or dictated or from a call recording, and it prepares the Attio records that meeting should produce: the person, the company, the note, the deal and its stage, the follow-up task. Nothing reaches your workspace until someone approves it.
Before you start
- A Memo account at app.sentmemo.com. Memo is a paid product; if you do not have an account yet, write to us and we will set one up.
- An Attio workspace, and permission in it to install apps. Attio asks a workspace admin to approve the connection.
Connecting Memo to Attio
- Sign in at app.sentmemo.com.
- Open Settings → CRM.
- Choose Attio and select Connect. You are sent to Attio to authorise the connection.
- Review the permissions Attio lists and approve. You are returned to Memo, which confirms the workspace it is now connected to.
- Memo reads your objects and their fields once, so it knows what your workspace actually looks like, custom objects and custom attributes included. This takes a few seconds.
One Attio workspace connects to one Memo workspace. To move the connection to a different Attio workspace, disconnect first and connect again.
What Memo does with it
Writes up meetings. Describe a call and Memo drafts the records it implies: creating or matching the person and company, writing a note on the right record, opening or advancing a deal, and setting a follow-up task with an owner and a due date. Every write is shown as a proposal you approve, edit or reject.
Prepares the next meeting. Before a meeting in your calendar, Memo pulls what Attio already knows about the attendees and their company (the open deal and its stage, the last notes, who owns the relationship) and sends a brief. When the attendee is not in Attio yet, it prepares a first-meeting brief from public sources instead.
Keeps the pipeline honest. Memo watches for deals that have gone quiet, stage changes that imply a next step nobody took, and meetings that happened but were never logged, and raises them where you will see them.
Drafts the follow-up. Memo can draft the follow-up email in your own writing style, ready to review and send. It never sends anything on its own.
Permissions and what each one is for
| Scope | Why Memo asks for it |
|---|---|
record_permission:read-write |
Read the people, companies and deals a meeting is about, and create or update them once you approve a proposal. This is the core of the integration. |
object_configuration:read |
Read your objects, attributes and select options so proposals use your workspace's own fields and status values rather than guessed ones. Read-only: Memo never changes your schema. |
note:read-write |
Read existing notes for context when preparing a meeting, and write the meeting note you approve. |
task:read-write |
Read open tasks so Memo does not propose a duplicate, and create the follow-up task you approve. |
user_management:read |
Read workspace members so records can be assigned to the right owner, and so Memo can tell a colleague from an external contact. |
meeting:read |
Read meetings on the Attio timeline, so meeting prep and the quiet-deal check reflect what has actually happened. Optional: without it those features return nothing rather than failing. |
call_recording:read, webhook:read-write |
Only for workspaces that record calls with Attio's own call intelligence. Memo registers one webhook subscription on call-recording.created so a finished recording reaches it, then reads that recording and drafts the write-up. Creating the subscription is a write, which is why the webhook permission is read-write: Memo creates and deletes only its own subscription, pointed at its own endpoint, and never changes a webhook it did not create. Optional, and unnecessary if you record with something else. |
Approval, and what happens without it
Memo proposes; a person decides. Every change that overwrites a value, opens a deal, assigns work to someone or sends a message is shown for approval first, with the exact fields it would set. You can edit a proposal before approving it, and your edits teach Memo what your team wants next time.
A narrow set of purely additive actions, such as creating a record that does not exist yet or appending a note, can be configured to happen at proposal time, presented as work already done with an undo on each row. This is off by default and is enabled per workspace, on request.
AI-generated content
Memo uses large language models to read your notes and draft records, briefs and messages. Generated content can be inaccurate or incomplete, which is why nothing reaches Attio without a person approving it. Your Attio data is not used to train any model. See the Privacy Policy for what is processed, by which subprocessors, and for how long it is kept.
Disconnecting
Disconnect from Settings → CRM in Memo, or remove the Memo app from your Attio workspace settings. Either revokes the token immediately and Memo stops reading and writing. Records Memo already created stay in Attio; they are your records. To have the copies Memo holds deleted, tell us.
Troubleshooting
“Connect your CRM” after connecting. The token was revoked on the Attio side, usually by an admin removing the app. Reconnect from Settings → CRM.
Meeting prep is empty. The connection predates the meeting:read
permission. Disconnect and reconnect to grant it, because permissions granted earlier do not
widen on their own.
Deals are proposed against the wrong object. Some workspaces disable the standard Deals object and keep deals in a custom one. Memo reads your configuration and follows it; if it picked the wrong one, tell us which object is authoritative and we will pin it.