Alerts and emails
Ping a Slack channel when a lead fills in a form, or email a summary when a report finishes.
n8n workflows and templates you can import today
n8n connects your apps with visual workflows: a form comes in, a row gets added to a sheet, someone gets a Slack message. Every n8n template on ZigsFlow is a JSON file you import, connect to your own accounts and switch on. Here's how.
⏱ Setup time10–20 minutes
🎯 DifficultyBeginner to intermediate
💰 CostFree self-hosted, paid on n8n Cloud
🧰 You needAn n8n instance
What n8n workflows are good for
If the job involves two or more apps and happens more than once a week, it's a candidate.
Data between apps
Copy new orders into Google Sheets, sync contacts to your CRM, or tidy records before they're stored.
Anything with an API
The HTTP Request node talks to almost any service, even ones without a built-in n8n node.
AI agent workflows
Send text to an AI model, have it classify or summarise, then route the result to the right place.
How to import and run an n8n workflow template
Seven steps from download to a workflow that runs by itself.
- 01
Choose a workflow
Open a template in the library and check which apps it connects, what triggers it, and which credentials you'll need.
- 02
Download the JSON file
Save the workflow file and keep an untouched copy, so you can start again if an edit goes wrong.
- 03
Open your n8n editor
Log in to n8n Cloud or your self-hosted n8n with an account that's allowed to create workflows.
- 04
Import the workflow
Create a new workflow and use Import from File in the editor menu. You can also copy the JSON and paste it straight onto the canvas.
- 05
Connect your credentials
Exported workflows never include anyone's passwords or API keys. Open each node marked with a warning and pick or create your own credentials, then swap sample values like sheet IDs and email addresses for yours.
- 06
Test it node by node
Run a test execution and click through each node's output. Make sure nothing sends real messages or edits live data before you're ready.
- 07
Save and switch it on
Save the workflow and turn it on with the toggle in the editor. From then on it runs whenever its trigger fires.
Read before you run: a workflow can call external URLs, run code nodes and change data in your apps. Look at every node before you connect real accounts.
How an n8n workflow is put together
Almost every workflow follows the same four-part shape. Once you see it, templates are easy to read.
1. Trigger
What starts the run: a schedule, a webhook, a new row, a new email. Use the Manual Trigger while you test.
2. Shape the data
Nodes like Edit Fields, IF and Code filter, rename and reshape the data for the next step.
3. Act in an app
An app node uses your credentials to do the real work: add the row, send the message, create the task.
4. Check the result
Look at the execution log, and add an error workflow so you hear about failures instead of finding them a week later.
n8n nodes you'll see in most templates
Names can vary slightly between n8n versions.
| Node | What it does | Example |
|---|---|---|
| Schedule / Webhook trigger | Starts the workflow | Every weekday at 9am, or when a form posts data |
| HTTP Request | Calls an API | Fetch data from a service with no built-in node |
| Edit Fields | Adds, renames or removes fields | Turn "email_address" into "email" for the next app |
| IF | Splits the flow on a condition | Only continue if the deal value is over $1,000 |
| Code | Runs your own JavaScript or Python | Clean up text before it's stored |
When an imported workflow doesn't work
The execution log usually points straight at the problem.
| Problem | What to check |
|---|---|
| "Could not import" or invalid JSON | Download the file again and make sure you copied all of it. Very old n8n versions may not read newer exports. |
| Credentials missing | Expected after any import. Add your own credentials to every node that shows a warning. |
| 401 or 403 from an API | The key is wrong, expired or missing a permission the endpoint needs. |
| The workflow never starts | Check it's switched on, the trigger is set up, and (for webhooks) that you're using the production URL, not the test one. |
| Odd or empty output | Open the node before it and compare field names. A renamed column breaks expressions quietly. |
| Fails on large data | Turn on pagination, process items in batches and watch the API's rate limits. |
n8n workflows FAQ
The short answers before you import your first template.
What is an n8n workflow?
It's a chain of connected nodes that automates a task. One node starts the run, the next ones change the data or call apps, and the whole thing runs without you once it's switched on.
Are these n8n templates free?
The templates are free to download. Running them depends on your setup: n8n's self-hosted Community Edition costs nothing, n8n Cloud is a paid plan, and some connected apps charge for their own API.
How do I import an n8n workflow from a JSON file?
Open a new workflow in the n8n editor and choose Import from File, or copy the JSON and paste it onto the canvas. Then add your credentials and test it before switching it on.
Do I need to know how to code to use n8n?
No. Most workflows are built by connecting nodes visually. A few use a Code node or expressions, and those templates say so up front.
Why is my imported workflow asking for credentials?
Because exported workflows never carry anyone's passwords or keys. You connect your own accounts to each node after importing.
Is it safe to import workflows from the internet?
Only after you've looked at every node. Check where data is sent, what code nodes do and which accounts are touched, then test with sample data first.
Find an n8n workflow for your next automation
Browse the n8n templates in the library, or send us the workflow you wish existed and we'll look at building it.