Attio

Overview

Connect your users to Attio for relationship-driven CRM, pipeline management, and workspace collaboration.

Property	Value
Provider ID	attio
Category	CRM
PKCE	Supported
Token refresh	Automatic
Redirect URI	Shown in Developer Portal

Step 1: Create an Attio OAuth App

Go to the Attio Developer Dashboard

Navigate to the Attio developer dashboard and sign in.

Create a new integration

Click Create a new integration and enter the integration name and description.

Configure OAuth

Under OAuth, add the Alter callback URL (from the Developer Portal) to Redirect URIs.

Select scopes

Select the scopes your integration needs. See Available Scopes below.

Get credentials

Copy the Client ID and Client Secret.

Warning

Never share your Client Secret publicly. Store it securely and only enter it in the Alter Vault Developer Portal.

Step 2: Add to Alter Vault

Open the Developer Portal

Go to portal.alterauth.com and navigate to the application.

Add Attio provider

Go to OAuth Providers > Add Provider > Attio.

Enter credentials

• Client ID: Paste your Attio Client ID
• Client Secret: Paste your Attio Client Secret

Select scopes

Choose the scopes the application needs.

Save

Click Save. The provider is now active.

Available Scopes

Records

Scope	Description
record_permission:read	Read access to records (people, companies, etc.)
record_permission:read-write	Read and write access to records

List Entries

Scope	Description
list_entry:read	Read access to list entries
list_entry:read-write	Read and write access to list entries

Notes

Scope	Description
note:read	Read access to notes
note:read-write	Read and write access to notes

Tasks

Scope	Description
task:read	Read access to tasks
task:read-write	Read and write access to tasks

User Management

Scope	Description
user_management:read	Read access to workspace user management

Webhooks

Scope	Description
webhook:read-write	Create and manage webhooks

Object Configuration

Scope	Description
object_configuration:read	Read access to object and attribute configuration
object_configuration:read-write	Read and write access to object and attribute configuration

MCP

Scope	Description
mcp	Access the Attio MCP (Model Context Protocol) server

Notes

• Attio scopes follow a read/read-write pattern. Request only the access level the application needs.
• For most CRM use cases, record_permission:read and list_entry:read provide sufficient read-only access.
• See the Attio API documentation for more details on available endpoints.

Policy-cataloged operations

Alter policy rules can target these attested operations and families for operation-level and parameter-aware controls.

Operation ID	Families	Method	Provider path
post:/v2/comments	send	POST	/v2/comments
delete:/v2/comments/{comment_id}	delete	DELETE	/v2/comments/{comment_id}
delete:/v2/files/{file_id}	delete	DELETE	/v2/files/{file_id}
delete:/v2/lists/{list}/entries/{entry_id}	delete	DELETE	/v2/lists/{list}/entries/{entry_id}
delete:/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}	delete	DELETE	/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}
delete:/v2/notes/{note_id}	delete	DELETE	/v2/notes/{note_id}
delete:/v2/objects/{object}/records/{record_id}	delete	DELETE	/v2/objects/{object}/records/{record_id}
delete:/v2/tasks/{task_id}	delete	DELETE	/v2/tasks/{task_id}
delete:/v2/webhooks/{webhook_id}	admin, delete	DELETE	/v2/webhooks/{webhook_id}
patch:/v2/webhooks/{webhook_id}	admin, write	PATCH	/v2/webhooks/{webhook_id}
post:/v2/webhooks	admin, write	POST	/v2/webhooks
patch:/v2/lists/{list}	write	PATCH	/v2/lists/{list}
patch:/v2/lists/{list}/entries/{entry_id}	write	PATCH	/v2/lists/{list}/entries/{entry_id}
patch:/v2/objects/{object}	write	PATCH	/v2/objects/{object}
patch:/v2/objects/{object}/records/{record_id}	write	PATCH	/v2/objects/{object}/records/{record_id}
patch:/v2/tasks/{task_id}	write	PATCH	/v2/tasks/{task_id}
patch:/v2/{target}/{identifier}/attributes/{attribute}	write	PATCH	/v2/{target}/{identifier}/attributes/{attribute}
post:/v2/files	write	POST	/v2/files
post:/v2/files/upload	write	POST	/v2/files/upload
post:/v2/lists	write	POST	/v2/lists
post:/v2/lists/{list}/entries	write	POST	/v2/lists/{list}/entries
post:/v2/meetings	write	POST	/v2/meetings
post:/v2/meetings/{meeting_id}/call_recordings	write	POST	/v2/meetings/{meeting_id}/call_recordings
post:/v2/notes	write	POST	/v2/notes
post:/v2/objects	write	POST	/v2/objects
post:/v2/objects/records/search	write	POST	/v2/objects/records/search
post:/v2/objects/{object}/records	write	POST	/v2/objects/{object}/records
post:/v2/objects/{object}/records/query	write	POST	/v2/objects/{object}/records/query
post:/v2/tasks	write	POST	/v2/tasks
post:/v2/{target}/{identifier}/attributes	write	POST	/v2/{target}/{identifier}/attributes
post:/v2/{target}/{identifier}/attributes/{attribute}/options	write	POST	/v2/{target}/{identifier}/attributes/{attribute}/options
post:/v2/{target}/{identifier}/attributes/{attribute}/statuses	write	POST	/v2/{target}/{identifier}/attributes/{attribute}/statuses
put:/v2/objects/{object}/records	write	PUT	/v2/objects/{object}/records
put:/v2/objects/{object}/records/{record_id}	write	PUT	/v2/objects/{object}/records/{record_id}
get:/v2/comments/{comment_id}	read	GET	/v2/comments/{comment_id}
get:/v2/files/{file_id}	read	GET	/v2/files/{file_id}
get:/v2/files/{file_id}/download	read	GET	/v2/files/{file_id}/download
get:/v2/meetings/{meeting_id}/call_recordings	read	GET	/v2/meetings/{meeting_id}/call_recordings
get:/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}	read	GET	/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}
get:/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}/transcript	read	GET	/v2/meetings/{meeting_id}/call_recordings/{call_recording_id}/transcript