Building Your First Workflow with n8n: A Beginner's Guide

n8n first workflow Building your first workflow in n8n is as simple as selecting a trigger, adding action nodes, and running a test execution. This guide walks you through the entire process — from choosing Cloud or self-host to launching your first automation in production.

Before You Start: Cloud or Self-Host?

The fastest way to get started with n8n is to create an account on n8n Cloud; those who prefer self-hosting can be up and running with Docker in a few minutes. Which path you choose depends on your data privacy requirements and the capacity of your technical team.

If you have already explored what n8n is, it is time to move on to the practical step. The platform comes in two primary deployment models: n8n Cloud and self-hosted. With the Cloud option, you can start building workflows in your browser as soon as you create an account, without managing any infrastructure. The free trial plan covers all core features and allows you to test a production-ready scenario quickly.

In the self-hosted model, your data stays entirely on your own servers — a critical advantage for organisations in the financial and healthcare sectors. Our guide on installing n8n with Docker covers how to run it with a single command and how to configure environment variables in detail. Whichever path you choose, the interface and workflow logic are identical; the steps in this guide apply to both environments.

The Interface and Core Concepts

The n8n interface consists of the workflow canvas, node panel, and execution history. Nodes represent individual steps in the workflow; the trigger is the starting point; and connections carry data between nodes.

When you first open n8n, an empty canvas greets you. Clicking the 'Add First Step' button in the top left opens the node library. This library contains over 400 integrations; use the search box to find the application you need in seconds.

You can position a node by dragging it onto the canvas and create a connection by pulling from its output handle. Double-clicking a node opens its parameters in the right panel. The 'Executions' tab in the top menu shows a log of all past runs — this is the screen you will use most during debugging.

Your First Workflow: Step by Step

For your first workflow, the chain Schedule Trigger → HTTP Request → Gmail Send is the ideal starting point. This three-step structure simultaneously teaches scheduling, external API calls, and sending notifications.

Open a new workflow and click 'Add First Step' to open the trigger selection screen. Select the 'Schedule' trigger and configure it to run every day at 09:00; you can use the cron expression '0 9 * * *'. Once the trigger is configured, a small clock icon appears on it.

Adding the HTTP Request Node

Pull from the right output handle of the trigger to add an 'HTTP Request' node. In the URL field, enter 'https://jsonplaceholder.typicode.com/todos/1' as an example; select GET as the method. This address is a free test service that simulates a real API endpoint and requires no credentials.

Sending a Notification with the Gmail Node

Connect a 'Gmail' node to the output of the HTTP Request node. Select the 'Send Message' operation. Enter the recipient email address in the 'To' field. Type 'Daily API Report' in the Subject field. In the Body field, you will use the expression syntax covered in the next section to pull data from the HTTP response. For now, you can also enter static text.

1. Create a new workflow (the '+' or 'New Workflow' button at the top left).
2. Add a Schedule Trigger and configure its frequency.
3. Connect an HTTP Request node and enter the URL and method.
4. Connect the Gmail node and select your Gmail credentials.
5. Click the 'Test Workflow' button at the top right.
6. Wait for a green check mark to appear on each node.
7. Inspect the response data in the execution log.

Adding Credentials and Testing

In n8n, credentials are a centralised identity management system that stores API keys and OAuth tokens in encrypted form. Once a credential definition is created, it can be reused across all nodes of the same type.

While configuring the Gmail node, click the '+ Add' button next to the 'Credential for Gmail' field. On the screen that opens, use the 'Sign in with Google' option to initiate the OAuth flow. A Google account authorisation page opens in your browser; after granting permission, n8n automatically stores the token. This token is stored with AES-256 encryption and is never displayed in plain text.

After successfully adding credentials, they appear selected in the node parameters. Click the 'Test Workflow' button at the top right to perform an on-demand test run. After execution, each node shows a green tick for success or a red exclamation mark for failure. In case of an error, click the node to read the detailed error message and inspect the input/output data structure.

• You can also access the Credentials Settings screen from 'Settings > Credentials' in the left menu.
• The same credentials can be shared across multiple workflows; updating them updates all workflows.
• In team environments, credentials can be shared using role-based access control.
• n8n supports automatic refresh mechanisms for expired OAuth tokens.

Expressions and Data Flow

n8n expressions let you access JSON data from previous nodes using the {{ $json.fieldName }} syntax. This allows each node to dynamically consume the output of the previous step.

As you start typing in any text field of a node, a small '/' or '{{ }}' icon appears on the right. Clicking this icon opens the Expression Editor. In the editor, you can see all the data received by the current node in a tree structure and auto-complete field names by clicking them.

Suppose the HTTP Request node returns a JSON response structured like this: { "id": 1, "title": "Task title", "completed": false }. If you type '{{ $json.title }}' in the Subject field of the Gmail node, the email subject will automatically be set to 'Task title'. In a flow with multiple nodes, use the syntax '{{ $node["HTTP Request"].json.title }}' to access data from a specific previous node.

• {{ $json.fieldName }} — a field from the data entering the current node
• {{ $node["NodeName"].json.fieldName }} — a field from a specific node's output
• {{ $now.toISO() }} — current timestamp (ISO 8601)
• {{ $workflow.name }} — the name of the current workflow
• {{ $itemIndex }} — the index of the current item in a loop

Expressions can be used not only in text fields but also in numeric and boolean fields. For example, in a condition node, '{{ $json.completed }}' performs a direct boolean comparison. An invalid expression is highlighted in red, and you can press the 'Test' button to view the expected data structure.

Debugging and Going Live

The execution log shows per-node input and output data, error messages, and duration for every run. To activate a workflow, simply toggle the 'Inactive' switch in the top right to 'Active'.

Switching to the 'Executions' tab in the top menu lists all past runs. Each row shows the run time, status (success/failure), and total duration. Clicking a run opens the workflow view at that moment, with the input/output item count displayed on each node. A failed node is shown with a red border; clicking it lets you read the full error message and stack trace.

The 'Pin Data' feature is very helpful during debugging: when you pin a node's output, that node is not re-triggered in subsequent test runs, and downstream nodes are tested with the fixed data. This lets you develop without hitting API rate limits.

To publish your workflow, click the 'Inactive' toggle at the top right; it switches to 'Active' and your Schedule Trigger begins running automatically at the configured time. For webhook-based triggers, n8n generates a URL as soon as you activate the workflow and starts listening for incoming requests to that URL.

• Always perform a test run before activating a workflow.
• For critical production workflows, set up an error notification flow using the Error Trigger node.
• Manage execution history retention by configuring the storage duration in 'Settings > Executions'.
• For high-volume data flows, use the 'Split In Batches' node to optimise memory usage.

Next Steps: AI Integration and Webhooks

Once you have completed your basic workflow, you can build far more powerful automation scenarios using n8n's AI agent support and webhook capabilities — the two areas where enterprise automation delivers the highest value.

n8n integrates natively with large language models (LLMs). Our guide on setting up AI agents with n8n walks through step by step how to build an automation system that reasons over your own data using OpenAI or a local model. Intelligent workflows that classify customer requests, summarise reports, or detect anomalies can now be built in n8n without writing a single line of code.

Webhook integration allows external systems to trigger n8n; events such as form submissions, payment notifications, or CRM updates can instantly start a workflow. Our in-depth content on n8n Webhook and API integration covers all the capabilities of the HTTP node and secure webhook design.

As a starting point, we recommend browsing n8n's library of more than 1,700 community templates. Templates contain ready-made node configurations for specific integrations or scenarios and can be imported into your workflow with a single click, allowing you to study a working example and adapt it to your own scenario.

Frequently Asked Questions

How do I get started with n8n?

The fastest way is to open a Cloud account at n8n.io; after registering with your email, you can start building workflows in the browser immediately. For those who prefer self-hosting, installation is possible with a single Docker command.

Do I need to know how to code to use n8n?

No. n8n's visual interface allows most automation scenarios to be built without writing any code. A JavaScript-enabled Code node is available for advanced use cases, but it is not required for beginners.

How do I create my first workflow?

Open a new workflow, add a trigger node (Schedule, Webhook, or Manual), then chain your action nodes. Use the Test Workflow button to run it instantly, inspect the results in the execution log, and activate it if there are no errors.

How do I test my workflow without publishing it?

The 'Test Workflow' button at the top right runs the workflow once without activating it. You can view each node's input and output on the canvas, inspect errors, and use the Pin Data feature to fix a specific node's output for downstream testing.

Are there ready-made templates in n8n?

Yes. n8n's template library contains over 1,700 community-created workflows. You can search by category from the 'Templates' tab in the left menu or at n8n.io/workflows.

How do I activate a workflow?

Simply click the 'Inactive' toggle in the top right corner of the workflow editor. It switches to 'Active' and, depending on the trigger type, scheduling or webhook listening starts automatically. A successful test run is recommended before activating.

What resources can I use to learn n8n?

The official documentation at docs.n8n.io, the community forum at community.n8n.io, and the video tutorials on the YouTube channel are the best starting points. The examples in the template library are also the most practical way to study real workflow structures.

Conclusion

Building your first workflow with n8n is a process that moves quickly once you have grasped a few core concepts. Starting from Cloud or Docker setup, once you understand the logic of triggers, nodes, credentials, and expressions, you will have laid the foundation needed to build production-level automations. The execution log and testing mechanisms make it easy to catch errors early and go live with confidence.

If you want to move on to more complex scenarios or plan to integrate n8n with your existing enterprise systems, Sora's automation team is ready with experienced consultants for a free discovery call. Contact us today for support on automation architectures tailored to the finance, manufacturing, or public sector.