Can AI answer engines cite your site?
Outreach scripts that get replies
Find the 3 workflows costing you sleep
200+ prompts, ready to ship
12-month posting plan in 60 sec
Brand voice doc in 4 steps
Runway / Pika / Sora / Veo formats
n8n is the open-source automation platform that connects your apps into visual workflows — a webhook fires, a form gets submitted, a payment lands, and n8n runs the next steps for you without a human in the loop. This generator skips the blank canvas: pick what triggers the automation and what should happen next, and you get a real, importable workflow JSON.
Every recipe below is based on real automation patterns I've built and refined through client work — lead capture, inbox triage, billing, e-commerce follow-up. Import is one click in n8n: Workflows → Import from File, or paste the JSON straight in. Credentials are never included; you connect your own on import.
Webhook, Gmail, Stripe, Typeform, Google Sheets, Calendly, and more.
Slack, GoHighLevel, HubSpot, email, SMS — whatever should happen next.
Import straight into n8n. Placeholder credentials only, never real keys.
All 12 recipes in the library
When it's actually worth automating
If a task follows the same trigger and the same steps every single time — a form comes in, you copy it into your CRM, you Slack the team — that's an n8n workflow, not a job. The templates above are the dozen versions of that pattern I get asked to build most often.
What n8n workflows are good for: moving data between tools the instant an event happens, running the same multi-step sequence without someone remembering to do it, and gluing together apps that don't natively talk to each other. What they're not good for: decisions that need real judgment call by call — that's where you keep a human in the loop or add an AI classification step like the Gmail recipe above.
Importing is the easy part. Open your n8n instance, go to Workflows in the left nav, click Import from File (or use the three-dot menu → Import from JSON if you'd rather paste), and the trigger + action nodes land on the canvas ready to connect your credentials.
Waseem, building from Bali · info@skynetjoe.com
Quick answers
Yes. Every template is a real n8n workflow object — nodes with real n8n-nodes-base type identifiers, typeVersion, parameters, and a connections graph chaining trigger to action. Open n8n, go to Workflows → Import from File (or paste it via the three-dot menu → Import from JSON), and the nodes drop straight onto the canvas.
No, and they never will. Nodes that need auth (Slack, Gmail, HubSpot, Stripe, Twilio, generic HTTP calls) carry a placeholder credential name only. On import, n8n prompts you to connect your own credential to each node — nothing here is a working secret.
The generator matches the closest available recipe for your trigger app and flags it with a 'closest match' note instead of failing. You still get a valid, importable JSON — just double-check the action nodes match what you actually want before you connect credentials.
The wizard, the recipe preview, and the full JSON preview are all free to browse with no gate. The email unlock only sits in front of the actual file download, so I know who's using the tool and can follow up if you want a custom build.
These 12 recipes cover the automations I get asked for most. If yours is more custom — multi-branch logic, a real AI agent, a legacy system with no API — that's a build, not a download.
Book a discovery call