n8n
Build a three-step automation that moves harmless test data and shows every result.
- Suitable for
- People who repeat a clear information-moving task and can describe its input and output.
- Do not start here if
- Not for automating payments, account deletion, legal decisions, or confidential customer data in a first trial.
- Visible result
- A manual trigger passes sample text through one transformation and writes a visible result.
- Time
- 60 min
- Device
- A modern browser; self-hosting has additional computer requirements
- Account
- Cloud and self-hosted paths have different account requirements
- Cost
- Plan, hosting, and connected services can each add cost
- Data
- Invented sample data only for the first workflow
- HAACC check
- Editorially reviewed
Not run by HAACC
Before you start
A modern browser; self-hosting has additional computer requirements
Cloud and self-hosted paths have different account requirements
Plan, hosting, and connected services can each add cost
Invented sample data only for the first workflow
Ability to state one input, one transformation, and one output
The path
- 01
Write the workflow contract
In one sentence each, write the input, transformation, output, and what must never happen. Use invented data.
Continue only whenThe workflow can be explained without naming any n8n node. - 02
Choose cloud or local deliberately
Compare the current official cloud and self-hosted paths for account, cost, storage, updates, and removal. Pick one; do not mix instructions.
Continue only whenYou can say who stores the workflow and test data. - 03
Build only three nodes
Use a manual trigger, one simple text transformation, and one visible output. Do not connect email, payment, customer, or production accounts.
Continue only whenEach node shows the expected sample data before the next node runs. - 04
Test one failure
Send an empty or malformed sample input. Confirm the workflow stops visibly instead of inventing or silently dropping data.
Continue only whenThe failed run is visible and does not trigger any external action.
A three-node workflow succeeds with valid sample data and fails visibly with invalid sample data.
Evidence boundary
HAACC reviewed the public source and shaped this path, but did not run the project on a clean machine. Treat every install step as unverified.
What HAACC checked
- Repository identity, snapshot metrics, and the visual workflow concept
- A bounded first workflow that contains no production credentials
What remains unchecked
- Cloud or self-hosted installation, billing, credential storage, upgrades, and deletion
- Repository license was not asserted by the captured GitHub license field
Stop and read
Automation can create irreversible actions
Do not connect payments, deletion, publishing, or customer systems until dry-run, approval, retry, and rollback behavior are reviewed.
Open repository does not settle every usage right
Check the current project license and plan terms for your intended hosting and commercial use.
When something fails
A node requests a real service credential
Remove that node from the first trial. Replace it with manual input or a local visible output.
The workflow runs but the output is unclear
Stop adding nodes. Inspect each node's input and output until the first mismatch is found.
Delete test credentials, workflow history, and the trial workflow. For self-hosting, stop and remove the dedicated service and volume using current official instructions.
Turn it into your project
Personal reading digest
Transform manually pasted links into a private weekly checklist before adding any external account.
Project idea intake
Turn a simple form into a structured local review queue with explicit failure states.
Source snapshot
- Repository
- n8n-io/n8n
- Captured
- 2026-07-20
- Stars at capture
- 197,052
- Forks at capture
- 59,468
- GitHub license field
- NOASSERTION
- Pinned revision
- Not pinned