n8n Agents

A first-class n8n Agent is a saved resource with its own instructions, model, tools, skills, sub-agents, memory, channels, scheduled tasks, versions, and spend limits. It is configured as JSON through the Agent MCP tools, never with Workflow SDK code. The AI Agent node inside a workflow is a different thing, covered by n8n-ai-nodes-official.

Agents are generally available. The UI shows a Preview tag because they change often and some features you might expect aren't there yet. They aren't ready for Enterprise yet: an Enterprise instance may have them enabled, but don't assume it. If create_agent isn't in your tool list, Agents aren't enabled on this instance. Say so and offer a workflow instead of guessing.

Non-negotiables

1. Always send a memory block when creating over MCP: "memory": { "enabled": true, "storage": "n8n" }. The UI adds it on every save. create_agent saves exactly what you send, and without it the Agent forgets the previous turn even inside one session (verified live).
2. Never publish without the user's explicit OK. A built Agent is a draft. Configuring a channel on an already published Agent connects it immediately, so confirm that too.
3. Publish what the Agent calls. Workflow tools need a When Executed by Another Workflow trigger, the same project, and a published workflow (validate_agent reports it). Saved sub-agents must be published too, and nothing checks that: validation and publishing pass, then production delegation fails and the parent quietly answers on its own.
4. Approval on anything that sends, changes, deletes, or spends, and know what the approver will see. See references/APPROVALS.md.
5. One mutate_agent per change, always with the latest configHash. A stale hash returns stale_config: call get_agent and retry.

Agent, workflow, or AI Agent node?

Decide before calling any build tool. The first question is the "say it out loud" test.