n8n Studio

Describe the automation — get an importable n8n workflow, the setup steps, and a test plan.

Back to SkillSafe
Revise an existing workflow (optional) — paste its JSON, get a free lint instantly
Or pick the file: read locally, nothing uploads until you run.
How it works

Nothing to hand? Load the — a schedule-triggered fetch, filter, sheet append and channel post — the , which validates an incoming lead and routes it robustly with an error workflow, or the , which takes an existing workflow with real lint findings and asks for a change.

1

Describe the automation

Trigger, steps, destinations — in plain English. The free scan reads it as you type and lists what it detected: the services named, the schedule or webhook phrasing, the step-shaped lines. Pin the trigger kind and the posture (lean happy-path, or robust with guards, retries and an error workflow) if you care; leave them on the defaults if you don't. Revising instead of starting fresh? Paste your existing workflow's JSON — the inspector lints it instantly, for free: missing trigger, orphan nodes, connections into nodes that don't exist, duplicate names, token-shaped secrets pasted inline.

2

The AI builds the workflow

A complete n8n workflow document: real node types with real parameters, one trigger matching what you chose, connections that all resolve, expressions in n8n's own {{ $json.field }} style, credentials referenced by placeholder — never an inline key — and a sticky note in the canvas summarizing what to configure. Every service, trigger hint and step the free scan detected is confirmed in the workflow or explicitly set aside, and the same linter that read your paste re-reads the generated JSON before it renders.

3

Import, configure, test

Download the .json and import it from n8n's Workflow menu. The node-by-node guide says what each node does and exactly what to set before first run; the setup steps walk the credentials; the test plan is executable — pin sample data, run single nodes, then activate. Assumptions and limits are stated honestly, so you know what was guessed and what the workflow deliberately does not handle. Past generations stay on your account with restore, and "Use as revision base" feeds the result back in, so the second run is a change request, not a rewrite.

Derived from the @n8n-io/n8n skill (n8n is fair-code, Sustainable Use License; this app generates standard n8n workflow documents and is not affiliated with n8n GmbH).