Attio

Live

OAUTH 2.0

CRM

CRM & Sales

Modern GTM teams track relationships in Attio. Your agent can read deal context, update records, and surface pipeline signals, scoped to the workspace member who authorized it.

  • Acts as the user: Record access and write actions stay tied to the workspace member who authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Attio
agent · Acme Q3
Run
Find all open deals over $50K and list the primary contact for each.
S
attio_records_search
78ms
CRM agent
4 open deals over $50K: Acme Corp ($120K, Sarah Chen), Globex ($85K, James Park), Initech ($72K, Maria Santos), Umbrella ($55K, David Kim).
Sources: 4 deals, Attio CRM
attiomcp
4 deals
18:29
Message Claude...

Tools your crm agent reaches for on Attio, scoped per user.

CALL ANY TOOL
Search records, manage contacts, update deals, and add notes. Same toolkit, every framework, no auth plumbing to maintain.
attio_records_search
Search records
Search records across object types using fuzzy text matching — people, companies, deals, or custom objects.
Parameters
Name
Type
Required
Description
query
string
Required
Search query string
object_type
string
Optional
Object type to search: people, companies, deals, or custom slug
limit
integer
Optional
Max results to return
attio_records_list
List records
attio_record_get
Get record
attio_record_update
Update record
attio_person_create
Create person
attio_note_create
Create note
Build your Agent
Drop the toolkit in, point it at the user, and your agent can search Attio records, update deals, and log notes from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["attio"], toolNames: ["attio_records_search", "attio_record_get", "attio_record_update"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["attio"], toolNames: ["attio_records_search", "attio_record_get", "attio_record_update"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["attio"], toolNames: ["attio_records_search", "attio_record_get", "attio_record_update"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/attio",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start pulling CRM intelligence from Attio.
Search & recall
Copy the prompt
Copied
Find all contacts at [company name].
Copy the prompt
Copied
Show me all open deals over $50K.
Copy the prompt
Copied
Search for [person name] in Attio.
Copy the prompt
Copied
List all companies in the [industry] sector.
Action & updates
Copy the prompt
Copied
Update the deal stage for [company] to Proposal.
Copy the prompt
Copied
Add a note to [person]'s record: [note text].
Copy the prompt
Copied
Create a new contact: [name], [email], [company].
Copy the prompt
Copied
Update the close date on [deal name] to [date].
Pipeline & reporting
Copy the prompt
Copied
What deals are closing this month?
Copy the prompt
Copied
List all contacts added in the last 7 days.
Copy the prompt
Copied
Show me all tasks assigned to me in Attio.
Copy the prompt
Copied
What is the total pipeline value for Q4?
SEE HOW AUTH WORKS
Users authorize Attio once. Their workspace credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Attio
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Attio
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Attio
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Attio
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other crm agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
CRM updates lose pipeline attribution
A shared Attio token looks fine in a demo. In production, every record update logs as a service account. List-level permissions collapse. Per-user pipeline visibility breaks. Scalekit resolves the credential of the actual BD or sales operator who triggered the agent, never a shared bot.
// shared bot token
token = "sk_attio_shared_xxx"
audit → bot_service_account
user_filter → broken

// scalekit · per-user
token = resolve(user_id)
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Attio today. HubSpot, Salesforce, Apollo tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Attio as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Attio oauth 2.0 stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Attio?
Yes. Pass a tool name filter to listScopedTools so the CRM agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Attio.
What happens when a user revokes Attio access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Does the agent respect record-level permissions in Attio?
Yes. Read and write actions inherit the authorizing user's Attio role and record access. List visibility, object scope, and field-level restrictions all carry over to every agent call.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""attio"": {
""url"": ""https://mcp.scalekit.com/attio"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.attio]
url = ""https://mcp.scalekit.com/attio""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""attio"": {
""url"": ""https://mcp.scalekit.com/attio"",
""type"": ""http""
}
}
}