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:
- Sign in with your Google account
- Grant n8n access to Google Sheets
- 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:
- Add a Slack node
- Create a Slack credential (Bot Token or OAuth)
- Select the channel to post to
- 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
- What are the best workflow automation tools for technical writers in 2026?
- What are the best AI-native automation tools in 2026?
- What are the best automation tools for finance and AP teams in 2026?
- What are the best automation tools for solo founders in 2026?
- What are the best automation tools for nonprofits in 2026?
Related Tools
Activepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationAutomatisch
Open-source Zapier alternative
Workflow AutomationBardeen
AI-powered browser automation via Chrome extension
Workflow AutomationCalendly
Scheduling automation platform for booking meetings without email back-and-forth, with CRM integrations and routing forms for lead qualification.
Workflow AutomationRelated Rankings
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.
Best No-Code Automation Platforms in 2026
A ranked list of no-code automation platforms in 2026. The ranking covers visual workflow builders that allow non-engineering teams to connect SaaS apps, route data, and add conditional logic without writing code. Entries cover proprietary cloud platforms (Zapier, Make, Pipedream, IFTTT) and open-source visual builders (n8n, Activepieces). Scoring reflects integration breadth, pricing accessibility, visual editor ease, reliability and error handling, and self-hosting availability.
Dive Deeper
Migrating 23 Make Scenarios to Self-Hosted n8n: a 3-Week Breakdown
Anonymized retrospective of a DTC ecommerce brand migrating 23 Make scenarios to a self-hosted n8n instance over three weeks. Tooling cost dropped from $348/month on Make Teams to roughly $12/month on a Hetzner VPS, but credential and webhook recreation consumed about 40% of total project time.
Trigger.dev vs Inngest 2026: OSS Durable Runners Compared
Trigger.dev (2022, London) is a fully Apache 2.0 durable runner with task-based authoring, machine-size selection, and first-class self-host. Inngest (2021, San Francisco) is a developer-first event-driven step platform with an open-source dev server and a managed cloud (50K step runs/month free, $20/month Hobby). This 2026 comparison covers license, programming model, pricing, observability, and self-host options.
Inngest vs Temporal 2026: Durable Functions vs Durable Workflows
Inngest (2021, San Francisco) is a developer-first durable functions platform with TypeScript and Python SDKs, 50,000 step runs/month free, and Hobby pricing from $20/month. Temporal (2019) is the heavyweight durable workflow engine with seven-language SDK coverage, Cassandra-backed scale, and Cloud pricing from roughly $200/month at low volume or $2.5-4.5K/month self-host. This 2026 comparison covers programming model, pricing, scale ceiling, and operational footprint.