n8n · workflow automation platform

n8n

Official documentation

n8n combines explicit workflow logic with model-driven steps, so a repeatable process can reserve AI for the part that needs interpretation. It is available as managed Cloud and self-hosted software under fair-code terms that need checking for the intended use. Workflows can connect model providers, tools, memory and MCP servers. For a small trial, begin with a manual trigger and synthetic ticket, validate the model's structured result and return a routing suggestion. Human review can guard selected AI tools and show their proposed parameters before approval or denial. Configure that step rather than relying on an instruction to ask first. Hosting, credentials, updates, backups and execution retention remain responsibilities to assign before making the workflow recurring.

Product profileDocumentation checked

AutomationAgents

In this profile

When it fits

Useful for

  • Combining repeatable process logic with a bounded AI interpretation step
  • Choosing between managed hosting and an operated self-hosted workflow installation

Limits to consider

  • Assuming self-hosting prevents configured provider nodes from transmitting data
  • Using a prompt alone as the approval gate for consequential tool calls

Capabilities and platforms

  • Combines model providers, tools, memory and MCP connections in workflows
  • Mixes explicit flow logic with AI interpretation rather than delegating every step
  • Human review can gate selected tools with proposed parameters visible before a decision

Where it runs

  • Managed Cloud
  • Self-hosted software

Access and setup

Cloud account or operated self-host installation, plus separately authorized provider and app credentials. Fair-code license terms apply; provider access is distinct from n8n hosting.

Current access and pricing
  1. Choose n8n Cloud or an officially documented self-host installation and assign hosting and maintenance ownership.
  2. Create a manual-trigger workflow with synthetic input and only the provider credentials it needs.
  3. Validate the structured result and configure actual human review for any consequential tool; test errors, retries and duplicate inputs before event triggers.

Proposed exercise · not hands-on tested

Draft a support-ticket route

Input

Synthetic support tickets and an explicit list of permitted team labels.

  1. Use a manual trigger to send one ticket to a configured classification step.
  2. Validate the returned label against the permitted list and retain an unknown or error path.
  3. Return an internal routing suggestion for review; repeat a ticket to inspect duplicate behavior before adding a live trigger.

Artifact to inspect

A draft routing suggestion and visible validation/error results.

What to verify

Check that invalid labels cannot become routes and that retries or duplicate inputs do not send unintended actions.

Data handling and permissions

Self-hosted n8n can still transmit workflow data to whichever provider a node calls. Trace the actual authored workflow rather than applying the separate n8n assistant privacy statement to it. The privacy documentation describes assistant workflow-context handling, default telemetry and self-host deletion responsibilities, but those do not establish that an arbitrary AI workflow keeps its input local. Review provider terms, connected credentials, execution storage and retention together. In a self-hosted installation, assign updates, backups and deletion ownership as operational tasks. Use synthetic tickets for the proposed exercise and keep the model's returned text from silently acquiring authority to perform a consequential action.

Other options

Make AI Agent (New)
Compare for cloud scenario building with agent steps.
Zapier Agents / AI by Zapier
Compare for connected-app work within the Zap editor.

Sources and scope

Documentation-based product profile; no hands-on testing. The proposed workflow is an authored exercise, not a verified outcome or a practical guide. Capabilities and policy statements describe vendor documentation checked October 2, 2026; task-fit comparisons are editorial judgments. Plan, region, administrator and interface limits may apply.

Source review: . Product access and terms can change.

Suggest a correction