How do you build an n8n AI agent for your CRM?
Trigger on a CRM webhook, give the AI Agent node your CRM's MCP tools, and put a human review step on anything that sends.
The short answer
- You build an n8n AI agent for a CRM by connecting n8n's AI Agent node to the CRM's MCP server through the MCP Client Tool node, then choosing which tools the agent may call.
- n8n's MCP Client Tool node accepts Bearer, header, multiple-header and OAuth2 credentials, and lets you expose all tools, selected tools, or all except a list, per n8n's docs in September 2026.
- n8n's human-in-the-loop setting pauses the workflow before a chosen tool runs and asks a person to approve or deny it in Slack, Teams, Telegram, Gmail or n8n Chat.
- SalesCrew connects to n8n through its MCP server, outbound webhooks and API, with every action available as one of 140+ MCP tools.
Build the agent in five steps
Node names from n8n's documentation, checked September 2026.
- 1
Start from a CRM event
Add a Webhook trigger in n8n and copy its URL. In your CRM, send the events you care about to it, such as a new lead or a deal stage change.
- 2
Add the AI Agent node
Connect a chat model to n8n's AI Agent node. Write a short system prompt that names the job, for example: qualify the new lead and add a note with your reasoning.
- 3
Give the agent your CRM's tools
Attach an MCP Client Tool node to the agent's Tools connector. Enter your CRM's MCP server address and a credential for your own user.
- 4
Pick the tools it may call
Under Tools to Include, choose Selected and tick only what this job needs. A lead qualifier needs search, read and note tools, not delete or send.
- 5
Gate the risky tools
Open the Tools panel on the AI Agent node, add a Human review step, pick an approval channel, and move any send or update tool behind it.
Keep each agent to one job
An n8n agent with every CRM tool attached will find creative ways to use them. You'll get better results from a narrow agent. Give the lead qualifier five tools, give the follow-up drafter five others, and let each workflow do one thing well.
Narrow tool lists also make review easier. When a reviewer sees an approval request in Slack, they should know from the tool name what's about to happen. So name your workflows after the job, and keep the prompt short enough that a teammate can read it.
Which n8n pieces do what
Read on n8n's own documentation.
| n8n piece | Role in a CRM agent | Setting to check |
|---|---|---|
| Webhook trigger | Starts the workflow when the CRM posts an event | The URL your CRM sends to |
| AI Agent node | Decides which tool to call and with what input | The system prompt and model |
| MCP Client Tool node | Exposes the CRM's MCP tools to the agent | Credential and Tools to Include |
| Human review step | Pauses a chosen tool call until a person approves | Approval channel and which tools sit behind it |
Checked on docs.n8n.io (MCP Client Tool; Human-in-the-loop for tools), September 2026.
How SalesCrew fits into an n8n agent
SalesCrew is an AI-native CRM, and every action in its app is also an MCP tool. Point n8n's MCP Client Tool at your SalesCrew MCP server URL and add a Bearer credential with your own MCP token. The agent then sees the same tools you'd use in the app, limited to your scopes.
On the trigger side, SalesCrew's outbound webhooks post events such as lead.created, deal.stage_changed and meeting.booked as signed JSON, with retries on failure. Any external send the agent starts still waits in SalesCrew's approval queue by default, so there's a second check inside the CRM. See the n8n integration page or the MCP server overview.
Give the agent its own token
Questions
- Does n8n have an MCP client?
- Yes. n8n's MCP Client Tool node connects an AI Agent to the tools an external MCP server exposes, per n8n's docs in September 2026. It supports Bearer, header, multiple-header and OAuth2 credentials. You can expose all of the server's tools, a selected list, or all except the ones you exclude.
- Can an n8n AI agent update CRM records on its own?
- Yes, if the CRM's MCP server or API gives it write tools. For anything that sends or deletes, switch on n8n's human review step for that tool, so the workflow pauses until a person approves or denies it. Reads and notes can run straight through.
- Should I use a webhook or MCP to connect n8n to a CRM?
- Use a webhook to start the workflow and MCP for the agent's actions. A CRM webhook tells n8n something happened, such as a new lead. The MCP Client Tool then gives the agent the CRM's tools, so it can look up the record and write back without you building one HTTP node per action.
- How does SalesCrew connect to n8n?
- SalesCrew connects to n8n through its MCP server, its outbound webhooks and its API. Webhooks post signed JSON events with retries. The MCP server gives n8n's agent 140+ tools under your own token's scopes.