n8n AI agent vs agents inside your CRM

An n8n agent is a workflow you build and host. A CRM agent runs on your records, with one approval queue and 140+ MCP tools behind it.

An admin approves every new account by hand. Nothing is created until then. We reply by email; no newsletter, no sequence.

app.salescrew.io/deals
Pipeline with weighted forecast and stage breakdown

An n8n AI Agent runs any tool you wire to it, with approval on the tools you choose (docs.n8n.io, checked September 2026). SalesCrew agents run on the CRM's own records, start in review mode, send every external action through one approval queue and log every call, and n8n reaches them through webhooks and MCP when you want both.

The short answer

  • The n8n AI Agent node pairs a chat model with tools and lets the agent pick which to call (docs.n8n.io, checked 24 September 2026).
  • n8n's human-in-the-loop setting pauses before chosen tools and asks for approval in Slack, Telegram or n8n Chat.
  • Every SalesCrew agent ships in review mode, and every external send waits in one approval queue with a kill switch that stops all agents.
  • n8n connects to SalesCrew through outbound webhooks, the API and the SalesCrew MCP server.

An n8n AI agent and SalesCrew's agents, side by side

Dimensionn8n AI AgentAgents inside SalesCrew
What you buildA workflow: chat model, tools, memory and triggers you wire togetherNothing to wire: agents act on the CRM's contacts, deals and inbox
ToolsAny node or MCP server you connect, chosen per agent140+ MCP tools, each with a UI twin that does the same thing
ApprovalHuman review on chosen tools via Slack, Telegram or n8n ChatOne queue grouped by agent, showing the artefact, evidence, confidence and cost
ModesHuman review on the tools you pickOff, draft, review or auto per agent; every agent ships in review
Hostingn8n Cloud or self-hostedEach client in its own database
Controls beside the queueApproval routed to the channel you configureKill switch for every agent, per-mailbox and per-domain caps, a send window, an audit log of every call

n8n facts checked on docs.n8n.io (AI Agent node, Human-in-the-loop for tools, MCP Client Tool), 24 September 2026. Disclosure: SalesCrew is our product.

What an n8n agent is good at

n8n shines when the job crosses many systems. Your agent can read a form, look up a record in one tool, write to another and post to Slack. You see the whole workflow on one canvas. If you already run n8n, adding an AI Agent node is a small step.

The cost is ownership. You choose the model, wire each tool, add review to the right tools and keep the credentials current. That's fine for a builder, and it's a lot to hand to a sales manager.

What changes when the agent lives in the CRM

An agent inside SalesCrew already knows your pipeline. Switch on the Inbox agent and it sweeps new threads every 15 minutes, drafting replies that wait in review. You wire nothing, and you keep one copy of your contacts.

The controls come with it. Research, tagging and scoring run on auto by default, while any email, LinkedIn message or marketplace proposal waits for a person. Stage changes, merges and deletes also wait in the queue, and anything that spends money stays human only.

You can still use n8n. Point a workflow at SalesCrew's outbound webhooks. Or give an n8n AI Agent a scoped MCP token, and it calls the same tools your team uses. Read the n8n integration and MCP vs Zapier for how that connection works.

Start every new agent in review

Whichever tool you build in, keep external sends behind a person until you've read a week of drafts. Our post on why agents should start in review mode sets out the checklist.

n8n AI agent questions

What is the n8n AI Agent node?
The n8n AI Agent node builds an agent inside a workflow. You connect a chat model and at least one tool, and the agent decides which tools to call. Since n8n 1.82.0 every AI Agent node works as a Tools Agent. The MCP Client Tool node lets it call tools on an outside MCP server (docs.n8n.io, checked 24 September 2026).
Can an n8n agent wait for a person before it acts?
Yes. n8n's human-in-the-loop setting pauses the workflow before a chosen tool runs and sends an approval request to Slack, Telegram or n8n Chat. The reviewer approves or denies, and a denied call is cancelled. You pick which tools need review, per agent (docs.n8n.io, checked 24 September 2026).
Can n8n connect to SalesCrew?
Yes, through outbound webhooks, the API and the SalesCrew MCP server. An n8n workflow can react to a SalesCrew webhook. An n8n AI Agent can also call SalesCrew's 140+ MCP tools through the MCP Client Tool node with a scoped token. External sends still land in SalesCrew's approval queue by default. SalesCrew is our product.
Where do agents inside SalesCrew keep their log?
Every tool call is written to SalesCrew's audit log with the actor: a user, a token or an agent. Each agent's runs and cost show on the Agents page, and the approval queue shows the evidence behind each item. You read one history instead of joining workflow logs to CRM records.
What does it cost to run agents inside SalesCrew?
SalesCrew Core costs $299 a month with unlimited seats, and the Agents pack adds in-product agents for $199 a month. The Agency plan ($1,200 a month) includes all agents. Each tier carries an AI allowance with a soft alert at 80% and a hard stop at 100% for AI only.