n8n Workflow Automation Studio

Complete n8n workflow automation guide covering node configuration, trigger setup, data transformation, error handling, and self-hosting for building automated business processes and integrations.

When to Use This Skill

Choose n8n Workflow Automation when:

• Building automated workflows connecting multiple APIs and services
• Creating data synchronization pipelines between tools
• Automating repetitive business processes (email, CRM, notifications)
• Setting up webhook-triggered automation
• Self-hosting workflow automation for data privacy

Consider alternatives when:

• Need simple Zapier-like point-and-click — use Zapier or Make
• Need code-first workflows — use Temporal or Inngest
• Need ML/data pipelines — use Airflow or Prefect

Quick Start

Copy
# Self-host n8n with Docker
docker run -d --name n8n -p 5678:5678 \
  -v n8n_data:/home/node/.n8n \
  -e N8N_BASIC_AUTH_ACTIVE=true \
  -e N8N_BASIC_AUTH_USER=admin \
  -e N8N_BASIC_AUTH_PASSWORD=secure_password \
  n8nio/n8n

# Activate automation studio
claude skill activate pro-n8n-workflow-automation-studio

Example: Lead Processing Workflow

Copy
{
  "name": "Lead Processing Pipeline",
  "nodes": [
    {
      "name": "Webhook Trigger",
      "type": "n8n-nodes-base.webhook",
      "parameters": {
        "path": "new-lead",
        "httpMethod": "POST",
        "responseMode": "lastNode"
      }
    },
    {
      "name": "Validate Lead",
      "type": "n8n-nodes-base.if",
      "parameters": {
        "conditions": {
          "string": [
            { "value1": "={{$json.email}}", "operation": "contains", "value2": "@" }
          ]
        }
      }
    },
    {
      "name": "Enrich with Clearbit",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "url": "=https://company.clearbit.com/v2/companies/find?domain={{$json.email.split('@')[1]}}",
        "authentication": "headerAuth",
        "headerParameters": { "values": [{ "name": "Authorization", "value": "Bearer {{$credentials.clearbitApiKey}}" }] }
      }
    },
    {
      "name": "Create in CRM",
      "type": "n8n-nodes-base.hubspot",
      "parameters": {
        "operation": "create",
        "resource": "contact",
        "email": "={{$node['Webhook Trigger'].json.email}}",
        "additionalFields": {
          "company": "={{$node['Enrich with Clearbit'].json.name}}",
          "website": "={{$node['Enrich with Clearbit'].json.domain}}"
        }
      }
    },
    {
      "name": "Notify Sales",
      "type": "n8n-nodes-base.slack",
      "parameters": {
        "channel": "#sales-leads",
        "text": "=New lead: {{$node['Webhook Trigger'].json.email}} from {{$node['Enrich with Clearbit'].json.name}}"
      }
    }
  ]
}

Core Concepts

Workflow Components

Component	Description	Example
Triggers	Start workflow execution	Webhook, Cron, Email, Database change
Regular Nodes	Process data and interact with services	HTTP Request, Code, IF, Switch
Data Transformation	Transform data between nodes	Set, Function, Merge, Split
Error Handling	Handle failures gracefully	Error Trigger, Retry, Fallback path
Sub-workflows	Reusable workflow modules	Execute Workflow node

Expression System

Expression	Purpose	Example
{{$json.field}}	Access current node data	{{$json.email}}
{{$node["Name"].json.field}}	Access specific node output	{{$node["Webhook"].json.body}}
{{$env.VAR}}	Environment variables	{{$env.API_KEY}}
{{$now}}	Current timestamp	ISO datetime
{{$workflow.id}}	Workflow metadata	Workflow ID
{{$execution.id}}	Execution metadata	Execution ID

Configuration

Parameter	Description	Default
execution_mode	Execution: regular, queue	regular
timezone	Default timezone	UTC
save_data_on_error	Save data when workflow errors	all
max_execution_time	Maximum workflow runtime	300s
concurrency	Max parallel executions	10
webhook_base_url	External webhook URL base	Auto-detect

Best Practices

1. Use error trigger workflows for monitoring — Create a dedicated error-handling workflow that catches failures from all workflows, logs the error details, and sends notifications via Slack or email. This centralizes error monitoring.

2. Split complex workflows into sub-workflows — When a workflow exceeds 15-20 nodes, extract logical sections into reusable sub-workflows. This improves readability, enables reuse, and isolates failure domains.

3. Use the Code node for complex data transformations — n8n's expression system handles simple mappings, but for complex transformations (data aggregation, conditional logic, array manipulation), use the Code node with JavaScript for clarity and maintainability.

4. Implement idempotency for webhook-triggered workflows — Webhooks may fire multiple times for the same event. Add deduplication logic (check by event ID or unique fields) before processing to prevent duplicate records or actions.

5. Version control your workflows by exporting JSON regularly — Export workflow JSON definitions to git. n8n doesn't have built-in version control, so manual exports and commit-based tracking provide the audit trail needed for production workflows.

Common Issues

Webhook URLs change after n8n restart or redeployment. Set WEBHOOK_URL environment variable to a fixed external URL. Use a reverse proxy (nginx, Caddy) with a stable domain name. For production, use N8N_HOST and N8N_PROTOCOL to generate consistent webhook URLs.

Workflow execution runs out of memory on large datasets. Process data in batches using the Loop node or SplitInBatches node. Avoid loading entire datasets into memory — use pagination for API calls and streaming for file operations. Increase the Node.js heap limit via NODE_OPTIONS=--max-old-space-size=4096.

Credentials are not portable between n8n instances. Export and import credentials separately using the n8n CLI: n8n export:credentials --all --output=creds.json. For production, use environment variables for sensitive values and reference them in credential configurations with {{$env.API_KEY}}.