Build a working automation from scratch — from picking a trigger through connecting nodes to activating and testing your n8n workflow. This guide takes UK users from empty canvas to live, automatically-running workflow in under half an hour.
What a workflow is in n8n • How to create a new workflow step by step • Testing and debugging workflows • Managing and organising workflows • Common first-workflow patterns for UK businesses • FAQ
A workflow in n8n is a set of interconnected nodes that together carry out a specific automation task. Think of it as a visual recipe: each step is a node, and the arrows between them show the order and direction data flows in.
A workflow can be simple — “when an email arrives with the subject ORDER, send an SMS” — or highly complex, with dozens of steps, conditions, loops and branches.
Every n8n workflow begins with a trigger node. The trigger decides when the workflow runs. It can respond to an external event (an HTTP request, a new email, a new row in a sheet) or operate on a schedule (every hour, daily at 09:00, the first of each month).
Once triggered, data flows through the action nodes — each one does something with the data: fetches additional information, transforms it, filters, sends, stores.
Key advantage: you see the data at every step. Click any node after a test run and you see exactly what went in and what came out. That dramatically simplifies building and fixing flows compared with writing scripts.
Let’s walk through building a simple but working workflow: every time you call a specific URL (webhook), n8n sends you a confirmation email. It’s an ideal starting point — you learn how triggers and actions connect.
In the sidebar menu, click Workflows, then + New Workflow in the top-right corner. You land on an empty canvas with the message “Add first step”.
Name the workflow by clicking the default “My workflow” at the top and typing your own, for example “Email notification on webhook call”.
Click the + button (or click in the middle of the canvas) to open the node panel. In the search field, type “Webhook” and select the matching node. It appears on the canvas as the first block.
Click on the webhook node to open its settings. Set the HTTP method to POST and note the generated Test URL — you’ll need it shortly. Click Listen for test event so the webhook starts listening.
Click the + on the right of the Webhook node (on its outgoing arrow) to add the next node. In the search field, type “Gmail” or “Send Email” and pick the appropriate node.
First time using Gmail, n8n asks you to set up credentials — click Create New Credential and follow the OAuth2 instructions. Google prompts you to sign in and authorise n8n to send emails on your behalf.
In the node settings, fill in:
Make sure the arrow from the Webhook node connects to the Gmail node.
Send a test request to the webhook URL (use Postman, curl, or a browser plugin). n8n detects the request, data flows through to the Gmail node, and an email is sent.
Example curl command:
curl -X POST https://yourinstance.n8n.smartxhosting.uk/webhook-test/abc123 \
-H "Content-Type: application/json" \
-d '{"name":"Test","email":"[email protected]"}'Check the target mailbox — if the email arrived, the workflow works.
Click the Inactive toggle in the top-right to switch it to Active. From this point, the workflow runs automatically every time the webhook URL receives a request. The Test URL becomes the Production URL after activation — use the production URL in real integrations.
n8n offers several built-in tools for testing and diagnosing problems. Use them regularly, especially when building new automations.
The simplest way to test. Click the Execute Workflow button in the bottom-left of the canvas. If your workflow starts with a webhook or external event, n8n can run it with sample data — or wait for the real event to arrive (“Listen for test event”).
Available after any test run. Click a node on the canvas — a panel appears on the right with input data (INPUT) and output data (OUTPUT). You see exactly what data went in and what came out. This is where you debug what’s happening at each step.
In the sidebar, the Executions section holds the full list of runs for every workflow. Errors are flagged red. Click any execution to see every node’s state during that specific run, including error messages and the data that caused them.
During development, you can pin the data output from a node, so test runs use that fixed data rather than re-fetching from the external service. Useful when the trigger is hard to fire on demand (a particular Gmail message, a specific webhook payload).
As you build more automations, organising your library becomes important. n8n offers several mechanisms worth learning early.
First step to order. Give workflows descriptive names like “Slack notification — new WooCommerce order” instead of “Workflow 5”. You can also add a description in the workflow settings that explains what it does, when, and why.
Let you group workflows by topic or project. Open a workflow and click Add Tags in the settings panel. Create your own tags such as “Sales”, “Reporting”, “Gmail”, “Customers”. Filter the workflows list by tag — particularly useful once you have ten or more workflows.
Use the Active/Inactive toggle on the workflow list or directly on the canvas editor. An inactive workflow does not respond to events and does not run on schedule — it’s frozen. Deactivate when you want to pause automation temporarily without deleting it (maintenance work, seasonal business breaks, troubleshooting a related workflow).
n8n workflows export to JSON. Use Download in the workflow menu to save a JSON file. Commit these to git for version control — especially useful for team environments where you want to review workflow changes like code.
Three patterns new UK users often build as their first workflow:
All three start with simple building blocks and scale to include conditions, branches and additional integrations as your needs grow.
n8n hosting ready for your first workflow
SmartXHosting n8n runs in a pre-configured Docker container on UK infrastructure — sign in and start building. UK-based support if you need help with advanced workflows or credentials.
Launch your n8n instanceQ: My workflow isn’t firing — what should I check?
A: Three things in order: (1) the workflow is set to Active; (2) the trigger is the correct type (Webhook for HTTP calls, Schedule for time-based); (3) credentials for any connected services (Gmail, Slack) are valid. Check the Executions page for recent errors.
Q: What’s the difference between Test URL and Production URL on a webhook?
A: Test URL is used during development with “Listen for test event” — the workflow stays active only for one test run. Production URL works whenever the workflow is Active and fires for every incoming request.
Q: Can I have more than one trigger per workflow?
A: Yes. A workflow can have multiple triggers running in parallel. Each trigger starts its own execution of the downstream actions.
Q: How do I stop a runaway workflow?
A: Deactivate it immediately via the Active/Inactive toggle. Check the Executions page for what’s been running. For long-running executions, n8n supports cancel via the execution detail page.
Q: Can workflows call other workflows?
A: Yes — use the Execute Workflow node to call another workflow from within a parent. Useful for reusable sub-automations like “send standard welcome email”.
Q: What if my workflow takes too long?
A: n8n has per-execution timeouts. On SmartXHosting hosting, standard timeouts cover typical workflows. For long-running tasks (large file processing, slow API), architect with batching or schedule the work as background jobs.
Q: How do I version-control workflows?
A: Export to JSON and commit to git. Some UK teams use a convention where each workflow has a matching JSON in a git repository — changes get reviewed as PRs before re-importing to n8n.
Q: Can I share a workflow with another user?
A: Yes. Export the JSON, send to them, they import into their own n8n. For teams, multi-user n8n on the same instance allows shared workflows with role-based permissions.