Rémi KokabiNovember 4, 20267 min read
lemlist and Attio MCP use cases
A deal moves to “qualified” in Attio. The company record has a domain, a deal stage, a owner. No contact attached, no sequence running, nothing happening in lemlist. Someone has to notice, export, enrich, and build a campaign by hand before the lead goes cold.
That gap is where most attio lemlist integration setups break down. The data sits in Attio, the outreach engine sits in lemlist, and connecting the two usually means a workflow built in advance for one specific trigger. Most of the real work doesn’t fit that mold.
I’m going to show you two ways to close that gap: the native sync that keeps both tools updated in the background, and MCP prompts you can run today to fill missing contacts, activate a saved list, or log reply status back on a record. No workflow builder required for either.
You’ll get the exact prompts, what the agent does with each one, and what to check before you let it touch a full list. Copy them, run them small first, then scale.
Native integration or MCP, what each one does
lemlist connects to Attio through a native integration that syncs contacts, campaigns, and activity between both tools automatically. The MCP path is different: it lets an AI agent in Claude, ChatGPT, or Cursor read and act on data in both Attio and lemlist inside a single conversation, on demand.
The native integration lets you add people to campaigns from their record, enrich records with data from lemlist, and start workflows when something happens in a campaign. You can use lemlist triggers inside Attio, from email opens and LinkedIn interactions to call outcomes. It runs in the background once you connect an API key.
The value of MCP is letting one agent work across Attio and every other MCP-connected tool at the same time. That means filling gaps in Attio records with lemlist’s People database, activating a saved list as a campaign, or writing outreach status back to CRM records, all from a prompt.
Here is how the two paths compare:
Native integration | MCP | |
|---|---|---|
What it does | Syncs contacts, triggers Attio workflows on lemlist activity, enrolls leads in campaigns from Attio | Lets an AI agent read and write in both tools through natural language prompts |
When it runs | Continuously, in the background | On demand, when you prompt the agent |
Who sets it up | RevOps or an admin, via API key in Attio settings | Anyone who connects both MCP servers in an AI client |
Best for | Ongoing data sync, workflow automation, campaign enrollment at scale | Ad hoc enrichment, cross-tool queries, acting on lists without building a workflow first |
The MCP does not replace the native integration. Use both: the integration for continuous sync, the MCP for the questions and actions that fall in between.
What you need before you start
The lemlist MCP server connected in Claude, ChatGPT, or Cursor. Follow the steps in how to set up the lemlist MCP to generate your API key and add the server URL to your client.
The Attio MCP server connected in the same client. Add
https://mcp.attio.com/mcpas a remote MCP server and complete the OAuth flow when prompted.Permissions scoped to what the use cases below actually need. If you only plan to read data, start with read-only access in both tools.
Start with read-only prompts before letting the agent write in either tool. Run a query, check the output, then move to prompts that create or update records.
1. Fill companies with no contact
Attio records often have the company name, domain, and deal stage, but no people attached. Without contacts, nobody on the team can start outreach, and the record sits idle.
Copy this prompt into your AI client with both MCP servers connected:
Find Attio companies in my target list with no contact, get the VP Sales and Head of RevOps from lemlist, and add them to each record.
The agent reads your Attio company list, filters for records with zero associated people, then searches lemlist’s People database for matching contacts by company domain and title. It enriches each contact with verified email and phone through waterfall enrichment, then writes the people back into the corresponding Attio record.
Before running this on a full list, test on five companies. Confirm the agent matched the right people to the right records and that the data landed in the correct Attio fields.
2. Activate an Attio list in one go
Turning a saved Attio list into a live campaign normally means exporting to CSV, cleaning the file, importing into lemlist, and mapping fields. That process eats time and introduces errors every time a column header doesn’t match.
Copy this prompt:
Take the Attio list 'Q4 targets', enrich every person with email and phone, and add them to a new lemlist campaign.
The agent reads every person in the Attio list, runs waterfall enrichment across 14+ providers to find verified emails and phone numbers, creates a new campaign in lemlist, and adds each enriched lead. No export, no CSV, no field mapping.
Before running on a full list, test on 10 leads. Check that enrichment returned valid contact data and that the campaign in lemlist has the right leads with the right variables.
3. Log outreach status back on records
Sales and RevOps teams want to see in Attio who is in a sequence, who opened, and who replied. Without that visibility, reps overlap on the same accounts, and managers lose track of pipeline coverage.
Copy this prompt:
For leads in lemlist campaigns this month, update their Attio record with the campaign name and reply status.
The agent reads every active campaign from the current month, pulls the lead list and each lead’s status (contacted, opened, replied, interested), then writes those values as attributes on the matching Attio person record. The result is a live view of outreach activity inside your CRM, without switching tabs.
Before running on all campaigns, test on one campaign. Verify the agent matched leads to the correct Attio records and that the attribute values are accurate.
Guardrails when an agent works in lemlist and Attio
When an AI agent has write access to two tools, small mistakes compound. These guardrails keep things under control:
Review every campaign the agent creates before you launch it. Check the sequence steps, timing, and lead list.
Test on 10 leads first. Run the full prompt only after you confirm the output is correct on a small batch.
Keep unsubscribes and exclusion lists active in lemlist. The agent respects them, but only if they are turned on.
Limit who on the team can connect the MCP servers. Treat MCP access like admin access to your CRM.
Log what the agent changed. After each session, check the records it created or updated in both Attio and lemlist. If your AI client shows a tool-call log, save it.
Run it in lemlist
Every prompt above relies on what the lemlist MCP server exposes to the agent. It works in Claude, ChatGPT, and Cursor.
Through the MCP, the agent can search the People database (650M+ contacts, 65M+ companies), enrich leads with waterfall enrichment across 14+ providers, and create campaigns and sequences across email, LinkedIn, calls, and WhatsApp. It can also read the unified inbox and campaign stats, and act on intent signals to prioritize who to reach first.
If you are building a B2B lead list from scratch or enriching an existing one, the agent handles both workflows from a single prompt.
Final takeaway
The native Attio integration keeps your CRM and outreach data in sync continuously. The MCP lets an AI agent act on that data, filling gaps, activating lists, and logging status, all from a single prompt. Together, they turn Attio from a system of record into a system that triggers real conversations.
Turn leads into pipeline
Find prospects, automate follow-ups, and generate more sales opportunities.