n8n helps you build automations from clear steps and add AI for classification, information extraction, or choosing an action. Workflows can run in n8n Cloud or on your own infrastructure.
AI within a visible workflow
In n8n, an event passes through connected nodes: data retrieval, transformation, a condition, a model call, and an action in another system. You can give an agent tools and memory while retaining ordinary, predictable steps around it. This helps when you need to see both the final response and why a record changed.
The platform is especially suitable for a technical user who is ready to understand the data structure and integration errors. The visual editor reduces the amount of manual code, but does not eliminate the need to understand identifiers, access rights and re-run behavior. One incorrectly selected array element can change the wrong record.
Example: triage requests without messaging customers
Use test requests and three predefined categories. The model should choose a category, briefly explain its choice, and flag missing information. The next node validates the value and saves the record to a demonstration table. Do not connect outbound messaging during the exercise.
Test ambiguous text, an empty message, and the same event twice. Uncertain cases need a separate branch, while repeats need duplicate prevention. If a model returns a polished explanation with an invalid category, automation must stop the write or route it for review instead of guessing the right value.
Cloud or your own AI infrastructure
The official Community edition is available for self-hosting under n8n’s terms. This is not an unconditional license for any resale or embedding: check your intended use against the license. Cloud and enterprise plans provide different organizational capabilities and support.
An official starter kit with n8n, Ollama, and supporting components is available for a local AI workflow. It is intended for exploration and prototyping and requires further work before production. Self-hosted n8n still sends context to a cloud model when one is used. A fully local setup requires checking the model, storage, tools, and every network component.
API, billing, and maintenance
n8n provides its own API for programmatic management of platform resources. This is distinct from an HTTP node calling another provider’s API and from an agent’s MCP tools. Check available operations and key permissions against your edition and configuration.
Cloud billing focuses on workflow executions; AI resources and external models have their own terms. The free Community edition does not cover servers, backups, or tokens. After launch, monitor error logs, connection recovery, and unfinished executions. Automation is useful when it can be safely repeated and changes to every important field can be explained.
Keep a reference input and expected record beside the workflow description. Rerun this example after updating a node or changing models. This helps detect field-name changes before they affect production data.
Suitable tasks
- Classify requests with result checks
- Link the model to tables and work systems
- Build your own local AI prototype
- Manage processes through API
Strengths
- A visible workflow combining AI with standard logic
- Community for self-hosting
- The product’s own API and official local AI starter kit
Limitations
- Self-hosting requires maintenance and license verification
- Local server does not make the external model local
- Error handling and duplicate prevention are required
Selection and conditions
- Free access
- Yes
- Trial period
- Yes
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Yes
- API
- Yes
“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.
- Input formats
- Text, Data
- Result
- Text, Data
Terms
Free refers to the licensed Community edition; local AI is possible with local Ollama and verified workflow nodes. The Starter kit is intended for prototyping. Cloud trial resources, infrastructure, and external inference are accounted for separately.From task to first result
Practical example
- Task
- Classify requests with result checks
- What to prepare
- A demonstration form request: “I can’t sign in after changing my email.” Three request categories and a test table without personal data are available.
Task brief or prompt
Set up a practice request-handling workflow: read the text, choose an allowed category, and prepare a short description for an employee. If information is insufficient, use “Needs review.” Write the result only to the test table. Do not message the customer or modify their account.
Expected result
A verifiable record in a test table and a log of completed steps; this is an automation setup task, rather than a demonstrated run result.
How to check the result
- Check that the category matches the original request and no data was invented.
- Repeat the same event: the workflow must not create a duplicate or trigger outbound sending.
An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.
Check details
Official sources
- n8n: the official workflow and agent platform
- n8n: Cloud, self-hosted and trial
- n8n: Models, Agents, Tools and Memory
- n8n: the platform’s own API
- n8n: self-hosting and Community
- n8n: the local AI starter kit and prototype limitations
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.
