How do you set up your first n8n workflow?

Quick Answer: Create a first n8n workflow in 8 steps: access the editor, create a workflow, add a trigger node (e.g., Google Sheets row added), configure credentials via OAuth, add action nodes (e.g., Slack notification), map data using expressions, test the workflow, and activate it. Most first-timers complete a basic workflow in 12-18 minutes.

Prerequisites

Before starting, organizations need either an n8n Cloud account or a self-hosted n8n instance. n8n Cloud offers a free tier with 5 active workflows and requires no setup. Self-hosting requires Docker or a direct installation on a Linux server with Node.js 18+.

Step 1: Access the n8n Editor

For n8n Cloud, sign up at n8n.io and open the workflow editor from your dashboard. For self-hosted instances, navigate to your n8n URL (typically https://your-domain.com or http://localhost:5678). The editor presents a blank canvas with a "+" button in the center.

Step 2: Create a New Workflow

Click the "+" button or use the top-left menu to create a new workflow. Name it something descriptive (e.g., "Google Sheets to Slack Notification"). n8n saves workflows automatically as you build them.

Step 3: Add a Trigger Node

Every workflow starts with a trigger. Click the "+" button on the canvas and search for your trigger type:

  • Schedule Trigger: Runs on a cron schedule (e.g., every 5 minutes, daily at 9am)
  • Webhook: Triggered by an HTTP request from an external service
  • App Trigger: Triggered by an event in a connected app (e.g., new row in Google Sheets)

For this tutorial, select Google Sheets Trigger and choose "Row Added" as the event.

Step 4: Configure Credentials

n8n will prompt you to create a Google credential. Click "Create New Credential" and follow the OAuth flow:

  1. Sign in with your Google account
  2. Grant n8n access to Google Sheets
  3. The credential is saved and encrypted in n8n's credential store

Select the specific spreadsheet and sheet organizations want to monitor.

Step 5: Add Action Nodes

Click the "+" button to the right of your trigger node to add action steps. For a Google Sheets-to-Slack workflow:

  1. Add a Slack node
  2. Create a Slack credential (Bot Token or OAuth)
  3. Select the channel to post to
  4. Map data from the Google Sheets trigger to the Slack message

Use expressions (click the gear icon on any field) to reference data from previous nodes. For example: {{ $json.Name }} submitted a new entry will insert the "Name" column value from the Google Sheet row.

Step 6: Test Your Workflow

Click "Test workflow" in the top-right corner. n8n will execute each node sequentially and show the output data on the canvas. Green check marks indicate success; red X marks indicate errors. Click any node to inspect its input and output data.

If testing with a Google Sheets trigger, you may need to add a test row to the spreadsheet first, or use the "Execute Node" feature to simulate trigger data.

Step 7: Activate the Workflow

Once testing passes, toggle the "Active" switch in the top-right corner. The workflow is now live and will trigger automatically when new rows are added to your Google Sheet.

Step 8: Monitor Executions

Open the "Executions" tab (left sidebar) to see a log of all workflow runs. Each execution shows:

  • Start and end time
  • Status (success or error)
  • Data processed at each node
  • Any error messages with stack traces

Set up error notifications by adding a workflow-level error handler that sends a Slack message or email when any execution fails.

Common Patterns for First Workflows

Pattern Trigger Actions
Form to CRM Webhook Create/update contact in HubSpot or Salesforce
Sheet to Slack Google Sheets row added Format message, post to channel
Email to task Gmail/IMAP trigger Parse email, create task in Notion or Asana
RSS to social RSS Feed trigger Format post, publish to Twitter/LinkedIn

Editor's Note: Google Sheets-to-Slack is our standard onboarding exercise for clients new to n8n. First-timers typically complete it in 12-18 minutes. The most common stumbling point is the Google OAuth consent screen setup — Google requires configuring a Cloud project, enabling the Sheets API, and creating OAuth credentials. This adds 5-10 minutes for users without an existing Google Cloud project. We pre-configure the Google credentials for client onboarding sessions to avoid this friction.

Related Questions

Written & reviewed by Rafal Fila · Last updated:

Related Tools

Related Rankings

Best Automation Platforms for AI Orchestration 2026

This ranking answers one question: how many real business applications can an AI agent act on out of the box? It evaluates nine platforms as of August 2026 on the reach they give an agent, not on the workflow logic they can express. That boundary is deliberate, because two neighbouring pages on this site answer different questions. Best Process Orchestration Platforms 2026 scores multi-step process control, error handling and state management. Best AI Agent Platforms 2026 scores building and hosting the agent itself. This page scores the layer between them: the connective tissue that lets an agent already built elsewhere reach the applications a business actually runs on. A platform that leads one of those pages can place low here, and two of them do. Scores derive from application and action catalogue counts, the exposure model each platform uses to publish those catalogues to an agent, setup effort, failure handling and cost per agent action. Every figure was retrieved from a vendor-owned surface on 11 August 2026 unless an earlier date is stated against it.

Best Durable Workflow Engines for Production in 2026

A ranked list of the best durable workflow engines for production deployments in 2026. Durable workflow engines persist execution state to a database so that long-running workflows survive process restarts, deployments, and infrastructure failures. The ranking covers Temporal, Prefect, Apache Airflow, Camunda, Windmill, and n8n. Tools were evaluated on production reliability, developer experience, scalability, open-source health, and documentation quality. The shortlist intentionally mixes code-first engines (Temporal, Prefect, Airflow) with hybrid visual platforms (Camunda, Windmill, n8n) to reflect how production teams actually choose workflow engines in 2026.

Dive Deeper

guide

Client Portals vs Workflow Orchestration Platforms: What Changes When External Parties Act Inside a Process

What changes when a client or supplier has to act inside your process, not just watch it? This guide compares four client portals with four orchestration platforms on how outsiders get in, whether you pay for them and what the audit log records, from vendor sources read 14 and 15 September 2026.

comparison

Moxo vs Zapier in 2026: Human Approval Steps, External Participants and Pricing

Moxo and Zapier both put a person in front of an automated decision, from opposite ends: Moxo builds the process out of human steps and attaches AI, while Zapier pauses an automation for a reviewer through its Human in the Loop app. This guide compares approvers, rejection, AI approval, audit logs, governance and pricing, verified 14 and 15 September 2026.

comparison

Keystroke vs n8n in 2026: Agent-Built TypeScript vs the Visual Canvas

Keystroke, launched in July 2026 by Y Combinator W24 company Sprint Labs, is a code-first automation platform where AI coding agents write workflows as TypeScript in the user's repository. n8n, founded in 2019, is the most widely deployed source-available visual workflow platform, with 200,000+ users and a $2.5 billion valuation. This comparison covers the agent-authored versus canvas building models, durable execution, licensing (Elastic License 2.0 vs the Sustainable Use License), verified July 2026 pricing including Keystroke's usage metering, and the maturity gap between a days-old platform and an established ecosystem.