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
Related Tools
Activepieces
No-code workflow automation with self-hosting and AI-powered features
Workflow AutomationAutomatisch
Open-source Zapier alternative
Workflow AutomationCamunda
Open-source workflow and process automation platform using BPMN.
Workflow AutomationHuginn
Build agents that monitor and act on your behalf
Workflow AutomationRelated Rankings
Best Automation Tools for Marketing Teams in 2026
A ranked evaluation of automation tools used by marketing teams for campaign operations, data management, lead workflows, and cross-platform coordination. Unlike dedicated marketing automation platforms (email tools), this ranking evaluates general-purpose automation tools through the lens of marketing team utility. As of March 2026, marketing teams increasingly rely on a combination of workflow automation platforms and specialized marketing tools. This ranking covers the broader marketing operations (MarOps) stack -- the tools that marketing teams use day-to-day for operations, not just email campaigns. Tools were scored across five criteria specific to marketing team needs: workflow coverage, marketer accessibility, integration breadth with marketing platforms, cost efficiency, and data handling capabilities.
Best Process Orchestration Platforms 2026
Process orchestration platforms coordinate complex, multi-step workflows with dependency management, failure handling, and execution monitoring. Unlike simple automation tools that chain triggers and actions, orchestration platforms handle saga patterns, parallel execution, conditional branching, and durable execution that survives infrastructure failures. This ranking evaluates 7 orchestration platforms as of March 2026, covering both enterprise-grade BPMN engines and developer-focused open-source frameworks. The evaluation spans orchestration depth (workflow complexity support), scalability (concurrent execution capacity), developer experience (SDK quality and debugging tools), monitoring (observability and failure recovery), and community (GitHub activity and commercial support). Scores reflect production deployments managing workflows from 50 to 15,000 daily runs.
Dive Deeper
Automation for Real Estate: Lead Routing, Document Management, and CRM Workflows
Real estate businesses use automation to route leads from listing portals, manage document workflows for transactions, send automated follow-ups, and synchronize property data across platforms. As of 2026, the average mid-size brokerage automates 8 to 15 workflows spanning lead capture, nurture sequences, and transaction coordination. This guide details the automation patterns that deliver measurable ROI in residential and commercial real estate operations.
Automation for SaaS Companies: Operations, Billing, and Growth
SaaS companies rely on automation for trial-to-paid conversion, usage-based billing reconciliation, customer onboarding sequences, and internal operations. As of 2026, the typical mid-market SaaS company automates between 15 and 40 internal workflows using a combination of iPaaS tools and custom integrations. This guide covers the most common automation patterns in SaaS operations, the tools best suited for each, and the implementation considerations that distinguish successful deployments from failed ones.
Automation for Digital Agencies: Client Onboarding, Reporting, and Project Management
Digital and marketing agencies automate client onboarding, project setup, time tracking aggregation, reporting pipelines, and internal communications. As of 2026, agencies with 10 or more employees typically maintain 12 to 25 automated workflows to reduce administrative overhead and ensure consistent service delivery. This guide covers the automation patterns that scale with agency growth, from freelancer-to-team transitions through multi-office operations.