Attio MCP integration for AI agents.
Connect AI agents to Attio through 10 structured actions, including get object, create record, delete record, and identify. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 10
- AUTHENTICATION
- OAuth 2.0 + API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Attio integration exposes
The Attio Agent App exposes 10 provider-backed actions for productivity and data work. Its current contract lets an authorized agent get one attio object by object id or api slug, create a record for an attio object using documented attribute value shapes, and delete a single attio record by object and record id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0 and API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Attio account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Attio capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_objectREADGet one Attio object by object ID or API slug.
INPUTS: object
create_recordWRITECreate a record for an Attio object using documented attribute value shapes.
INPUTS: object / values
delete_recordHIGH IMPACTDelete a single Attio record by object and record ID.
INPUTS: object / recordId
identifyREVIEWIdentify the current Attio access token, its workspace, and the scopes attached to it.
get_recordREADGet a single Attio record by object and record ID.
INPUTS: object / recordId
list_attributesREADList attributes defined on an Attio object or list.
INPUTS: target / identifier / limit / offset / showArchived
list_objectsREADList all system-defined and user-defined objects in an Attio workspace.
list_recordsREADList Attio records for an object with optional filtering, view filtering, sorting, limit, and offset.
INPUTS: object / filter / filterViewId / sorts / limit
update_recordWRITEUpdate an Attio record by appending or overwriting multiselect values according to Attio's PATCH and PUT semantics.
INPUTS: object / recordId / values / mode
upsert_recordWRITECreate or update an Attio record for an object using a unique matching attribute.
INPUTS: object / matchingAttribute / values
INPUT CONTRACTS
Know what the action needs before it runs.
get_object
objectOPTIONAL- The object ID or API slug, such as people or companies.
create_record
objectOPTIONAL- The object ID or API slug, such as people or companies.
valuesOPTIONAL- Record values keyed by Attio attribute API slug or attribute ID. Values are forwarded using Attio's documented attribute value shapes.
delete_record
objectOPTIONAL- The object ID or API slug, such as people or companies.
recordIdOPTIONAL- The Attio record UUID.
get_record
objectOPTIONAL- The object ID or API slug, such as people or companies.
recordIdOPTIONAL- The Attio record UUID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Object
Get one Attio object by object ID or API slug. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_objectControl Create Record
Create a record for an Attio object using documented attribute value shapes. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_recordVerify with Get Record
Get a single Attio record by object and record ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_recordSAFETY BOUNDARY
Operate Attio with explicit limits
- Authorize Attio with OAuth 2.0 and API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_record` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `record_permission:read-write`, `object_configuration:read`, and `record_permission:read`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Attio task completed successfully.
CONNECTION MODEL
OAuth 2.0 + API key
Attio access token sent as a Bearer token. Create or copy a token from the Attio developer dashboard: https://build.attio.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 5
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Attio.