n8n
A workflow automation platform with cloud and self-hosted options for technical teams.
Where it fits
A workflow automation platform with cloud and self-hosted options for technical teams.
Price and access
Check the current plan before paying
A free option is available for trying real tasks. Paid plans or usage can add higher limits or extra features.
- Starter (billed annually)€20 / monthAs of 2026-09-05 · source ↗
- Pro (billed annually)€50 / monthAs of 2026-09-05 · source ↗
Prices are collected from the official site and can change. Always confirm the current plan, taxes and regional availability before paying.
What it helps with and what to check
Good tasks to start with
- Technical automations and AI workflows
- Teams needing a self-hosted option
Keep an eye on
- Self-hosting adds security and operations work
- Give each credential and webhook only the access it needs
How to start
Tick each step as you work. These checks stay on this page only; they do not verify results in the external tool.
0 of 5 steps checked
Start with a practice workflow
In an n8n workspace you are allowed to use, create an empty workflow named Practice — review a draft. You need access to an existing installation or a Cloud account; check the current terms before signing up. Use only fictional data. This exercise uses two nodes and needs no connected email, CRM or AI account.
Add a manual start
Add one Manual Trigger node. It starts the workflow when you choose Execute Workflow; it does not set a schedule. Keep this practice workflow separate from any live workflow. If you see existing nodes that send messages or update records, create a new empty workflow instead.
Create one fictional record
Connect an Edit Fields (Set) node after Manual Trigger. In Mode, choose JSON Output and enter this fixed JSON: {"task":"Review a weekly update","owner":"Practice user","status":"needs_review"} Keep the values fixed, not expressions. This is a record you wrote, not an AI result. If JSON is rejected, check the double quotes and commas before continuing.
Run once and inspect the output
Choose Execute Workflow and inspect the Edit Fields output. Confirm one item contains task = Review a weekly update, owner = Practice user and status = needs_review. Change only status to reviewed in the JSON, run again, and confirm the new output reflects that change. If there is no output, check the node connection; if the old value remains, confirm you reran the edited workflow. A green node alone is not the check.
Write the real workflow brief before connecting apps
Write five lines: what starts the workflow; the minimum input fields; the expected output; who approves changes; and what happens on failure or a duplicate run. Continue to the requirements Task below to turn those lines into a brief. This practice checks data setup and inspection only. Sending messages, changing live records and scheduling runs each need their own permission and test.
Platforms
Privacy and human checks
Before you upload
- Remove customer names, passwords, identifying details and company secrets.
- Read the provider’s current retention, training and workspace settings.
Before you use the result
- Verify facts, sources, calculations and code against the original material.
- Have a person review important content or actions before publishing, sending or running them.
Related tasks and guides
Prepare inputs or review results in these AhaDo workflows. Copy permitted material yourself when using an external tool.
Alternatives
A visual no-code platform for building multi-step automations and data flows.
View comparison option ZapierA no-code automation platform with AI workflow and agent features across many software services.
View comparison option Microsoft Power AutomateMicrosoft’s low-code platform for business workflows, desktop automation and approvals.
View comparison optionOfficial source and research status
Guide published · Practice workflow researched from official n8n Manual Trigger and Edit Fields documentation on 7 September 2026. The fictional record is authored; this is not a recorded provider-account run.
Listed means a published directory entry. Guide published means it also includes dedicated start steps and sourced prices. Neither status means real-user results have been verified.
- Official product source
- Open source ↗
- Last researched
- 2026-09-05
- Real-user evidence
- Not collected yet
Report a correction
Has a tool's information, price or signup changed? Tell us and help the next beginner.
