Aircall Help Center | AI Actions: Setting up Attio actions for your AI Voice Agent

AI Actions: Setting up Attio actions for your AI Voice Agent

The Attio MCP integration connects your AI Voice Agent with Attio CRM, allowing AI agents to search CRM records, create or update people, add notes, create follow-up tasks, and understand what attributes exist on Attio objects.

You can use Attio Flows to trigger AI voice agents when something happens in your CRM. The agent can then proactively call leads and customers, qualify opportunities, follow up with prospects, collect information, and update Attio with the outcome, automatically turning CRM events into real conversations and next steps.

Typical uses include lead qualification, sales follow-up, re-engagement, customer check-ins, and data enrichment.

How it works on inbound and outbound calls

Whoever starts the conversation, the result is the same: Attio is updated and a next step is created.

Inbound calls: a customer calls and the agent talks to them. An Attio record is found, created, or updated, and the next task is created.
Outbound calls: an Attio event triggers an AI call and the agent has the conversation. The conversation is captured, Attio is updated, and the next action is created.

The same Attio integration and actions work for both. To set up an agent that makes outbound calls, see the Outbound AI Voice Agent setup guide.

Important: The agent can change real Attio data. Attio supports write actions, so your instructions should clearly define what the agent is allowed to do. For example, decide whether it can create new people, update existing records, create notes, create tasks, or only read and search CRM data.

Before you begin

An Attio account.
At least one AI Voice Agent created. If you don't have one yet, please see Configuring your AI Voice Agent first, then come back to this guide.
Admin permissions on the Aircall Dashboard.

Actions and use cases

Attio <> Aircall Agentic integration gives you three building blocks.

Building block	What it defines	Examples
Use cases	Who the agent is, and the business outcome it supports	Lead qualification, sales follow-up, re-engagement, customer check-ins, data enrichment
Action groups	What the agent can do for a caller or a CRM-triggered workflow	Finding a CRM record, creating a new person, logging a note, updating a person, creating a follow-up task
Actions	What the agent can access and change in Attio	Searching records, creating records, upserting records, creating notes, creating tasks, listing attribute definitions

AI actions

These are the individual tools available to your agent through the Attio MCP integration. They give the agent access to specific CRM workflows: record search, people creation, person upsert and update, note creation, task creation, and attribute discovery.

Attio actions fall into two types:

Read actions retrieve information, such as searching records or listing attribute definitions.
Write actions create or update CRM information, such as creating a person record, upserting a person record, creating a note, or creating a follow-up task.

Action	Type	What it does	Good to know
Search Records	Read	Performs full-text search for records in a given Attio object.	Finds existing people or companies by indexed attributes such as email, phone, name or title, domain, description, social handle, or location.
List Attribute Definitions	Read	Lists metadata for the attributes on an object, including real slugs, types, required fields, and valid select and status options.	Optional for normal creates and updates. Used to discover custom attributes or to answer what information can be stored on a record.
Create Record	Write	Creates a brand-new CRM person record from structured profile data.	Used for new contacts, leads, or customers. The object is set exactly to people. Note text and follow-up details don't go into profile values.
Upsert Record	Write	Creates or updates a CRM person or contact record by matching an existing unique attribute.	Used when the caller provides a unique identifier such as an email and asks to create or update contact details. Attributes are passed as CRM value-entry arrays.
Create Note	Write	Creates a new note attached to an existing Attio record and returns the note ID.	Requires a parent object and a parent record ID. The agent resolves or creates the record first. It never creates a standalone note or invents a parent record ID.
Create Task	Write	Creates a new follow-up task in Attio.	Used for callbacks, reminders, follow-ups, sending information, or actions the team should track. The task is linked to a record only if the object and record ID are known.

Common action combinations

Log a call note on an existing person: Search Records, then Create Note.
Create a brand-new person and log discussion context: Create Record, then Create Note.
Capture a callback request: Create Task.
Update a known contact using their email: Upsert Record.

Action groups

An action group combines Attio actions to handle one CRM task. Because Attio includes write actions, make the allowed outcome clear for each group: search only, create person, update person, log note, or create task.

Action group	What the agent does	Actions used	Example caller request
Find an existing CRM record	Finds an existing Attio record before answering CRM questions, logging notes, updating contact details, or creating linked tasks.	Search Records	"Can you find the record for maria@example.com before logging this call?"
Create or update a person record	Creates a new person, or updates an existing one, using structured profile information from the caller or workflow.	Create Record, or Upsert Record	"Add Don Lopez, don@northwind.io, as a brand-new lead."
Log a CRM note	Records what was discussed as a note on an existing or newly created Attio record.	Search Records, then Create Note. Or Create Record, then Create Note	"Log that we discussed the enterprise migration timeline and they want a proposal next week."
Create a follow-up task	Creates a task when the conversation ends in a callback, reminder, follow-up, information request, or next action for the team.	Create Task	"Create a task for sales to call this lead back tomorrow about pricing."
Discover CRM attributes	Checks the attributes available on an Attio object, especially before writing to custom fields or explaining what data can be stored.	List Attribute Definitions	"Can this people record store a LinkedIn URL or customer tier?"
End-to-end CRM call outcome	Combines record lookup, profile updates, notes, and tasks to turn a call outcome into CRM data and a clear next step.	Search Records, then Upsert Record, then Create Note, then Create Task	"We qualified a new lead, captured their needs, and sales should follow up next Tuesday."

Use cases

A use case defines who your agent is, what role it plays, and how it talks to leads, prospects, and customers. Each one combines Attio action groups into a specific CRM workflow.

For Attio, the strongest loop is between CRM events and real conversations: an Attio event triggers an AI call, the agent has the conversation, and the agent updates Attio and creates next actions.

Lead qualification, sales follow-up, re-engagement, and customer check-ins each combine four action groups: find an existing CRM record, create or update a person record, log a CRM note, and create a follow-up task. Data enrichment combines discover CRM attributes, find an existing CRM record, create or update a person record, and log a CRM note.

Use case	What the agent does	Keep in mind
Lead qualification	Qualifies new leads with a real conversation. When a new lead enters Attio, a Flow can trigger an outbound AI call. The agent asks qualification questions, captures the answers, updates the lead record, and creates the follow-up task for sales.	Never guess record IDs, attribute slugs, select or status values, emails, phone numbers, assignee IDs, or deadlines. Record the lead's own words where possible.
Sales follow-up	Follows up with prospects at the right moment. When a prospect reaches a specific stage or needs follow-up, Attio can trigger an AI call. The agent continues the conversation, captures the response, updates the CRM, and creates the next task.	Don't overwrite CRM information unless the prospect clearly gives updated information. Don't invent follow-up dates, assignees, or record links. If several records match, ask before writing.
Re-engagement	Turns cold or inactive opportunities back into conversations. Attio can trigger an outbound AI call when a prospect has gone inactive or an opportunity meets specific criteria. The agent re-engages the prospect, understands their situation, updates the record, and routes the opportunity to sales when there's renewed interest.	Don't pressure uninterested prospects. Don't create tasks for vague interest unless your workflow requires it. Record negative outcomes accurately and respectfully.
Customer check-ins	Checks in with customers without adding work for your team. Trigger an AI call when an account reaches a milestone, has been inactive, or needs a check-in. The agent gathers feedback, captures new information, updates the customer record, and creates follow-up actions for the account team.	Don't invent sentiment, health scores, risks, or opportunities. Don't promise actions outside the workflow: create a task for the responsible team instead. Only record information relevant to the business relationship.
Data enrichment	Keeps CRM data fresh through real conversations. When a record is missing important information, Attio can trigger an AI call to collect it from the contact. The agent asks the relevant questions and updates the CRM with what it gathers.	Ask only necessary questions. Don't infer missing details. Check attribute definitions before writing to custom attributes, and use only valid select and status options.

Setting up Attio AI Actions

Step 1: Install Attio AI Actions

Steps

Go to Aircall Dashboard > Integrations > Apps.
If Attio isn't installed yet, go to the Agentic integration collection in Integrations, click Install, and log in to Attio if needed.
Open the Attio integration and select the AI Actions tab.
Install the Attio AI Actions.

Note: Installing the AI Actions only makes them available. An agent uses them once you add them in Step 2.

Step 2: Add Attio actions to your AI Voice Agent

Steps

Go to Aircall Dashboard > AI Agents > AI Voice Agents and open the agent you want to configure.
Under Functional abilities, click AI actions.
Click + Add action.
In Select from integrations list, search Attio and pick an action.
Review the preset instructions and required inputs, then click Add action. Repeat for each action you want the agent to use.
Click Save.
Click Activate agent to start using it for your calls.

Note: If an Attio action is missing from the dropdown, the Attio AI Actions aren't installed yet. Go back to Step 1.

Starter prompt

Here's a starting prompt that turns a call into CRM updates and a next step. Paste it into your Conversation guidelines and adapt it to your agent.

**Capture an end-to-end Attio call outcome**

Turn a conversation into accurate CRM updates and next actions.

1. Resolve the person record using **Search Records**, or create/upsert the person when the caller is new or provides a unique identifier.
2. Update structured CRM fields only when the caller provides clear profile or qualification data and the attribute is known.
3. Use **Create Note** to capture the conversation summary, qualification answers, objections, buying timeline, feedback, or call outcome.
4. Use **Create Task** when there is a follow-up, callback, reminder, handoff, or next action.
5. Keep profile data, notes, and tasks separate.

Do not invent missing CRM data. Do not claim an update, note, or task was completed until the relevant write action succeeds.

Step 3: Testing your setup

Test in two stages before you go live.

AI Actions Testing tab (MCP Playground)

Go to Aircall Dashboard > Integrations > Apps.
Open your Attio integration and go to the AI Actions Testing tab, which opens the MCP Playground.
Select an action from the dropdown and fill in its parameters.
Click Execute to check the connection. The result appears in the Output panel.

Test call

Go to Aircall Dashboard > AI Agents > AI Voice Agents and open the agent you want to test.
Click Test Call to simulate a real conversation from start to finish.

Important: Test calls use AI Voice Agent minutes and can change real Attio data. Create Record, Upsert Record, Create Note, and Create Task are write actions, so anything they create or update during testing is real.

Tip: If an action fails in the MCP Playground, check the Attio connection. If it works there but the agent didn't use it on a call, check that the action is added to the agent and that your Conversation guidelines say when to use it. After each change to your rules, make a new test call.

Guidelines for every Attio agent

Use only the actions the request needs.
Work only with real record IDs that Attio returns.
Never guess or make up record IDs, workspace member IDs, attribute slugs, select or status options, emails, phone numbers, or task deadlines.
If you need to attach a note and don't have the record ID, search for the person or company first.
Create a new person only for brand-new people, or when the caller asks to be set up as a customer, contact, or lead.
Use upsert when the caller gives a unique identifier, such as an email, and asks to create or update their details.
Add a note only once you have a real record to attach it to. A note can't exist on its own.
Use tasks for callbacks, follow-ups, reminders, information to send, or anything your team should track.
Check attribute definitions only to discover custom fields or see what a record can store. They're optional for normal person creation or standard people attributes.
If several records match, ask a short question before writing to any record.
Keep profile data, notes, and tasks separate.
Don't say a note, update, or task was saved until the action has succeeded.

FAQs

Does the agent change my Attio data?

Yes. Attio actions can create and update real CRM data: people, notes, and tasks. Your instructions define which of these the agent is allowed to do.

Which Attio records can the agent work with?

It can search for people and companies, and create or update people. Notes and tasks can be attached to a record once the agent has found or created it.

Can the agent add a note without a record?

No. A note can't exist on its own. The agent finds or creates the record first.

What if several Attio records match the caller?

The guidelines above have the agent ask a short question to confirm which record is right before it writes to any record.

Can the agent assign a task to a specific person?

Only when it already has that person's valid Attio workspace member ID. Otherwise, the task is created without an assignee.

Will the agent tell the caller something was saved before it's saved?

It shouldn't. The guidelines above tell the agent not to say a note, update, or task was saved until the action has succeeded.

Typical uses include lead qualification, sales follow-up, re-engagement, customer check-ins, and data enrichment.

How it works on inbound and outbound calls

Whoever starts the conversation, the result is the same: Attio is updated and a next step is created.

Inbound calls: a customer calls and the agent talks to them. An Attio record is found, created, or updated, and the next task is created.
Outbound calls: an Attio event triggers an AI call and the agent has the conversation. The conversation is captured, Attio is updated, and the next action is created.

The same Attio integration and actions work for both. To set up an agent that makes outbound calls, see the Outbound AI Voice Agent setup guide.

Important: The agent can change real Attio data. Attio supports write actions, so your instructions should clearly define what the agent is allowed to do. For example, decide whether it can create new people, update existing records, create notes, create tasks, or only read and search CRM data.

Before you begin

An Attio account.
At least one AI Voice Agent created. If you don't have one yet, please see Configuring your AI Voice Agent first, then come back to this guide.
Admin permissions on the Aircall Dashboard.

Actions and use cases

Attio <> Aircall Agentic integration gives you three building blocks.

Building block	What it defines	Examples
Use cases	Who the agent is, and the business outcome it supports	Lead qualification, sales follow-up, re-engagement, customer check-ins, data enrichment
Action groups	What the agent can do for a caller or a CRM-triggered workflow	Finding a CRM record, creating a new person, logging a note, updating a person, creating a follow-up task
Actions	What the agent can access and change in Attio	Searching records, creating records, upserting records, creating notes, creating tasks, listing attribute definitions

AI actions

Attio actions fall into two types:

Read actions retrieve information, such as searching records or listing attribute definitions.
Write actions create or update CRM information, such as creating a person record, upserting a person record, creating a note, or creating a follow-up task.

Action	Type	What it does	Good to know
Search Records	Read	Performs full-text search for records in a given Attio object.	Finds existing people or companies by indexed attributes such as email, phone, name or title, domain, description, social handle, or location.
List Attribute Definitions	Read	Lists metadata for the attributes on an object, including real slugs, types, required fields, and valid select and status options.	Optional for normal creates and updates. Used to discover custom attributes or to answer what information can be stored on a record.
Create Record	Write	Creates a brand-new CRM person record from structured profile data.	Used for new contacts, leads, or customers. The object is set exactly to people. Note text and follow-up details don't go into profile values.
Upsert Record	Write	Creates or updates a CRM person or contact record by matching an existing unique attribute.	Used when the caller provides a unique identifier such as an email and asks to create or update contact details. Attributes are passed as CRM value-entry arrays.
Create Note	Write	Creates a new note attached to an existing Attio record and returns the note ID.	Requires a parent object and a parent record ID. The agent resolves or creates the record first. It never creates a standalone note or invents a parent record ID.
Create Task	Write	Creates a new follow-up task in Attio.	Used for callbacks, reminders, follow-ups, sending information, or actions the team should track. The task is linked to a record only if the object and record ID are known.

Common action combinations

Log a call note on an existing person: Search Records, then Create Note.
Create a brand-new person and log discussion context: Create Record, then Create Note.
Capture a callback request: Create Task.
Update a known contact using their email: Upsert Record.

Action groups

Action group	What the agent does	Actions used	Example caller request
Find an existing CRM record	Finds an existing Attio record before answering CRM questions, logging notes, updating contact details, or creating linked tasks.	Search Records	"Can you find the record for maria@example.com before logging this call?"
Create or update a person record	Creates a new person, or updates an existing one, using structured profile information from the caller or workflow.	Create Record, or Upsert Record	"Add Don Lopez, don@northwind.io, as a brand-new lead."
Log a CRM note	Records what was discussed as a note on an existing or newly created Attio record.	Search Records, then Create Note. Or Create Record, then Create Note	"Log that we discussed the enterprise migration timeline and they want a proposal next week."
Create a follow-up task	Creates a task when the conversation ends in a callback, reminder, follow-up, information request, or next action for the team.	Create Task	"Create a task for sales to call this lead back tomorrow about pricing."
Discover CRM attributes	Checks the attributes available on an Attio object, especially before writing to custom fields or explaining what data can be stored.	List Attribute Definitions	"Can this people record store a LinkedIn URL or customer tier?"
End-to-end CRM call outcome	Combines record lookup, profile updates, notes, and tasks to turn a call outcome into CRM data and a clear next step.	Search Records, then Upsert Record, then Create Note, then Create Task	"We qualified a new lead, captured their needs, and sales should follow up next Tuesday."

Use cases

A use case defines who your agent is, what role it plays, and how it talks to leads, prospects, and customers. Each one combines Attio action groups into a specific CRM workflow.

For Attio, the strongest loop is between CRM events and real conversations: an Attio event triggers an AI call, the agent has the conversation, and the agent updates Attio and creates next actions.

Use case	What the agent does	Keep in mind
Lead qualification	Qualifies new leads with a real conversation. When a new lead enters Attio, a Flow can trigger an outbound AI call. The agent asks qualification questions, captures the answers, updates the lead record, and creates the follow-up task for sales.	Never guess record IDs, attribute slugs, select or status values, emails, phone numbers, assignee IDs, or deadlines. Record the lead's own words where possible.
Sales follow-up	Follows up with prospects at the right moment. When a prospect reaches a specific stage or needs follow-up, Attio can trigger an AI call. The agent continues the conversation, captures the response, updates the CRM, and creates the next task.	Don't overwrite CRM information unless the prospect clearly gives updated information. Don't invent follow-up dates, assignees, or record links. If several records match, ask before writing.
Re-engagement	Turns cold or inactive opportunities back into conversations. Attio can trigger an outbound AI call when a prospect has gone inactive or an opportunity meets specific criteria. The agent re-engages the prospect, understands their situation, updates the record, and routes the opportunity to sales when there's renewed interest.	Don't pressure uninterested prospects. Don't create tasks for vague interest unless your workflow requires it. Record negative outcomes accurately and respectfully.
Customer check-ins	Checks in with customers without adding work for your team. Trigger an AI call when an account reaches a milestone, has been inactive, or needs a check-in. The agent gathers feedback, captures new information, updates the customer record, and creates follow-up actions for the account team.	Don't invent sentiment, health scores, risks, or opportunities. Don't promise actions outside the workflow: create a task for the responsible team instead. Only record information relevant to the business relationship.
Data enrichment	Keeps CRM data fresh through real conversations. When a record is missing important information, Attio can trigger an AI call to collect it from the contact. The agent asks the relevant questions and updates the CRM with what it gathers.	Ask only necessary questions. Don't infer missing details. Check attribute definitions before writing to custom attributes, and use only valid select and status options.

Setting up Attio AI Actions

Step 1: Install Attio AI Actions

Steps

Go to Aircall Dashboard > Integrations > Apps.
If Attio isn't installed yet, go to the Agentic integration collection in Integrations, click Install, and log in to Attio if needed.
Open the Attio integration and select the AI Actions tab.
Install the Attio AI Actions.

Note: Installing the AI Actions only makes them available. An agent uses them once you add them in Step 2.

Step 2: Add Attio actions to your AI Voice Agent

Steps

Go to Aircall Dashboard > AI Agents > AI Voice Agents and open the agent you want to configure.
Under Functional abilities, click AI actions.
Click + Add action.
In Select from integrations list, search Attio and pick an action.
Review the preset instructions and required inputs, then click Add action. Repeat for each action you want the agent to use.
Click Save.
Click Activate agent to start using it for your calls.

Note: If an Attio action is missing from the dropdown, the Attio AI Actions aren't installed yet. Go back to Step 1.

Starter prompt

Here's a starting prompt that turns a call into CRM updates and a next step. Paste it into your Conversation guidelines and adapt it to your agent.

**Capture an end-to-end Attio call outcome**

Turn a conversation into accurate CRM updates and next actions.

1. Resolve the person record using **Search Records**, or create/upsert the person when the caller is new or provides a unique identifier.
2. Update structured CRM fields only when the caller provides clear profile or qualification data and the attribute is known.
3. Use **Create Note** to capture the conversation summary, qualification answers, objections, buying timeline, feedback, or call outcome.
4. Use **Create Task** when there is a follow-up, callback, reminder, handoff, or next action.
5. Keep profile data, notes, and tasks separate.

Do not invent missing CRM data. Do not claim an update, note, or task was completed until the relevant write action succeeds.

Step 3: Testing your setup

Test in two stages before you go live.

AI Actions Testing tab (MCP Playground)

Go to Aircall Dashboard > Integrations > Apps.
Open your Attio integration and go to the AI Actions Testing tab, which opens the MCP Playground.
Select an action from the dropdown and fill in its parameters.
Click Execute to check the connection. The result appears in the Output panel.

Test call

Go to Aircall Dashboard > AI Agents > AI Voice Agents and open the agent you want to test.
Click Test Call to simulate a real conversation from start to finish.

Important: Test calls use AI Voice Agent minutes and can change real Attio data. Create Record, Upsert Record, Create Note, and Create Task are write actions, so anything they create or update during testing is real.

Tip: If an action fails in the MCP Playground, check the Attio connection. If it works there but the agent didn't use it on a call, check that the action is added to the agent and that your Conversation guidelines say when to use it. After each change to your rules, make a new test call.

Guidelines for every Attio agent

Use only the actions the request needs.
Work only with real record IDs that Attio returns.
Never guess or make up record IDs, workspace member IDs, attribute slugs, select or status options, emails, phone numbers, or task deadlines.
If you need to attach a note and don't have the record ID, search for the person or company first.
Create a new person only for brand-new people, or when the caller asks to be set up as a customer, contact, or lead.
Use upsert when the caller gives a unique identifier, such as an email, and asks to create or update their details.
Add a note only once you have a real record to attach it to. A note can't exist on its own.
Use tasks for callbacks, follow-ups, reminders, information to send, or anything your team should track.
Check attribute definitions only to discover custom fields or see what a record can store. They're optional for normal person creation or standard people attributes.
If several records match, ask a short question before writing to any record.
Keep profile data, notes, and tasks separate.
Don't say a note, update, or task was saved until the action has succeeded.

FAQs

Does the agent change my Attio data?

Yes. Attio actions can create and update real CRM data: people, notes, and tasks. Your instructions define which of these the agent is allowed to do.

Which Attio records can the agent work with?

It can search for people and companies, and create or update people. Notes and tasks can be attached to a record once the agent has found or created it.

Can the agent add a note without a record?

No. A note can't exist on its own. The agent finds or creates the record first.

What if several Attio records match the caller?

The guidelines above have the agent ask a short question to confirm which record is right before it writes to any record.

Can the agent assign a task to a specific person?

Only when it already has that person's valid Attio workspace member ID. Otherwise, the task is created without an assignee.

Will the agent tell the caller something was saved before it's saved?

It shouldn't. The guidelines above tell the agent not to say a note, update, or task was saved until the action has succeeded.