How to Build Your First n8n Workflow: Step-by-Step Tutorial

This tutorial walks you through building your first n8n workflow from scratch—adding a trigger, connecting nodes, configuring credentials, testing with live data, pinning outputs for iteration, and activating for production. You’ll use the visual canvas and node panel to construct everything without coding, and you’ll move step by step from a blank canvas to a running automation in approximately 5 minutes. [1]

How do you add a trigger node to start your first n8n workflow?

Open the nodes panel by clicking the + icon in the top‑right corner of the canvas or pressing Tab. For a beginner‑friendly starting point, search for and select Manual Trigger. This node adds a button to your canvas and lets you run the workflow on‑demand without depending on an external event, so you can test freely before wiring up a real trigger. [2]

For a timer‑based automation, use instead a Schedule Trigger node and set its interval to 1 minute so you can see results quickly during testing. The official beginner tutorial recommends choosing the trigger type based on whether you want manual control or automatic execution [3]. Every workflow must begin with exactly one trigger node; learn more about all trigger types in the n8n trigger types guide.

How do you add action nodes and configure credentials for an n8n workflow?

After the trigger, click the + icon on the right side of the last node to open the node panel again. Search for the service you want to use (e.g., Slack, Gmail, or Google Sheets), select it, and the node auto‑connects to the previous one. You then fill in required fields—channel name, email address, or sheet tab—directly in the parameters panel on the right. [2]

To connect securely to an external service, click Create New next to the credential field, select the authentication type (OAuth2, API key, or Header Auth), grant permission, and n8n stores the encrypted credential for reuse in all your workflows [1]. For the HTTP Request node—the universal adapter for any API—enter the full URL, set the HTTP method, and optionally add headers or a body. For a thorough reference on these core nodes, see the core n8n nodes guide.

How do you test individual nodes and the full workflow in n8n?

Click on any node to open its details panel, then click the Execute step button to test only that node—n8n runs it with the data from the previous step and displays the output immediately underneath it. The node turns green on success and red on failure, showing the error message and stack trace for debugging before you proceed. [4]

After testing each node individually, click the Execute Workflow button at the top of the canvas to run the entire workflow end‑to‑end. The data flowing through each node is visualised in real time, and you can switch between Table, JSON, and Schema views to inspect every output format. Test executions with a Manual Trigger are free and don’t consume your plan’s monthly quota [5]. For systematic debugging strategies, see the error workflow & retry guide.

How do you pin data in n8n to avoid repeated API calls during development?

Run the node once to load live data, then click the Pin Data button in the OUTPUT panel—the data is frozen and n8n will use this snapshot on every subsequent test execution instead of calling the external API again. A “This data is pinned” banner appears in the output view, and you can unpin or edit the data at any time. [6]

You can also create completely synthetic mock data using a Code node or Set node and then pin that output for iterative development. Pinned data only works during manual testing—it is ignored during production executions, so your production automations always process live data.

How do you execute a full workflow and inspect the results in n8n?

With all nodes configured and individually tested, click Execute Workflow in the top toolbar. n8n runs every node in sequence and updates the canvas with green checkmarks on completed nodes and any red × on failures. Each node’s output panel displays the total number of items processed and the execution duration in milliseconds. [4]

For error‑checking, expand the failed node’s output or open the execution history from the left sidebar to find the exact input that caused the problem. The JSON and Schema views help pinpoint mismatches when upstream format changes break downstream logic. For a deeper walk through data flow fundamentals, see the expressions reference guide.

How do you activate an n8n workflow so it runs automatically in production?

After you complete testing, click the Publish button in the top‑right corner of the editor (previously labeled “Activate” in earlier versions). This saves a versioned snapshot and makes the workflow live. For scheduled triggers, n8n then fires automatically at the next interval; for webhook triggers, the Production URL becomes active and ready to receive requests. [7]

If a webhook trigger seems stuck on the Test URL after publishing, simply unpublish the workflow, make a small edit (like adding a space in a note), and publish again [7]. Monitor executions after activation; each execution logs to the Executions tab with a status icon, duration, and retry‑on‑failure granular settings. For robust production deployment patterns, see the production security hardening guide.