> For the complete documentation index, see [llms.txt](https://memoket.gitbook.io/attio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://memoket.gitbook.io/attio/connect-memoket-to-attio.md). # Connect Memoket to Attio Send selected recording content from Memoket to an existing person or company record in Attio. This guide explains setup, the data used by the integration, and why each permission is requested. ## Connect your workspace You need a Memoket account, an Attio workspace you can authorize, and access to the person or company record you want to use. 1. Open **Integrations** in Memoket and select **Attio**. 2. Choose **Connect**. Memoket opens Attio's authorization page. 3. Sign in to Attio if needed, select the appropriate workspace, review the permissions, and approve the connection. 4. Return to Memoket and check the connected workspace before selecting a destination. Authorization takes place through Attio's OAuth flow. You do not provide your Attio password to Memoket. ## Send recording content 1. Open a processed recording in Memoket and choose **Share**, then **Attio**. 2. Choose **Companies** or **People** and search for an existing record. Company domains and people's email addresses help distinguish records with similar names. 3. Select the destination and the available content you want to send: **Brief**, **Summary**, **Transcript**, or a custom report from that recording. 4. Confirm the send, then open the selected record in Attio and check its notes. One send creates one Attio note, with the recording title as the note title and the selected text combined in its body. Memoket checks that the destination is still accessible before sending. The integration supports existing people and company records; it does not create, update, or delete these records or their attributes. ## Data read from Attio and how it is used **Connection information.** Memoket checks the authorized token's status, app identity, granted permissions, workspace ID, and workspace name. These identify and validate the connected workspace. If Attio returns the authorizing workspace member ID, it is used to distinguish the connection. **Destination records.** Memoket queries the selected people or companies object and uses record IDs, names, company domains, and people's email addresses to display searchable destinations. The record ID and object type identify where a note should be attached. A selected record is retrieved again to verify access before sending or saving an automatic destination. Attio's record API may return additional attributes. The integration's destination model uses the name, domain, and email fields described above; it does not copy other attributes into that model. This workflow does not use Attio records as source material for generating a recording's transcript or summary. **Send results.** When Attio creates a note, Memoket uses the returned note ID and parent record information to confirm the destination and record the send result. Connection credentials, workspace identifiers, selected destinations, automatic-send preferences, and send-status information support connection and delivery. Disconnecting is not a request to delete all export history. ## Data sent to Attio Memoket sends the selected destination's object type and record ID, the recording title, and the selected recording text. The text is submitted as Markdown to create a native Attio note. This is a one-way recording-content export. It does not upload the original audio file, import existing Attio notes into Memoket, or synchronize later edits between the two applications. The current integration does not fetch, edit, or delete existing Attio notes. The resulting note is subject to your Attio workspace's access permissions. ## Permissions and why they are needed Memoket requests these three OAuth scopes. A scope is a permission that Attio grants to the connected app. ### object\_configuration:read Attio requires this scope for record queries and for creating a note linked to a record. It enables the integration to address the supported people and companies objects. Memoket does not request permission to change object configuration. ### record\_permission:read Allows querying and retrieving existing people and company records for destination search and access checks. Attio also requires it when attaching a new note to a record. Memoket does not request record-write permission. ### note:read-write Allows creating the note containing the recording content you selected. This is the scope required by Attio's note-creation endpoint. Although the scope also grants access to existing notes, the current integration only creates notes and does not use it to fetch, update, or delete existing notes. No permissions for lists, tasks, comments, files, meetings, call recordings, webhooks, or workspace-member administration are requested for this integration. Attio's references document the required scopes for [listing records](https://docs.attio.com/rest-api/endpoint-reference/records/list-records) and [creating a note](https://docs.attio.com/rest-api/endpoint-reference/notes/create-a-note). ## Optional automatic sending Automatic sending is off by default. In the Attio integration settings, you can enable it, choose one existing person or company as the destination, and select Brief, Summary, and/or Transcript. Eligible new recordings are sent to that saved destination when processing completes. Enabling automatic sending or changing the destination does not backfill previous recordings. Review the saved destination carefully: automatic sending uses that choice. You can turn it off in the integration settings. ## Disconnect and manage access Open Attio's connection menu in Memoket and choose **Disconnect**. This removes the saved connection, clears destination settings, and disables automatic sending in Memoket. Notes already created in Attio remain there, and send-status history is not erased by disconnecting. To revoke the app's authorization at the provider, remove the Memoket app through your Attio workspace's app-management settings. Disconnecting in Memoket and revoking authorization in Attio are separate actions. ## Troubleshooting and support * **A record is missing:** check the connected workspace, confirm your Attio access, and search under the correct Companies or People category. * **Authorization or permissions have changed:** reconnect and review the permissions requested by Attio. * **Selected content is unavailable:** wait for the recording's processing to finish and select content that is available. * **A send result is uncertain:** check the destination's notes before sending again to avoid creating a duplicate. For help, contact . See the [Memoket website](https://memoket.ai/) and [terms of service](https://memoket.ai/policies/terms-of-service).