WHAT IT TESTS
A small deterministic harness for the paths that usually fail later.
The workflow starts manually and creates only local synthetic data. It checks a ready item, a repeated item, a retryable failure, an exhausted retry, and invalid input. The final node throws unless the expected distribution and every zero-action boundary still hold.
- 01Seed
Create five deterministic fixtures with no customer or personal data.
- 02Validate
Check required fields and classify an in-run duplicate before any action is planned.
- 03Route
Separate ready, duplicate, bounded retry, and accountable review outcomes.
- 04Fail closed
Throw if seven count and safety invariants do not match the expected result.
IMPORT AND RUN
Use a test instance. Read the notes before extending it.
- 01Download
Save the static workflow JSON from this page. No form, account, email, or tracking request is involved.
- 02Inspect
Review the four Sticky Notes and five functional nodes, then import the file into an authorized non-production n8n environment.
- 03Execute
Run the Manual Trigger. No credential setup is required because the workflow contains no external node.
- 04Verify
Confirm the final node reports five fixtures, seven assertions, and zero duplicate effects, side effects, and external actions.
n8n documents workflow JSON import in its official import and export guide. The published file was imported and executed locally in n8n 2.26.8 before release.
EXPECTED RESULT
One ready, one duplicate, one retry, and two review items.
- Fixture count
5 - Outcome counts
ready: 1,duplicate: 1,retry: 1,review: 2 - Assertion count
7 - Safety result
duplicate_effects: 0,side_effects_executed: 0,external_actions: 0 - Execution capability
none. The harness can classify and plan, but it cannot change an outside system.
HONEST LIMITS
This is a test harness, not a production workflow.
This self-directed resource is not client work, an official n8n template, an n8n partnership claim, a security assessment, or proof of production readiness. Its duplicate set exists only during one execution. A real workflow still needs client-owned authority, credentials, durable state, concurrency controls, retry limits, observability, rollback, and acceptance tests before external actions are enabled.