No-code AutomationWhat is an automation workflow?
A workflow is a set of steps (nodes) joined together so that a process runs by itself.
Read on 14 November 2026. Products change quickly: check the sources.
The idea
The n8n documentation says that a workflow is a collection of nodes connected together to automate a process. You can create one from scratch or start from a workflow template, and once it is running you can share it. The same page lists the parts of working with workflows: creating and running them, saving and publishing them (including naming versions), storing credentials, using the building blocks (nodes and connections) and understanding executions, meaning the record of each run.
Triggers and actions
When you add a node, n8n lists its available operations, and there are two kinds:
| Kind | What it does |
|---|---|
| Trigger | Starts a workflow in response to an event or condition in a service. Trigger operations have a bolt icon when you search for a node |
| Action | A specific task inside the workflow: manipulate data, do something in an external system, or cause an event in another system |
Core nodes can be actions or triggers. Most nodes connect to one external service; core nodes give general functions such as logic, scheduling or generic API calls. Cluster nodes are groups of nodes that work together: a root node plus sub-nodes. The documentation also has app nodes, one set per service, and a list of trigger nodes that includes services such as Gmail, Google Sheets, Slack and Telegram.
How to think about a first automation
- Choose one event that should start it (a form arrives, a time is reached, an email comes in).
- List what should happen in order.
- Decide what happens when it fails (see the page on errors).
- Test with sample data before you publish it.
Do I need to write code?
n8n's own table lists a Code node for full JavaScript or Python, but also expressions, the visual data nodes and, on Cloud only, an AI Transform node. See the page on expressions and data.
Is this the same as a script?
It does the same kind of job. The difference is that you build it from visible steps, and each run is recorded as an execution.
Sources
- n8n docs: Workflows (docs.n8n.io/workflows/)
- n8n docs: Node types (docs.n8n.io/integrations/builtin/node-types/)
Read on 14 November 2026.
This is an independent guide. It is not connected with n8n. Products change quickly: statements were read on 14 November 2026 from the n8n documentation pages named under Sources, and limits, defaults and version numbers may have changed since. We do not give prices or compare products.