Attio
The Attio enables tools and to call Attio APIs on behalf of a .
Want to quickly get started with Attio in your or AI app? The pre-built Arcade Attio MCP server is what you want!
What’s documented here
This page describes how to use and configure Attio auth with Arcade.
This is used by:
- The Arcade Attio MCP server, which provides pre-built for interacting with Attio
- Your app code that needs to call Attio APIs
- Or, your custom tools that need to call Attio APIs
Use Arcade’s default Attio auth provider
Arcade offers a default Attio that you can use in the Arcade Cloud Platform. In this case, your will see Arcade as the name of the application requesting permission.
If you choose to use Arcade’s Attio auth, you don’t need to configure anything. Follow the Attio MCP server examples to get started calling Attio .
Use your own Attio app credentials
When using your own app credentials, make sure you configure your to use a custom user verifier. Without this, your end-users will not be able to use your app or in production.
In a production environment, you will most likely want to use your own Attio app credentials. This way, your will see your application’s name requesting permission.
Before showing how to configure your Attio app credentials, let’s go through the steps to create an Attio app.
Create an Attio app
You need an Attio workspace to create an OAuth app. If you don’t have one, sign up at attio.com .
- In your Attio workspace, go to Settings → Developer → Apps
- Click Create app and give it a name and description
- In your app’s settings, navigate to the OAuth tab
- Toggle Enable OAuth 2.0 at the top of the page
- Under Redirect URIs, add the redirect URL generated by Arcade (see below)
- Under Scopes, enable the scopes your app needs. If you plan to use the Arcade Attio MCP server, enable:
call_recording:readlist_configuration:read-writelist_entry:read-writemeeting:readnote:read-writeobject_configuration:read-writerecord_permission:read-writetask:read-writeuser_management:read
- Copy the Client ID and Client Secret from the OAuth tab
By default, your Attio app can only authorize in the workspace it was created in. To allow users from other workspaces to authorize your app, click Request publication in your app’s settings.
Configure your own Attio auth provider in Arcade
Dashboard GUI
Configure Attio auth using the Arcade Dashboard GUI
Access the Arcade Dashboard
To access the Arcade Cloud dashboard, go to api.arcade.dev/dashboard . If you are self-hosting, by default the dashboard will be available at http://localhost:9099/dashboard . Adjust the host and port number to match your environment.
Navigate to the OAuth Providers page
- Under the Connections section of the Arcade Dashboard left-side menu, click Connected Apps.
- Click Add OAuth Provider in the top right corner.
- Select the Included Providers tab at the top.
- In the Provider dropdown, select Attio.
Enter the provider details
- Enter
attioas the ID for your provider. - Optionally enter a Description.
- Enter the Client ID and Client Secret from your Attio app.
- Note the Redirect URL generated by Arcade. This must be added to your Attio app’s redirect URIs.
Create the provider
Hit the Create button and the provider will be ready to be used.
When you use tools that require Attio auth using your Arcade credentials, Arcade will automatically use this Attio OAuth provider. If you have multiple Attio providers, see using multiple auth providers of the same type for more information.
Using the Arcade Attio MCP server
The Arcade Attio MCP server provides to interact with Attio CRM objects, such as records, notes, tasks, lists, and meetings.
Refer to the MCP server documentation and examples to learn how to use the server to build and AI apps that interact with Attio.
Using Attio auth in app code
Use the Attio in your own and AI apps to get a -scoped token for the Attio API. See authorizing agents with Arcade to understand how this works.
Use client.auth.start() to get a token for the Attio API:
Python
from arcadepy import Arcade
client = Arcade() # Automatically finds the `ARCADE_API_KEY` env variable
user_id = "{arcade_user_id}"
# Start the authorization process
auth_response = client.auth.start(
user_id=user_id,
provider="attio",
scopes=[
"record_permission:read-write",
"note:read-write",
],
)
if auth_response.status != "completed":
print("Please complete the authorization challenge in your browser:")
print(auth_response.url)
# Wait for the authorization to complete
auth_response = client.auth.wait_for_completion(auth_response)
token = auth_response.context.token
# Do something interesting with the token...Using Attio auth in custom tools
You can author your own custom tools that interact with the Attio API.
Use the Attio() auth class to specify that a tool requires authorization with Attio. The authentication token needed to call the Attio API is available in the through the context.get_auth_token_or_empty() method.
from typing import Annotated import httpx from arcade_tdk import ToolContext, tool from arcade_tdk.auth import Attio @tool( requires_auth=Attio( scopes=["record_permission:read-write"], ) ) async def query_attio_companies( context: ToolContext, limit: Annotated[ int, "Maximum number of company records to return.", ] = 10, ) -> Annotated[dict, "List of company records from Attio"]: """Query company records from Attio.""" url = "https://api.attio.com/v2/objects/companies/records/query" headers = { "Authorization": f"Bearer {context.get_auth_token_or_empty()}", "Content-Type": "application/json", } async with httpx.AsyncClient() as http_client: response = await http_client.post( url, headers=headers, json={"limit": limit}, ) response.raise_for_status() return response.json()