Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Scopes: object_configuration:read, record_permission:read-write, list_configuration:read.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create an Attio app: Go to the Attio developer dashboard at https://build.attio.com/ and create a new app. Any Attio workspace (including the free plan) can be used for development.
  2. Configure OAuth: In the app’s OAuth settings, add the redirect URI <your-app-url>/api/auth/attio/callback and select the scopes object_configuration:read, record_permission:read-write, and list_configuration:read.
  3. Set credentials: Copy the client ID and client secret from the app settings into your .env as ATTIO_CLIENT_ID and ATTIO_CLIENT_SECRET.
  4. Verify access: Complete the OAuth flow, then run the List Objects tool followed by Query Records on the people object.

​
Provider notes

  • Attio access tokens expire; refresh tokens are exchanged at https://app.attio.com/oauth/token with grant_type=refresh_token
  • Client credentials are sent in the POST body (application/x-www-form-urlencoded) at the token endpoint
  • Record values use Attio’s attribute-value format: values are arrays of { value } entries keyed by attribute slug
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as attio__list_objects with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.