Which AI agent actions should need human approval?

Anything that leaves your system or can't be undone: emails, messages, proposals, deletes, merges and spend. Research, tagging, logging and summaries can usually run on their own. SalesCrew's default policy follows that split, with every external send held for review and any spend kept human-only.

Can n8n pause an AI agent until someone approves a tool call?

Yes. n8n's human-in-the-loop feature pauses the workflow when an AI Agent node reaches a tool with human review switched on, per n8n's docs in September 2026. The request goes to a channel such as Slack, Microsoft Teams, Telegram, Gmail or n8n Chat. Approve runs the tool with the AI's input; deny cancels it and tells the agent.

Does ChatGPT ask before a connector writes data?

Yes, by default. OpenAI's developer mode guide says write actions require confirmation, and you can remember an approve or deny choice for a given tool within one conversation, checked September 2026.

How do I stop every agent at once?

Use a kill switch that sits outside the agents themselves. In SalesCrew, one control on the Agents page stops every agent, and its MCP twin, agent_set_mode, does the same from any AI client. Manual work in the CRM carries on as normal.

How do you approve an AI agent's tool calls first?

Sort each tool by risk, hold the risky ones in a queue a person clears, and log every call either way.

app.salescrew.io/inbox

The unified reply inbox with classified threads

The short answer

You approve an AI agent's tool calls by putting a review step between the agent's decision and the action, for the tools that send, delete or spend.
n8n pauses an AI Agent workflow on any tool with human review switched on and waits for Approve or Deny in Slack, Teams, Telegram, Gmail or n8n Chat, per n8n's docs in September 2026.
ChatGPT asks for confirmation before a connector's write action by default, one tool call at a time.
SalesCrew holds every external send an agent attempts in one approval queue, lets low-risk actions run, and writes every tool call to the audit log.

Sort your tools by what they can break

Approving every call sounds safe, but your reviewers will stop reading after the twentieth tag change. Approving nothing is how an agent emails the wrong list. So start by sorting your tools into risk classes.

Reads, tags, notes and summaries can usually run straight through. Anything a customer sees goes to a person first: emails, LinkedIn messages, proposals. Stage changes, merges and deletes go to review too, because they're hard to undo. Spend stays with a human, full stop.

Where each tool puts the approval step

Read on each vendor's own documentation.

Tool	Where the approval happens	What a reviewer can do	Source
n8n AI Agent	Human review step on selected tools; request sent to Slack, Teams, Telegram, Gmail, Discord, WhatsApp or n8n Chat	Approve (runs with the AI's input) or Deny (cancels; the agent is told)	docs.n8n.io, Human-in-the-loop for tools
ChatGPT connectors	Confirmation prompt in the chat before a write action	Approve or deny; remember the choice per tool for one conversation	developers.openai.com, developer mode guide
SalesCrew (our product)	One approval queue for every agent, grouped by agent	Approve, edit then approve, or reject with a reason that feeds the next run	Disclosure: SalesCrew is our product.

Checked on docs.n8n.io and developers.openai.com, September 2026.

Put the queue where the data lives

A review step inside one workflow tool only guards that workflow. If a second agent, or a teammate's ChatGPT, calls your CRM directly, it skips the check. The safer place for the queue is the system that owns the records.

That's how SalesCrew works. Each agent runs in one of four modes: off, draft, review or auto. Auto falls back to review below a confidence threshold. Every item in the queue shows the draft, the evidence behind it, the confidence and the cost. Read the full setup on the agent approval workflow page.

The same queue answers to any AI client, because every action in SalesCrew is also an MCP tool. Claude, ChatGPT or Cursor can list, approve and reject items through approval_list, approval_approve and approval_reject. Guardrails still apply at send time: at least 3 days between touches per contact, daily caps per mailbox and domain, and suppression checked again before anything leaves.

Log the calls that run without review too

Most teams watch the queue and forget the auto lane. Write every tool call to an audit log with the actor behind it, whether a user, a token or an agent. When something goes wrong, the log is how you find out which call did it.

Questions

Which AI agent actions should need human approval?: Anything that leaves your system or can't be undone: emails, messages, proposals, deletes, merges and spend. Research, tagging, logging and summaries can usually run on their own. SalesCrew's default policy follows that split, with every external send held for review and any spend kept human-only.
Can n8n pause an AI agent until someone approves a tool call?: Yes. n8n's human-in-the-loop feature pauses the workflow when an AI Agent node reaches a tool with human review switched on, per n8n's docs in September 2026. The request goes to a channel such as Slack, Microsoft Teams, Telegram, Gmail or n8n Chat. Approve runs the tool with the AI's input; deny cancels it and tells the agent.
Does ChatGPT ask before a connector writes data?: Yes, by default. OpenAI's developer mode guide says write actions require confirmation, and you can remember an approve or deny choice for a given tool within one conversation, checked September 2026.
How do I stop every agent at once?: Use a kill switch that sits outside the agents themselves. In SalesCrew, one control on the Agents page stops every agent, and its MCP twin, agent_set_mode, does the same from any AI client. Manual work in the CRM carries on as normal.