Learn n8n Automation for Free - 100 Essential Nodes Tutorial
Master n8n workflow automation with our comprehensive free tutorial covering 100 essential nodes. Learn triggers, data transformation, AI integration, and powerful automations. Complete documentation with examples.
Complete n8n Learning Path
Our comprehensive guide includes 100 carefully documented n8n nodes covering everything from basic webhooks and HTTP requests to advanced AI agents and LLM integrations. Each node includes detailed parameter documentation, practical examples, use cases, pro tips, and links to official documentation.
Node Categories
Trigger Nodes
Start workflows automatically with webhooks, schedules, or events from 100+ apps. Learn Webhook, Schedule Trigger, MQTT Trigger, RabbitMQ, Kafka, and more.
Core Nodes
The essential building blocks of any workflow. Master HTTP Request, IF, Switch, Set, Code, Merge, Wait, and other fundamental nodes.
Data Transformation Nodes
Transform, filter, merge, and shape data exactly how you need it. Learn Aggregate, Sort, Limit, Filter, Split Out, Remove Duplicates, and more.
Integration Nodes
Connect to 100+ apps and services. Gmail, Slack, Discord, Google Sheets, Airtable, Notion, HubSpot, Salesforce, Stripe, Shopify, and many more.
AI & LLM Nodes
Build AI agents, RAG systems, and LLM-powered workflows. OpenAI, Claude, Gemini, Ollama, Hugging Face, embeddings, vector stores, and AI tools.
Advanced Nodes
Master complex automation scenarios. Execute Command, SSH, GraphQL, MQTT, Kafka, AWS Lambda, and n8n's own management nodes.
All 100 n8n Nodes - Complete Documentation
Below you'll find the complete documentation of all 100 nodes, including parameters, credentials, examples, use cases, and pro tips.
1. HTTP Request Node
The HTTP Request node is the most versatile and commonly used node in n8n. It allows you to make HTTP requests to any REST API endpoint, retrieve data, send data, and interact with virtually any web service. This node supports all HTTP methods (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) and can handle various authentication types, headers, query parameters, and request bodies.
Parameters
- Method: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
- URL: The endpoint URL (supports expressions)
- Authentication: None, Basic Auth, Bearer Token, OAuth2, API Key, Custom
- Headers: Custom request headers as key-value pairs
- Query Parameters: URL query string parameters
- Body Content Type: JSON, Form-Data, Form URL Encoded, Raw, Binary
- Body: Request payload data
- Response Format: JSON, Text, Binary, File
- Timeout: Request timeout in milliseconds
- Retry on Fail: Enable automatic retries
- Max Retries: Number of retry attempts
- Ignore SSL Issues: Skip SSL certificate verification
Credentials
HTTP Request credentials (for authentication), or specific API credentials depending on the service
Example
GET request to fetch user data:
URL: https://api.example.com/users/{{$json.userId}}
Method: GET
Authentication: Bearer Token
Headers: {'Accept': 'application/json'}
Use Cases
- Fetching data from REST APIs
- Sending form submissions to webhooks
- Integrating with services without dedicated n8n nodes
- Uploading files to cloud storage APIs
- Triggering external webhooks and automation
Pro Tips
- Use expressions like {{$json.field}} to dynamically set values
- Enable 'Split Into Items' when API returns arrays
- Set appropriate timeouts for slow APIs
- Use the 'Retry on Fail' option for unreliable endpoints
- Check 'Response' tab to debug API responses
2. Webhook Node
The Webhook node creates an HTTP endpoint that can receive data from external services. When data is sent to this webhook URL, it triggers your workflow. This is essential for real-time integrations, receiving form submissions, handling payment notifications, and connecting with services that support webhook callbacks.
Parameters
- HTTP Method: GET, POST, PUT, PATCH, DELETE, HEAD (which methods to accept)
- Path: Custom URL path segment (e.g., /my-webhook)
- Authentication: None, Basic Auth, Header Auth
- Response Mode: When to respond - immediately, or after workflow completes
- Response Code: HTTP status code to return
- Response Data: What data to return in the response
- Options: Binary Data, Raw Body, IP Whitelist
Credentials
Optional: Basic Auth or Header Auth credentials for securing your webhook
Example
Receiving Stripe payment events: Path: /stripe-webhook Method: POST Authentication: Header Auth (using Stripe signature) Response Mode: Respond immediately
Use Cases
- Receiving payment notifications from Stripe/PayPal
- GitHub/GitLab push events for CI/CD
- Form submissions from websites
- IoT device data collection
- Third-party service integrations
Pro Tips
- Use 'Test URL' for development, 'Production URL' for live
- Secure webhooks with authentication for sensitive data
- Return appropriate status codes (200, 400, 500)
- Use 'Respond to Webhook' node for custom responses
- Enable binary data handling for file uploads
3. IF Node
The IF node enables conditional branching in your workflows. It evaluates conditions and routes data to different outputs based on whether conditions are true or false. You can create complex logic with multiple conditions using AND/OR operators. This is fundamental for creating dynamic, intelligent automations.
Parameters
- Conditions: Define rules using operators
- Value 1: First value to compare (supports expressions)
- Operation: Equals, Not Equals, Greater Than, Less Than, Contains, Starts With, Ends With, Is Empty, etc.
- Value 2: Second value to compare
- Combine: AND (all must match) or OR (any must match)
- Output: True branch and False branch
Example
Check if order amount exceeds $100:
Value 1: {{$json.orderAmount}}
Operation: Greater Than
Value 2: 100
True → Send VIP notification
False → Send standard confirmation
Use Cases
- Routing high-value vs low-value customers
- Filtering spam from legitimate leads
- Checking if user is authenticated
- Validating form data before processing
- Implementing approval workflows
Pro Tips
- Use multiple conditions with AND for strict matching
- Chain multiple IF nodes for complex decision trees
- The 'Contains' operator is great for text filtering
- Use 'Is Empty' to handle missing data gracefully
- Both outputs can be connected to subsequent nodes
4. Set Node
The Set node allows you to add, modify, or create new data fields in your workflow items. It's essential for data transformation, preparing data for API calls, renaming fields, and creating new calculated values. You can keep existing fields or replace all data with only the fields you specify.
Parameters
- Keep Only Set: Keep all fields or only the ones you set
- Values to Set: Define new field names and values
- Field Name: The name of the field to create/modify
- Field Type: String, Number, Boolean, Array, Object
- Field Value: The value (supports expressions)
- Dot Notation: Enable to set nested properties like 'user.address.city'
Example
Prepare data for API call:
Field 1: fullName = {{$json.firstName}} {{$json.lastName}}
Field 2: emailAddress = {{$json.email.toLowerCase()}}
Field 3: timestamp = {{Date.now()}}
Field 4: status = 'active'
Use Cases
- Renaming fields to match API requirements
- Calculating values from existing data
- Creating standardized data formats
- Adding timestamps or IDs to records
- Preparing webhook payloads
Pro Tips
- Use expressions for dynamic values
- Enable 'Keep Only Set' to clean up unnecessary fields
- Dot notation works for nested objects
- Combine with Merge node for complex transformations
- String type supports template literals
5. Code Node
The Code node allows you to write custom JavaScript or Python code within your workflow. This is incredibly powerful for complex data transformations, custom logic, API interactions that need special handling, and anything that built-in nodes can't accomplish. You have full access to the input data and can return any data structure.
Parameters
- Language: JavaScript or Python
- Mode: Run Once for All Items, or Run Once for Each Item
- JavaScript/Python Code: Your custom code
- Available Variables: $input, $json, $items(), $env, $execution, $node, $workflow
Example
JavaScript - Transform and filter data:
const results = [];
for (const item of $input.all()) {
if (item.json.status === 'active') {
results.push({
json: {
id: item.json.id,
name: item.json.name.toUpperCase(),
createdAt: new Date().toISOString()
}
});
}
}
return results;
Use Cases
- Complex data transformations
- Custom validation logic
- Parsing non-standard data formats
- Mathematical calculations
- Working with dates and times
- String manipulation and regex
Pro Tips
- $input.all() returns all items, $input.first() returns first item
- Always return an array of items with {json: {...}} structure
- Use try/catch for error handling
- Access environment variables with $env.VAR_NAME
- Python mode requires specific syntax for item access
6. Schedule Trigger Node
The Schedule Trigger node starts your workflow at specified times or intervals. Use it for automated reports, periodic data syncs, cleanup jobs, reminders, and any task that needs to run on a schedule. Supports cron expressions for complex scheduling.
Parameters
- Trigger Interval: Seconds, Minutes, Hours, Days, Weeks, Months, Custom (Cron)
- Interval Value: How often to trigger
- Trigger at Day of Week: For weekly triggers
- Trigger at Day of Month: For monthly triggers
- Trigger at Hour: What hour to run
- Trigger at Minute: What minute to run
- Cron Expression: Custom cron for complex schedules
Example
Daily report at 9 AM: Trigger Interval: Days Trigger at Hour: 9 Trigger at Minute: 0 Or using Cron: 0 9 * * * (every day at 9:00 AM)
Use Cases
- Daily/weekly automated reports
- Hourly data synchronization
- Database cleanup jobs
- Social media scheduled posts
- Invoice generation
- Health checks and monitoring
Pro Tips
- Cron format: minute hour day-of-month month day-of-week
- Use crontab.guru to validate cron expressions
- Schedule considers server timezone
- Combine with IF node for conditional execution
- Add error handling for long-running jobs
7. Merge Node
The Merge node combines data from multiple workflow branches into a single stream. It offers various modes for merging: appending items, matching by field values, or combining based on position. Essential for workflows where you need to gather data from multiple sources.
Parameters
- Mode: Append, Merge by Position, Merge by Key, Keep Key Matches, Remove Key Matches, Combine
- Join Mode: Inner Join, Left Join, Keep Non-Matches
- Match Fields: Fields to match on when using key-based merging
- Output Data: All matches, first match only
- Options: Disable Dot Notation, Clash Handling
Example
Merge user data with order data: Mode: Merge by Key Input 1 Property: userId Input 2 Property: customerId Result: Combined records where userId matches customerId
Use Cases
- Combining API responses from multiple services
- Enriching lead data with additional info
- Matching records from different databases
- Comparing old vs new data
- Aggregating parallel branch results
Pro Tips
- Append mode simply stacks all items together
- Merge by Key works like SQL JOIN
- Use 'Keep Key Matches' to filter to only matching records
- Position-based merge requires same item count in both inputs
- Enable 'Combine All' to create all possible combinations
8. Switch Node
The Switch node routes items to different outputs based on matching rules. Unlike IF (which has only true/false), Switch can have multiple outputs for different conditions. Think of it as a multi-way branch - like a switch statement in programming.
Parameters
- Mode: Rules or Expression
- Rules: Define conditions for each output
- Data Type: String, Number, Boolean, Date/Time
- Routing Rules: Each rule creates a separate output
- Output: Number of outputs equals number of rules plus fallback
- Fallback Output: Where non-matching items go
Example
Route orders by status: Rule 1: status equals 'pending' → Output 0 Rule 2: status equals 'processing' → Output 1 Rule 3: status equals 'shipped' → Output 2 Fallback → Output 3 (handle unknown statuses)
Use Cases
- Multi-department ticket routing
- Priority-based processing
- Country/region-specific workflows
- Order status handling
- Role-based access control
Pro Tips
- Order rules from most to least specific
- Use fallback output for error handling
- Expression mode allows complex conditions
- Combine with Merge to reunite branches later
- Each output can go to different workflow branches
9. Loop Over Items Node
The Loop Over Items node (formerly Split In Batches) processes items in batches rather than all at once. This is crucial for handling large datasets, respecting API rate limits, and avoiding memory issues. It enables loop-like behavior in your workflows.
Parameters
- Batch Size: Number of items to process per iteration
- Options: Reset on each run
- Done output: When all batches are complete
- Loop output: For continuing the loop
Example
Process 100 records in batches of 10: Batch Size: 10 First iteration: items 1-10 Second iteration: items 11-20 ... and so on After all: Continues from 'Done' output
Use Cases
- Processing large CSV imports
- Respecting API rate limits (e.g., 100 requests/minute)
- Bulk operations on databases
- Pagination handling
- Memory-efficient large data processing
Pro Tips
- Connect 'Loop' output back to the node to process next batch
- Connect 'Done' output to continue workflow after all items
- Use smaller batches for slow APIs
- Add Wait node for strict rate limiting
- Monitor memory usage for very large datasets
10. Wait Node
The Wait node pauses workflow execution for a specified duration or until a specific time. Useful for rate limiting, scheduling delays, waiting for external processes to complete, or implementing retry logic with delays.
Parameters
- Resume: After Time Interval, At Specified Time, On Webhook Call
- Wait Amount: Duration to wait
- Wait Unit: Seconds, Minutes, Hours, Days
- Date and Time: Specific datetime to resume
- Webhook: Resume when a webhook is called
Example
Wait 5 seconds between API calls: Resume: After Time Interval Wait Amount: 5 Wait Unit: Seconds
Use Cases
- API rate limiting delays
- Waiting for file processing
- Scheduled follow-up actions
- Implementing retry delays
- Pausing for external processes
Pro Tips
- Use with Loop node for rate limiting
- Webhook resume is great for async processes
- Consider 'At Specified Time' for scheduled events
- Long waits may timeout on cloud instances
- Use execution data to track wait status
11. Edit Fields Node
The Edit Fields node (also known as Rename Keys) allows you to rename, copy, delete, or reorder fields in your data. It's a simpler alternative to Set node when you just need to restructure existing data without complex transformations.
Parameters
- Operation: Rename Keys, Set/Add Fields, Remove Fields
- Fields: Source field and target field mappings
- Include: Which fields to keep
- Options: Deep Copy, Ignore Non-Existing
Example
Rename API response fields: Operation: Rename Keys user_name → name email_address → email created_at → createdAt
Use Cases
- Converting snake_case to camelCase
- Mapping API fields to database columns
- Removing sensitive fields before logging
- Reordering fields for export
- Standardizing data between systems
Pro Tips
- Use 'Include All' then exclude specific fields
- Enable 'Deep Copy' for nested objects
- Combine with Set node for complex transformations
- Order matters when renaming multiple fields
12. Filter Node
The Filter node removes items from the workflow that don't match specified conditions. Unlike IF node which creates two branches, Filter simply passes through matching items and discards the rest. Perfect for cleaning data and focusing on relevant records.
Parameters
- Conditions: Define filter rules
- Value: The field to check
- Operation: Equals, Not Equals, Contains, Greater Than, etc.
- Compare To: The value to compare against
- Combine: AND (all conditions) or OR (any condition)
Example
Keep only active premium users: Condition 1: status equals 'active' AND Condition 2: plan equals 'premium' Result: Only items matching both conditions pass through
Use Cases
- Removing test/spam data
- Filtering by date ranges
- Keeping only new records
- Excluding specific categories
- Quality control before processing
Pro Tips
- Use Contains for partial text matching
- Combine multiple conditions with AND for precise filtering
- The 'Exists' operation checks if a field is present
- Filter early in workflows to improve performance
13. Aggregate Node
The Aggregate node combines multiple items into summarized data or a single item. Use it for calculating totals, averages, counts, or creating arrays from individual items. Essential for reporting and data analysis workflows.
Parameters
- Aggregate: All Item Data, Individual Fields
- Fields to Aggregate: Which fields to process
- Aggregation: Sum, Count, Average, Min, Max, Concatenate
- Include: All fields or specific fields
- Merge: Combine all items into one
Example
Calculate sales summary: Field: amount → Sum (Total Sales) Field: orderId → Count (Number of Orders) Field: amount → Average (Average Order Value)
Use Cases
- Daily/weekly sales reports
- Counting items by category
- Calculating averages and totals
- Merging multiple items into one
- Creating summary statistics
Pro Tips
- Use 'All Item Data' to merge entire items
- Concatenate creates comma-separated lists
- Group before aggregating for subtotals
- Output is a single item with aggregated values
14. Sort Node
The Sort node reorders items based on field values. You can sort alphabetically, numerically, by date, and in ascending or descending order. Multiple sort fields are supported for complex ordering.
Parameters
- Field Name: Which field to sort by
- Order: Ascending or Descending
- Type: String, Number, Date
- Options: Case Sensitive, Multiple sort fields
Example
Sort orders by priority then date: Field 1: priority (Number, Descending) - high priority first Field 2: createdAt (Date, Ascending) - oldest first within same priority
Use Cases
- Priority-based task ordering
- Chronological event lists
- Alphabetical sorting for reports
- Top N by value selection
- Consistent data ordering
Pro Tips
- Sort after filtering for better performance
- Use with Limit node to get 'top N' items
- Date sorting requires proper date format
- Case sensitive by default for strings
15. Limit Node
The Limit node restricts the number of items passed through. Use it to get the first N items, implement pagination, or prevent overwhelming downstream services with too much data.
Parameters
- Max Items: Maximum number of items to output
- Keep: First items or Last items
Example
Get top 10 highest-value orders: 1. Sort by orderValue descending 2. Limit to 10 items (First items)
Use Cases
- Top N records selection
- Implementing pagination
- Limiting API responses
- Sample data for testing
- Preventing data overload
Pro Tips
- Combine with Sort for 'top N' use cases
- Use in loops for pagination
- 'Last items' is useful after reverse chronological sort
- Apply early to improve workflow performance
16. Remove Duplicates Node
The Remove Duplicates node eliminates duplicate items based on field values. Essential for data cleaning, ensuring unique records, and preventing duplicate actions in your workflows.
Parameters
- Compare: All Fields, Selected Fields
- Fields to Compare: Which fields determine uniqueness
- Keep: First or Last occurrence of duplicates
Example
Remove duplicate email entries: Compare: Selected Fields Fields: email Keep: First occurrence Result: Only unique emails remain
Use Cases
- Email list deduplication
- Preventing duplicate notifications
- Cleaning imported data
- Unique visitor tracking
- Database insert preparation
Pro Tips
- Compare on unique identifiers (email, ID)
- Use 'All Fields' for exact duplicate detection
- Keep 'Last' for most recent version
- Combine multiple fields for composite uniqueness
17. Split Out Node
The Split Out node takes an array field within an item and creates separate items for each array element. This is the opposite of Aggregate - it explodes arrays into individual items for processing.
Parameters
- Field to Split Out: The array field name
- Include: Other fields to include with each new item
- Options: Destination Field Name
Example
Split order items:
Input: { orderId: 123, items: ['A', 'B', 'C'] }
Field to Split: items
Output: 3 items, each with orderId and one item value
Use Cases
- Processing order line items
- Handling multi-value form submissions
- Expanding nested data structures
- Processing array responses from APIs
- Creating individual records from lists
Pro Tips
- Keep parent fields with 'Include' options
- Useful after JSON parse for nested arrays
- Combine with Set to restructure split data
- Works great before loop processing
18. Respond to Webhook Node
The Respond to Webhook node sends a custom response back to the webhook caller. Use it when the Webhook trigger is set to 'Respond: Using Respond to Webhook Node'. This allows you to process data before responding and send dynamic responses.
Parameters
- Response Code: HTTP status code (200, 400, 500, etc.)
- Response Headers: Custom HTTP headers
- Response Body: Data to return
- Options: Binary Data, No Response Body
Example
Return processed data:
Response Code: 200
Response Body: {
'success': true,
'processedId': '{{$json.id}}',
'timestamp': '{{$now}}'
}
Use Cases
- Returning validation results
- Sending confirmation with processed ID
- API endpoint responses
- Error messages to callers
- Returning transformed data
Pro Tips
- Webhook must use 'Using Respond to Webhook Node' mode
- Can appear anywhere in the workflow
- Multiple respond nodes = only first executed is sent
- Include appropriate status codes for errors
19. Execute Workflow Node
The Execute Workflow node calls another n8n workflow as a sub-workflow. This enables modular workflow design, code reuse, and complex automation by breaking large workflows into manageable pieces.
Parameters
- Source: Database (select workflow) or Parameter (workflow ID)
- Workflow ID: The workflow to execute
- Mode: Call directly, or spawn as new execution
- Wait for Sub-Workflow: Wait for completion or continue
- Input Data: Data to pass to sub-workflow
Example
Modular order processing: Main workflow: Receive order → Execute 'Validate Order' workflow → Execute 'Process Payment' workflow → Execute 'Send Notification' workflow
Use Cases
- Reusable utility workflows
- Complex multi-stage processes
- Error handling workflows
- Parallel processing
- Workflow organization and modularity
Pro Tips
- Sub-workflows can return data to parent
- Use for common operations like email formatting
- Great for error handling routines
- Can trigger multiple sub-workflows in parallel
- Sub-workflow needs trigger node to receive data
20. No Operation Node
The No Operation (NoOp) node passes data through without modification. It's primarily used for documentation, debugging, organizing complex workflows, and as a placeholder during development.
Parameters
- No parameters - simply passes data through unchanged
Example
Use case: Debug point in workflow Node before → NoOp (click to inspect data) → Node after
Use Cases
- Debugging and inspecting data flow
- Workflow documentation/comments
- Placeholder during development
- Merging multiple branches
- Visual workflow organization
Pro Tips
- Great for seeing data at specific points
- Use descriptive names like 'Debug Point' or 'Data: After Transform'
- Can be left in production workflows
- Zero performance impact
21. Gmail Node
The Gmail node integrates with Google's email service. It can send emails, read messages, manage labels, handle drafts, and work with threads. Essential for email automation, notifications, and processing incoming emails.
Parameters
- Resource: Message, Thread, Label, Draft
- Operation: Send, Get, Get Many, Delete, Reply, Add Label, Remove Label
- To: Recipient email addresses
- Subject: Email subject line
- Email Type: Text or HTML
- Message: Email body content
- Attachments: File attachments
- Options: CC, BCC, Reply-To, References
Credentials
Gmail OAuth2 credentials (requires Google Cloud project setup)
Example
Send HTML email with dynamic content:
Resource: Message
Operation: Send
To: {{$json.customerEmail}}
Subject: Order #{{$json.orderId}} Confirmation
Email Type: HTML
Message: <h1>Thank you!</h1><p>Your order is confirmed.</p>
Use Cases
- Automated email notifications
- Order confirmations
- Lead follow-up sequences
- Email parsing and processing
- Newsletter sending
Pro Tips
- Use HTML type for rich formatting
- Add attachments from previous nodes
- Label operations help organize responses
- Use Message-ID for threading
- Rate limits apply - batch with Wait node
22. Slack Node
The Slack node enables sending messages, managing channels, uploading files, and interacting with Slack workspaces. Perfect for team notifications, alerts, and integrating business processes with Slack.
Parameters
- Resource: Message, Channel, User, File, Reaction, User Group
- Operation: Post, Update, Delete, Get, Get Many, Upload
- Channel: Target channel (ID or name)
- Text: Message content (supports Markdown)
- Blocks: Rich message blocks (JSON)
- Attachments: Message attachments
- Options: Thread TS, Unfurl, As User
Credentials
Slack OAuth2 or Bot Token credentials
Example
Post alert to channel:
Resource: Message
Operation: Post
Channel: #alerts
Text: :warning: *Alert*: {{$json.alertType}}\n{{$json.message}}
Use Cases
- System monitoring alerts
- Sales notifications
- Build/deploy announcements
- Customer support tickets
- Daily summaries
Pro Tips
- Use Slack markdown for formatting
- Thread messages for organized conversations
- Blocks allow rich interactive messages
- Mention users with <@USER_ID>
- Channel names need # prefix
23. Discord Node
The Discord node sends messages to Discord channels via webhooks or bot integration. Great for gaming communities, development teams, and community notifications.
Parameters
- Resource: Message, Channel, Role, Member
- Operation: Send (via webhook), Post, Get Many
- Webhook URL: Discord webhook URL
- Content: Message text
- Embeds: Rich embed messages (JSON)
- Options: Username, Avatar URL, TTS
Credentials
Discord Webhook URL or Bot OAuth2
Example
Send webhook message: Webhook URL: https://discord.com/api/webhooks/... Content: New deployment completed! :rocket: Username: Deploy Bot
Use Cases
- Deployment notifications
- Community announcements
- Alert systems
- Bot interactions
- Event notifications
Pro Tips
- Webhooks are simpler than bot integration
- Use embeds for rich formatting
- Custom username/avatar per message
- Discord markdown for formatting
- Rate limits apply (30 messages/minute)
24. Telegram Node
The Telegram node integrates with Telegram messaging. Send messages, photos, documents, and manage bots. Popular for personal notifications, group communications, and bot development.
Parameters
- Resource: Message, Chat, File, Callback
- Operation: Send Message, Send Photo, Send Document, Edit Message, Delete Message
- Chat ID: Target chat/user/group ID
- Text: Message content (Markdown or HTML)
- Parse Mode: Markdown, HTML, or None
- Reply Markup: Inline keyboards, buttons
- Options: Disable Notification, Protect Content
Credentials
Telegram Bot API credentials (Bot Token from @BotFather)
Example
Send formatted message:
Operation: Send Message
Chat ID: {{$json.userId}}
Text: *Order Update*\nYour order #{{$json.orderId}} has shipped!
Parse Mode: Markdown
Use Cases
- Personal notifications
- Order status updates
- Alert systems
- Customer support bots
- Group announcements
Pro Tips
- Create bot via @BotFather on Telegram
- Get chat ID from updates or @userinfobot
- Use inline keyboards for interactive bots
- Markdown V2 requires escape characters
- Documents can be sent from URLs
25. Microsoft Teams Node
The Microsoft Teams node enables messaging, channel management, and team collaboration integration. Essential for enterprise environments using Microsoft 365.
Parameters
- Resource: Message, Channel, Team, Chat
- Operation: Send, Get, Create, List
- Team: Target team
- Channel: Target channel
- Content Type: Text or HTML
- Message: Message content
- Options: Attachments, Importance, Mentions
Credentials
Microsoft OAuth2 credentials
Example
Post channel message:
Resource: Message
Operation: Send
Team: Development
Channel: General
Message: Build #{{$json.buildNumber}} completed successfully! :white_check_mark:
Use Cases
- CI/CD notifications
- Incident alerts
- Daily standups automation
- Project updates
- Team announcements
Pro Tips
- Requires Microsoft 365 subscription
- Adaptive Cards for rich messages
- Tag team members with @mentions
- Bot accounts have rate limits
- Webhook alternative for simpler use
26. SendGrid Node
The SendGrid node provides transactional and marketing email capabilities. Send single or bulk emails, use templates, and manage contacts. Popular for email marketing and transactional notifications.
Parameters
- Resource: Email, Contact, List, Template
- Operation: Send, Create, Get, Delete
- From Email: Sender address
- To Email: Recipient(s)
- Subject: Email subject
- Content Type: Text/HTML/Template
- Dynamic Template ID: For template-based emails
- Template Data: Variables for templates
Credentials
SendGrid API Key
Example
Send template email:
Resource: Email
Operation: Send
From: noreply@company.com
To: {{$json.email}}
Dynamic Template ID: d-xxxx
Template Data: { 'firstName': '{{$json.name}}', 'orderTotal': '{{$json.total}}' }
Use Cases
- Transactional emails
- Marketing campaigns
- Welcome sequences
- Password reset emails
- Bulk notifications
Pro Tips
- Use templates for consistent formatting
- Dynamic data with template variables
- Verify sender domains for deliverability
- Check bounce/spam reports
- Use categories for analytics
27. Twilio Node
The Twilio node enables SMS messaging and phone call automation. Send text messages, make calls, and handle voice responses. Essential for two-factor authentication, notifications, and customer communication.
Parameters
- Resource: SMS, MMS, Call
- Operation: Send, Make Call
- From: Your Twilio phone number
- To: Recipient phone number (E.164 format)
- Body: Message content
- Media URL: For MMS images
- TwiML: For call scripts
Credentials
Twilio API credentials (Account SID and Auth Token)
Example
Send SMS notification:
Resource: SMS
Operation: Send
From: +15551234567
To: {{$json.phoneNumber}}
Body: Your verification code is {{$json.code}}
Use Cases
- Two-factor authentication
- Appointment reminders
- Order status updates
- Emergency alerts
- Marketing campaigns
Pro Tips
- Phone numbers must be E.164 format (+1234567890)
- Verify Twilio phone number ownership
- SMS character limits apply (160 chars)
- Use TwiML for voice call scripts
- Check message delivery status
28. WhatsApp Business Node
The WhatsApp Business node integrates with WhatsApp Business API for sending messages, templates, and media. Essential for customer support and business communication.
Parameters
- Resource: Message, Template
- Operation: Send
- Phone Number ID: Your WhatsApp Business number ID
- Recipient: Customer phone number
- Type: Text, Template, Image, Document, Audio, Video
- Template Name: Pre-approved template name
- Template Language: Template language code
Credentials
WhatsApp Business Cloud API credentials
Example
Send template message: Resource: Template Operation: Send Recipient: +1234567890 Template Name: order_confirmation Template Variables: [orderId, total]
Use Cases
- Customer notifications
- Order confirmations
- Shipping updates
- Support automation
- Appointment reminders
Pro Tips
- Templates must be pre-approved by Meta
- Use for 24-hour conversation window
- Rich media supported (images, documents)
- Requires WhatsApp Business API access
- Phone numbers need country code
29. Google Sheets Node
The Google Sheets node reads from and writes to Google Spreadsheets. Perfect for data storage, reporting, form data collection, and as a simple database alternative for small projects.
Parameters
- Resource: Spreadsheet, Sheet
- Operation: Append, Update, Get, Get Many, Delete, Clear, Create
- Document ID: Spreadsheet ID from URL
- Sheet: Sheet name or gid
- Range: Cell range (A1 notation)
- Data: Row data to write
- Options: Header Row, Value Input Option
Credentials
Google OAuth2 or Service Account credentials
Example
Append new lead:
Operation: Append Row
Document ID: (from spreadsheet URL)
Sheet: Leads
Values: Name = {{$json.name}}, Email = {{$json.email}}, Date = {{$now}}
Use Cases
- Lead collection from forms
- Reporting dashboards
- Simple data storage
- Data export/import
- Collaborative data management
Pro Tips
- Sheet ID is in the URL after /d/
- Use 'Get Many' with filters for querying
- First row should be headers
- Date formatting may need adjustment
- Batch operations for better performance
30. Airtable Node
The Airtable node connects to Airtable bases for database-like operations. Create, read, update, and delete records. Great for CRM, project management, and content management use cases.
Parameters
- Operation: Create, Get, Get Many, Update, Delete, Search
- Base ID: Airtable base identifier
- Table: Table name or ID
- Record ID: For single record operations
- Fields: Record field values
- Filter Formula: Airtable formula for filtering
- Sort: Sort field and direction
Credentials
Airtable Personal Access Token or OAuth2
Example
Create new record:
Operation: Create
Base: appXXXXXX
Table: Contacts
Fields: Name = {{$json.name}}, Email = {{$json.email}}, Status = 'New'
Use Cases
- CRM operations
- Project tracking
- Content calendars
- Inventory management
- Lead databases
Pro Tips
- Base ID starts with 'app', Table ID starts with 'tbl'
- Use formula filtering for efficient queries
- Linked records use record IDs
- Attachment fields need special handling
- Rate limits: 5 requests per second per base
31. Notion Node
The Notion node integrates with Notion workspaces for page and database operations. Create pages, manage databases, and search content. Popular for documentation and knowledge management automation.
Parameters
- Resource: Page, Database, Block, User
- Operation: Create, Get, Get Many, Update, Archive, Append, Search
- Database ID / Page ID: Target resource
- Properties: Page/database properties
- Content: Block content for pages
- Filter: Query filter for database
Credentials
Notion API credentials (Integration Token)
Example
Create database entry:
Resource: Database
Operation: Append
Database ID: (from database URL)
Properties: Title = {{$json.name}}, Status = 'In Progress', Due Date = {{$json.dueDate}}
Use Cases
- Task automation
- Documentation updates
- Content publishing
- Meeting notes
- Project tracking
Pro Tips
- Share pages/databases with your integration
- Database ID is in the URL
- Properties must match database schema
- Rich text requires specific block format
- Use search for finding content
32. Trello Node
The Trello node manages cards, lists, and boards in Trello. Create cards, move them between lists, add comments, and automate your Kanban workflow.
Parameters
- Resource: Board, Card, List, Checklist, Label, Attachment
- Operation: Create, Get, Update, Delete, Move
- Board ID: Target board
- List ID: Target list
- Card Name: Card title
- Description: Card description
- Due Date: Card due date
- Labels: Card labels
Credentials
Trello API credentials (API Key and Token)
Example
Create support ticket card:
Resource: Card
Operation: Create
List ID: {{$json.supportListId}}
Name: Support: {{$json.subject}}
Description: From: {{$json.email}}\n\n{{$json.message}}
Use Cases
- Support ticket creation
- Task automation
- Sprint planning
- Content pipeline
- Lead tracking
Pro Tips
- Get IDs from Trello API or browser console
- Use webhooks for trigger events
- Checklists can be automated
- Labels are great for categorization
- Due dates include time component
33. Jira Software Node
The Jira node integrates with Jira Software for issue tracking and project management. Create issues, update status, add comments, and manage sprints programmatically.
Parameters
- Resource: Issue, Project, User, Sprint
- Operation: Create, Get, Get Many, Update, Delete, Changelog, Notify, Transitions
- Project: Jira project key
- Issue Type: Bug, Story, Task, Epic, etc.
- Summary: Issue title
- Description: Issue description
- Priority: Issue priority
- Assignee: Assigned user
Credentials
Jira API Token or OAuth2 credentials
Example
Create bug from alert:
Resource: Issue
Operation: Create
Project: PROJ
Issue Type: Bug
Summary: [Auto] {{$json.alertTitle}}
Description: Alert triggered at {{$json.timestamp}}\n\n{{$json.details}}
Priority: High
Use Cases
- Automated bug creation
- Sprint management
- Status sync across systems
- Time tracking
- Release management
Pro Tips
- Project key is the prefix (e.g., PROJ-123)
- Custom fields need field IDs
- Use transitions for status changes
- JQL for advanced querying
- Webhooks for event triggers
34. GitHub Node
The GitHub node integrates with GitHub repositories for issue management, pull requests, releases, and repository automation. Essential for DevOps and development workflows.
Parameters
- Resource: Issue, Pull Request, Release, Repository, User, File, Review
- Operation: Create, Get, Edit, Lock, Add Labels, Remove Labels
- Owner: Repository owner (username or org)
- Repository: Repository name
- Issue Number / PR Number: For specific operations
- Title: Issue/PR title
- Body: Description content
Credentials
GitHub OAuth2 or Personal Access Token
Example
Create issue from bug report:
Resource: Issue
Operation: Create
Owner: myorg
Repository: myrepo
Title: Bug: {{$json.title}}
Body: Reported by: {{$json.reporter}}\n\n{{$json.description}}
Labels: ['bug', 'needs-triage']
Use Cases
- Automated issue creation
- PR status notifications
- Release automation
- Repository management
- CI/CD integration
Pro Tips
- Personal access tokens need appropriate scopes
- Use webhooks for real-time triggers
- Markdown supported in bodies
- Labels must exist before adding
- Rate limits apply (5000 requests/hour)
35. GitLab Node
The GitLab node connects to GitLab for repository, issue, and merge request management. Similar to GitHub node but for GitLab instances including self-hosted.
Parameters
- Resource: Issue, Repository, Release, User, Merge Request
- Operation: Create, Get, Get Many, Update, Delete
- Project ID or Path: Target project
- Title: Issue/MR title
- Description: Content body
- Labels: Comma-separated labels
- Assignees: User IDs
Credentials
GitLab API credentials (Access Token)
Example
Create deployment issue:
Resource: Issue
Operation: Create
Project: group/project
Title: Deploy: {{$json.version}}
Description: Deployment scheduled for {{$json.deployTime}}
Labels: deployment, production
Use Cases
- Issue tracking automation
- CI/CD pipeline triggers
- Merge request workflows
- Release management
- DevOps automation
Pro Tips
- Works with GitLab.com and self-hosted
- Project can be ID or 'namespace/project'
- Configure base URL for self-hosted
- Supports GitLab webhooks for triggers
- Personal access tokens need api scope
36. Stripe Node
The Stripe node integrates with Stripe for payment processing, customer management, and subscription handling. Essential for e-commerce and SaaS payment automation.
Parameters
- Resource: Customer, Charge, Invoice, Subscription, Product, Price, Payment Intent
- Operation: Create, Get, Get Many, Update, Delete
- Customer ID: Stripe customer ID
- Amount: Payment amount (in cents)
- Currency: Payment currency
- Description: Payment description
- Metadata: Custom metadata
Credentials
Stripe API credentials (Secret Key)
Example
Create customer and subscription:
1. Create Customer: email = {{$json.email}}, name = {{$json.name}}
2. Create Subscription: customer = {{$json.customerId}}, price = price_xxx
Use Cases
- Payment processing
- Subscription management
- Invoice generation
- Customer onboarding
- Refund automation
Pro Tips
- Use test mode keys for development
- Amounts are in cents (100 = $1.00)
- Webhooks for payment events
- Metadata for custom tracking
- Idempotency keys prevent duplicates
37. Shopify Node
The Shopify node connects to Shopify stores for order management, product updates, and customer operations. Essential for e-commerce automation.
Parameters
- Resource: Order, Product, Customer, Inventory, Collection
- Operation: Create, Get, Get Many, Update, Delete
- Order ID / Product ID: Resource identifiers
- Fulfillment Status: Order fulfillment status
- Financial Status: Payment status
- Product Details: Title, description, variants
Credentials
Shopify API credentials (Access Token)
Example
Fulfill order:
Resource: Order
Operation: Update
Order ID: {{$json.orderId}}
Fulfillment Status: fulfilled
Tracking Number: {{$json.tracking}}
Use Cases
- Order fulfillment
- Inventory sync
- Product catalog updates
- Customer segmentation
- Sales reporting
Pro Tips
- Use Shopify webhooks for triggers
- Rate limits: 2 requests/second
- Inventory managed per location
- Variants are separate from products
- GraphQL API for complex queries
38. HubSpot Node
The HubSpot node integrates with HubSpot CRM for contact, company, deal, and ticket management. Perfect for sales and marketing automation.
Parameters
- Resource: Contact, Company, Deal, Ticket, Engagement, Form
- Operation: Create, Get, Get Many, Get Recently Created/Updated, Update, Delete, Search
- Properties: CRM property values
- Filters: Search filters
- Associations: Link to other objects
Credentials
HubSpot API credentials or OAuth2
Example
Create or update contact:
Resource: Contact
Operation: Upsert
Email: {{$json.email}}
Properties: firstname = {{$json.firstName}}, lastname = {{$json.lastName}}, company = {{$json.company}}
Use Cases
- Lead capture and sync
- Deal pipeline automation
- Contact enrichment
- Support ticket creation
- Marketing automation
Pro Tips
- Use internal property names, not labels
- Upsert prevents duplicate contacts
- Associations link contacts to companies/deals
- Webhooks for real-time triggers
- Rate limits vary by subscription
39. Salesforce Node
The Salesforce node connects to Salesforce CRM for comprehensive object operations. Manage leads, opportunities, accounts, contacts, and custom objects.
Parameters
- Resource: Account, Contact, Lead, Opportunity, Case, Task, Custom Object
- Operation: Create, Get, Get Many, Update, Delete, Upsert, Add to Campaign
- Object Type: Salesforce object type
- Record ID: Salesforce record ID
- Fields: Object field values
- External ID: For upsert operations
Credentials
Salesforce OAuth2 credentials
Example
Create lead from form:
Resource: Lead
Operation: Create
Company: {{$json.company}}
LastName: {{$json.lastName}}
Email: {{$json.email}}
Lead Source: Web Form
Use Cases
- Lead management
- Opportunity tracking
- Case creation
- Data synchronization
- Custom object automation
Pro Tips
- Use API names, not labels
- Connected App required for OAuth
- SOQL for complex queries
- Bulk API for large operations
- Field-level security affects visibility
40. Zendesk Node
The Zendesk node integrates with Zendesk Support for ticket, user, and organization management. Essential for customer support automation.
Parameters
- Resource: Ticket, User, Organization, Ticket Field
- Operation: Create, Get, Get Many, Update, Delete, Recover
- Subject: Ticket subject
- Description: Ticket description
- Priority: Urgent, High, Normal, Low
- Status: New, Open, Pending, Solved, Closed
- Type: Problem, Incident, Question, Task
Credentials
Zendesk API credentials (Token or OAuth2)
Example
Create support ticket:
Resource: Ticket
Operation: Create
Subject: {{$json.subject}}
Description: {{$json.message}}
Requester Email: {{$json.email}}
Priority: Normal
Type: Question
Use Cases
- Ticket creation from emails/forms
- Automated ticket routing
- Status updates
- Customer lookup
- Support analytics
Pro Tips
- Use email for requester lookup
- Custom fields use IDs
- Macros for common updates
- Webhooks for ticket events
- Side conversations for internal notes
41. PostgreSQL Node
The PostgreSQL node connects to PostgreSQL databases for SQL operations. Execute queries, insert/update/delete records, and work with database tables directly.
Parameters
- Operation: Execute Query, Insert, Update, Delete
- Query: SQL query (for Execute Query)
- Table: Target table name
- Columns: Columns to select/update
- Where: Conditions for filtering
- Options: Return type, additional outputs
Credentials
PostgreSQL database credentials (host, port, user, password, database)
Example
Insert record:
Operation: Insert
Table: users
Columns: name, email, created_at
Values from: {{$json.name}}, {{$json.email}}, {{$now}}
Use Cases
- Database CRUD operations
- Reporting queries
- Data synchronization
- ETL pipelines
- Backup and migration
Pro Tips
- Use parameterized queries to prevent SQL injection
- Limit result sets for large tables
- Use transactions for multiple operations
- Index frequently queried columns
- SSL required for production
42. MySQL Node
The MySQL node connects to MySQL/MariaDB databases for SQL operations. Similar to PostgreSQL node but for MySQL-compatible databases.
Parameters
- Operation: Execute Query, Insert, Update, Delete
- Query: SQL query text
- Table: Target table
- Columns: Column mappings
- Where Conditions: Filter criteria
- Options: SSL, additional settings
Credentials
MySQL database credentials
Example
Query with parameters:
Operation: Execute Query
Query: SELECT * FROM orders WHERE customer_id = ? AND status = ?
Query Parameters: {{$json.customerId}}, 'pending'
Use Cases
- E-commerce databases
- WordPress integration
- Legacy system integration
- Data warehousing
- Reporting
Pro Tips
- Use ? placeholders for parameters
- Connection pooling for performance
- SSL certificates for security
- Handle NULL values explicitly
- Timezone configuration matters
43. MongoDB Node
The MongoDB node connects to MongoDB databases for document operations. Insert, find, update, and aggregate documents in collections.
Parameters
- Operation: Find, Insert, Update, Replace, Delete, Aggregate
- Collection: Target collection name
- Query (JSON): MongoDB query filter
- Update (JSON): Update operations
- Options: Projection, Sort, Limit
- Pipeline: Aggregation pipeline stages
Credentials
MongoDB connection credentials (connection string)
Example
Find documents with filter:
Operation: Find
Collection: products
Query: { 'category': '{{$json.category}}', 'price': { '$lte': 100 } }
Limit: 50
Sort: { 'createdAt': -1 }
Use Cases
- Document storage
- Real-time data
- IoT data collection
- Content management
- Analytics aggregation
Pro Tips
- Use MongoDB query syntax ($ operators)
- Aggregation for complex transformations
- Indexes improve query performance
- ObjectId handling may need conversion
- Connection string includes auth
44. Redis Node
The Redis node connects to Redis for key-value operations, caching, and pub/sub messaging. Fast in-memory data store for caching and session management.
Parameters
- Operation: Get, Set, Delete, Keys, Push, Pop, Info, Publish, Increment
- Key: Redis key name
- Value: Value to store
- Key Type: String, Hash, List, Set
- Expire: TTL in seconds
- Options: Channel for pub/sub
Credentials
Redis connection credentials (host, port, password)
Example
Cache API response:
Operation: Set
Key: api_cache:{{$json.endpoint}}
Value: {{JSON.stringify($json.data)}}
Expire: 3600
Use Cases
- Response caching
- Session storage
- Rate limiting counters
- Pub/sub messaging
- Leaderboards
Pro Tips
- Set TTL to prevent memory issues
- Use namespaced keys (app:type:id)
- JSON serialize complex values
- Hash type for object-like data
- Lists for queues
45. AWS S3 Node
The AWS S3 node integrates with Amazon S3 for object storage operations. Upload, download, list, and manage files in S3 buckets.
Parameters
- Resource: Bucket, File, Folder
- Operation: Create, Delete, Get Many, Upload, Download, Copy, Move
- Bucket Name: S3 bucket name
- File Name: Object key
- Binary Property: For file uploads
- Options: ACL, Content Type, Tags
Credentials
AWS credentials (Access Key ID and Secret Access Key)
Example
Upload file to S3:
Operation: Upload
Bucket: my-bucket
File Name: uploads/{{$json.fileName}}
Binary Property: data
ACL: public-read
Use Cases
- File backup
- Static asset hosting
- Data archival
- File distribution
- Document storage
Pro Tips
- Use proper ACL for security
- Content-Type affects browser behavior
- Presigned URLs for temporary access
- Versioning for file history
- Lifecycle rules for cost management
46. Google Drive Node
The Google Drive node manages files and folders in Google Drive. Upload, download, share, and organize files programmatically.
Parameters
- Resource: File, Folder, Shared Drive
- Operation: Upload, Download, Copy, Delete, List, Share, Move
- File/Folder ID: Google Drive file ID
- Name: File/folder name
- Parents: Parent folder IDs
- Binary Property: For uploads
Credentials
Google OAuth2 credentials
Example
Upload and share report:
1. Upload: Binary data, Name = report-{{$now.format('YYYY-MM-DD')}}.pdf
2. Share: File ID = {{$json.id}}, Email = {{$json.recipientEmail}}, Role = reader
Use Cases
- Automated backups
- Report generation
- File sharing workflows
- Document organization
- Collaborative editing
Pro Tips
- File ID is in the sharing URL
- Use folders for organization
- Sharing permissions: reader, writer, owner
- Binary property for file content
- MIME types matter for Google Docs
47. Dropbox Node
The Dropbox node integrates with Dropbox for file storage operations. Upload, download, and manage files in Dropbox accounts.
Parameters
- Resource: File, Folder, Search
- Operation: Upload, Download, Copy, Delete, Move, List, Get Metadata
- Path: Dropbox path (/folder/file.txt)
- Binary Property: For file uploads
- Options: Autorename, Mode
Credentials
Dropbox OAuth2 credentials
Example
Backup to Dropbox:
Operation: Upload
Path: /backups/data-{{$now.format('YYYY-MM-DD')}}.json
Binary Property: data
Use Cases
- File backups
- Document sharing
- Media storage
- Sync workflows
- Archive management
Pro Tips
- Paths start with / (root)
- Autorename handles conflicts
- Use shared links for public access
- Batch operations for efficiency
- Webhooks for file changes
48. FTP Node
The FTP node connects to FTP/SFTP servers for file transfer operations. Upload, download, list, and manage files on remote servers.
Parameters
- Operation: Upload, Download, Delete, Rename, List
- Path: Remote file/directory path
- Binary Property: For file transfers
- Protocol: FTP or SFTP
- Options: Permissions, Recursive
Credentials
FTP/SFTP credentials (host, port, user, password/key)
Example
Download latest file:
Operation: List
Path: /incoming
→ Filter most recent
→ Download: path = {{$json.path}}
Use Cases
- Legacy system integration
- Partner file exchange
- Server backup
- Batch file processing
- Data import/export
Pro Tips
- SFTP is more secure than FTP
- Use SSH keys when possible
- Check file permissions
- Handle large files with care
- Passive mode may be required
49. Read/Write Files from Disk Node
The Read/Write Files from Disk node handles local file operations on the n8n server. Read, write, and append to files in the local filesystem.
Parameters
- Operation: Read, Write
- File Path: Full path to file
- Binary Property: For binary files
- Options: File Encoding, Append
Example
Write log file:
Operation: Write
File Path: /data/logs/process-{{$now.format('YYYY-MM-DD')}}.log
Text: {{$now}} - {{$json.message}}\n
Append: true
Use Cases
- Log file creation
- Local file processing
- Configuration management
- Data export
- Temporary file handling
Pro Tips
- Self-hosted only (not cloud)
- Check file permissions
- Use absolute paths
- Append mode for logs
- Clean up temporary files
50. Spreadsheet File Node
The Spreadsheet File node reads and writes spreadsheet files (Excel, CSV, ODS). Convert between binary spreadsheet data and n8n items.
Parameters
- Operation: Read from File, Write to File
- File Format: CSV, ODS, XLS, XLSX, HTML, RTF
- Binary Property: Input/output binary data
- Options: Header Row, Delimiter, Sheet Name
- Range: Specific cell range to read
Example
Read Excel file: Operation: Read from File Binary Property: data File Format: xlsx Header Row: true Sheet: Sheet1
Use Cases
- CSV import/export
- Excel processing
- Report generation
- Data transformation
- Bulk data import
Pro Tips
- Header row creates named fields
- Use Sheet name for multi-sheet files
- CSV delimiter customizable
- Output is JSON items
- Large files need memory
51. XML Node
The XML node converts between XML and JSON formats. Parse XML data into JSON for easier processing, or generate XML from JSON for APIs that require it.
Parameters
- Mode: XML to JSON, JSON to XML
- Property Name: Field containing data
- Options: Attribute prefix, Explicit root, Normalize tags
Example
Parse XML API response: Mode: XML to JSON Property Name: data Options: Explicit Array = false
Use Cases
- SOAP API integration
- Legacy system data
- RSS feed processing
- XML file parsing
- Data interchange
Pro Tips
- Attributes become properties with prefix
- Arrays need explicit handling
- Namespace handling may need config
- Test with sample data first
- Use Code node for complex XML
52. HTML Node
The HTML node extracts data from HTML content using CSS selectors. Perfect for web scraping, parsing email content, and extracting structured data from HTML pages.
Parameters
- Operation: Extract HTML Content, Generate HTML Template
- Source Data: HTML string or binary
- Extraction Values: CSS selector, attribute, return value type
- Options: Trim values, Convert to text
Example
Extract product prices:
Operation: Extract HTML Content
Source: {{$json.html}}
Extractions:
- CSS Selector: .product-price
Attribute: text
Key: price
Use Cases
- Web scraping
- Email content parsing
- Price monitoring
- Content aggregation
- Data extraction
Pro Tips
- Use browser DevTools to find selectors
- Handle dynamic content limitations
- Text vs HTML content options
- Multiple selectors for arrays
- Respect robots.txt
53. Markdown Node
The Markdown node converts between Markdown and HTML formats. Useful for documentation, email templates, and content management workflows.
Parameters
- Mode: Markdown to HTML, HTML to Markdown
- Markdown/HTML: Input content
- Options: GitHub Flavored Markdown, Sanitize
Example
Convert Markdown to HTML email:
Mode: Markdown to HTML
Markdown: # Order Confirmed\n\nYour order **#{{$json.orderId}}** has been confirmed.
Use Cases
- Email formatting
- Documentation generation
- Content conversion
- Blog publishing
- Report creation
Pro Tips
- GFM enables tables and task lists
- Sanitize for user-generated content
- Combine with SendGrid for emails
- Preserve formatting in conversion
- Code blocks need proper escaping
54. Crypto Node
The Crypto node performs cryptographic operations including hashing, HMAC, encryption, and random value generation. Essential for security, verification, and data protection.
Parameters
- Action: Hash, Hmac, Sign, Generate
- Type: MD5, SHA1, SHA256, SHA384, SHA512
- Value: Input data
- Property Name: Field to process
- Encoding: hex, base64, binary
- Secret: For HMAC/signing
Example
Verify webhook signature:
Action: Hmac
Type: SHA256
Value: {{$json.body}}
Secret: {{$env.WEBHOOK_SECRET}}
Encoding: hex
→ Compare with received signature
Use Cases
- Webhook signature verification
- Password hashing
- API request signing
- Data integrity checks
- Token generation
Pro Tips
- SHA256 for most modern uses
- Use secrets for HMAC
- Compare hashes securely
- Base64 for compact output
- Generate UUIDs for IDs
55. Date & Time Node
The Date & Time node manipulates date and time values. Format dates, add/subtract time, calculate differences, and convert between timezones.
Parameters
- Operation: Format Date, Add/Subtract Time, Calculate, Round Date, Get Time Between Dates
- Date: Input date value
- Format: Output format string
- Value: Amount to add/subtract
- Unit: Years, Months, Days, Hours, Minutes, Seconds
- Timezone: Target timezone
Example
Calculate due date:
Operation: Add to Date
Date: {{$now}}
Duration: 7
Unit: days
Format result:
Operation: Format Date
Format: YYYY-MM-DD
Use Cases
- Due date calculations
- Timezone conversions
- Date formatting for APIs
- Age/duration calculations
- Scheduling logic
Pro Tips
- Use ISO format for APIs
- Moment.js format strings
- Handle timezones explicitly
- Calculate business days separately
- Null handling for missing dates
56. OpenAI Node
The OpenAI node integrates with OpenAI's API for GPT models, embeddings, and image generation. Use it for text generation, conversation, code assistance, and content creation.
Parameters
- Resource: Chat, Text, Image, Audio
- Operation: Complete, Message, Create, Transcribe
- Model: gpt-4, gpt-4-turbo, gpt-3.5-turbo, dall-e-3
- Prompt/Messages: Input text or conversation
- Temperature: Creativity (0-2)
- Max Tokens: Response length limit
- System Message: Context/instructions
Credentials
OpenAI API credentials (API Key)
Example
Generate product description:
Resource: Chat
Model: gpt-4-turbo
System: You are a marketing copywriter.
User: Write a compelling 100-word description for: {{$json.productName}}
Temperature: 0.7
Use Cases
- Content generation
- Customer support automation
- Code assistance
- Translation
- Summarization
Pro Tips
- Lower temperature for factual tasks
- Higher temperature for creativity
- Use system message for persona
- Monitor token usage for costs
- Streaming for long responses
57. Anthropic Claude Node
The Anthropic Claude node integrates with Claude AI models for natural language processing. Known for safety, helpfulness, and long context windows.
Parameters
- Model: claude-3-opus, claude-3-sonnet, claude-3-haiku
- Prompt/Messages: Input conversation
- System: System prompt/instructions
- Max Tokens: Maximum response length
- Temperature: Response randomness
- Stop Sequences: Generation stop triggers
Credentials
Anthropic API credentials (API Key)
Example
Analyze customer feedback:
Model: claude-3-sonnet
System: You are a customer insights analyst.
User: Analyze this feedback and identify key themes: {{$json.feedback}}
Use Cases
- Long document analysis
- Complex reasoning tasks
- Content moderation
- Research assistance
- Code review
Pro Tips
- Large context window (200K tokens)
- Good for nuanced analysis
- Use Haiku for speed/cost
- Opus for complex reasoning
- XML tags for structured output
58. Google Gemini Node
The Google Gemini node connects to Google's Gemini AI models. Supports text, code, and multimodal (text + images) capabilities.
Parameters
- Model: gemini-pro, gemini-pro-vision, gemini-ultra
- Messages: Conversation messages
- Temperature: Response variability
- Max Output Tokens: Response length
- Safety Settings: Content filtering
- Options: Top K, Top P
Credentials
Google AI credentials (API Key)
Example
Analyze image and describe:
Model: gemini-pro-vision
Messages: What's in this image? Describe in detail.
Image: {{$binary.data}}
Use Cases
- Multimodal analysis
- Image understanding
- Code generation
- General chat
- Document processing
Pro Tips
- Vision model for images
- Free tier available
- Safety settings configurable
- Good for code tasks
- Use with Google Cloud
59. AI Agent Node
The AI Agent node creates autonomous AI agents that can use tools, make decisions, and complete complex multi-step tasks. Combines LLMs with tool-calling capabilities.
Parameters
- Agent Type: Conversational, OpenAI Functions, ReAct
- Chat Model: Connected LLM node
- Tools: Connected tool nodes
- System Message: Agent instructions
- Max Iterations: Loop limit
- Options: Return intermediate steps, memory
Example
Research agent: Agent Type: ReAct System: You are a research assistant. Use tools to find and summarize information. Tools: Wikipedia, Web Search, Calculator Max Iterations: 10
Use Cases
- Autonomous research
- Complex workflows
- Multi-step reasoning
- Tool orchestration
- Dynamic decision making
Pro Tips
- Connect appropriate tools
- Clear system prompts
- Limit iterations to prevent loops
- Monitor for hallucinations
- Test with simple tasks first
60. Basic LLM Chain Node
The Basic LLM Chain node creates a simple chain that takes input, processes it through an LLM, and returns output. The foundation for AI workflows in n8n.
Parameters
- Prompt: Text prompt with optional variables
- Chat Model: Connected LLM model
- Output Parser: Structure the output
- Options: Prompt variables
Example
Categorize support tickets:
Prompt: Categorize this support ticket into one of: billing, technical, account, other.\n\nTicket: {{$json.message}}\n\nCategory:
Model: GPT-4
Output: Structured parser for category
Use Cases
- Text classification
- Content generation
- Summarization
- Translation
- Simple AI tasks
Pro Tips
- Use variables in prompts
- Connect output parsers for structure
- Chain multiple for complex flows
- Simple and efficient
- Good starting point for AI
61. Retrieval QA Chain Node
The Retrieval QA Chain node implements RAG (Retrieval-Augmented Generation) for answering questions based on your documents. Combines vector search with LLM generation.
Parameters
- Chat Model: Connected LLM
- Retriever: Connected vector store retriever
- Question: User query
- Return Source Documents: Include retrieved context
- Options: Chain type (stuff, map_reduce, refine)
Example
Document Q&A:
Question: {{$json.question}}
Retriever: Pinecone vector store
Model: GPT-4
Return Source: true
Use Cases
- Document search
- Knowledge base Q&A
- Customer support
- Research assistance
- Internal wiki search
Pro Tips
- Quality embeddings matter
- Chunk documents appropriately
- Return sources for verification
- Use map_reduce for many docs
- Pre-process documents
62. Text Splitter Node
The Text Splitter node breaks large documents into smaller chunks for embedding and retrieval. Essential for RAG systems where documents exceed context limits.
Parameters
- Chunk Size: Characters per chunk
- Chunk Overlap: Characters shared between chunks
- Separator: Split character/string
- Keep Separator: Include in chunks
- Options: Recursive, Token-based
Example
Chunk PDF for embedding: Chunk Size: 1000 Chunk Overlap: 200 Separator: \n\n (paragraphs)
Use Cases
- Document preparation
- RAG preprocessing
- Long text handling
- Embedding preparation
- Context management
Pro Tips
- Overlap preserves context
- Match chunk size to model
- Semantic splitting preferred
- Test chunk quality
- Token-based for accuracy
63. Embeddings Node
The Embeddings node converts text into vector representations using embedding models. Essential for semantic search, similarity matching, and RAG systems.
Parameters
- Model: text-embedding-3-small, text-embedding-3-large, text-embedding-ada-002
- Options: Dimensions, Batch size
Example
Create embeddings for documents:
Model: text-embedding-3-small
Input: {{$json.text}}
→ Store in vector database
Use Cases
- Document indexing
- Semantic search
- Similarity matching
- Clustering
- Recommendation systems
Pro Tips
- Smaller models are cost-effective
- Dimensions affect quality/cost
- Batch for efficiency
- Same model for query/docs
- Cache embeddings
64. Vector Store Node (Pinecone)
The Pinecone Vector Store node connects to Pinecone for storing and querying vector embeddings. Managed vector database for production RAG systems.
Parameters
- Mode: Insert, Get Many (Query), Retrieve (for chain)
- Pinecone Index: Index name
- Pinecone Namespace: Optional namespace
- Top K: Number of results
- Options: Metadata filter
Credentials
Pinecone API credentials
Example
Query similar documents:
Mode: Get Many
Index: knowledge-base
Query: {{$json.question}}
Top K: 5
Use Cases
- Document retrieval
- Semantic search
- Knowledge bases
- Recommendation systems
- RAG applications
Pro Tips
- Create index beforehand
- Namespace for organization
- Metadata for filtering
- Pod vs serverless pricing
- Batch upserts
65. Memory Buffer Node
The Memory Buffer node maintains conversation history for chat applications. Enables context-aware responses by tracking previous messages.
Parameters
- Session ID: Unique conversation identifier
- Context Window Length: Messages to remember
- Session ID Key: Field for session ID
Example
Chatbot with memory:
Session ID: {{$json.userId}}
Window Length: 10
→ Connect to AI Agent/Chain
Use Cases
- Chatbots
- Customer support
- Conversational AI
- Multi-turn dialogues
- Context retention
Pro Tips
- Unique session IDs per user
- Limit window for performance
- Clear memory when needed
- Combine with external storage
- Token limits apply
66. Output Parser Node
The Output Parser node structures LLM responses into specific formats like JSON, lists, or custom schemas. Ensures consistent, parseable AI outputs.
Parameters
- Type: Structured, JSON, List, Auto-fix
- Schema: JSON Schema definition
- Format Instructions: Added to prompt
- Options: Fix errors, Retry
Example
Parse product details:
Type: Structured
Schema: { name: string, price: number, description: string }
→ LLM outputs valid JSON
Use Cases
- Structured extraction
- API response formatting
- Data normalization
- Form filling
- Consistent outputs
Pro Tips
- Define clear schemas
- Use auto-fix for robustness
- Test edge cases
- Simpler schemas work better
- Validate outputs
67. Summarization Chain Node
The Summarization Chain node condenses long documents into summaries. Supports different strategies for handling documents of various lengths.
Parameters
- Type: Stuff, Map Reduce, Refine
- Chat Model: Connected LLM
- Document: Text to summarize
- Options: Combine prompt, Summary prompt
Example
Summarize meeting transcript:
Type: Map Reduce
Document: {{$json.transcript}}
Model: GPT-4
Output: Executive summary with key decisions
Use Cases
- Meeting summaries
- Article condensation
- Report digests
- Email threads
- Document processing
Pro Tips
- Stuff for short docs
- Map Reduce for long docs
- Refine for incremental improvement
- Custom prompts for focus
- Pre-split very long docs
68. Sentiment Analysis Tool
The Sentiment Analysis tool analyzes text to determine emotional tone (positive, negative, neutral). Can be used standalone or as a tool for AI agents.
Parameters
- Text: Input text to analyze
- Options: Detailed analysis, Score
Example
Analyze customer review:
Text: {{$json.review}}
Output: { sentiment: 'positive', score: 0.85, confidence: 0.92 }
Use Cases
- Customer feedback analysis
- Social media monitoring
- Review classification
- Support ticket routing
- Brand monitoring
Pro Tips
- Use with IF node for routing
- Aggregate for trends
- Consider context/sarcasm limits
- Combine with categorization
- Track sentiment over time
69. Wikipedia Tool
The Wikipedia tool allows AI agents to search and retrieve information from Wikipedia. Provides reliable, encyclopedic knowledge for research tasks.
Parameters
- Query: Search term
- Top K Results: Number of results
- Options: Language, Summary only
Example
Agent uses Wikipedia: Query: Albert Einstein contributions to physics Top K: 3 → Returns Wikipedia summaries
Use Cases
- Research assistance
- Fact verification
- Knowledge augmentation
- Educational content
- Context provision
Pro Tips
- Good for factual queries
- Use as agent tool
- Verify for recent events
- Combine with other sources
- Summary mode is faster
70. Calculator Tool
The Calculator tool enables AI agents to perform mathematical calculations. Overcomes LLM limitations with numerical operations.
Parameters
- Expression: Mathematical expression to evaluate
Example
Agent uses Calculator: Expression: (150 * 12) + (75 * 0.15) → Returns: 1811.25
Use Cases
- Financial calculations
- Unit conversions
- Statistical analysis
- Pricing calculations
- Math problem solving
Pro Tips
- Agents auto-detect math needs
- Standard math operators
- Supports complex expressions
- Precise vs LLM estimation
- Good for financial workflows
71. Code Interpreter Tool
The Code Interpreter tool allows AI agents to write and execute code. Enables data analysis, file manipulation, and complex computations within AI workflows.
Parameters
- Language: Python, JavaScript
- Sandbox: Execution environment
- Timeout: Execution time limit
- Options: Output format
Example
Agent analyzes data: Input: CSV data Action: Agent writes Python to analyze, create charts Output: Analysis results and visualizations
Use Cases
- Data analysis
- Report generation
- File processing
- Complex calculations
- Custom transformations
Pro Tips
- Sandboxed execution
- Monitor for security
- Set appropriate timeouts
- Test code outputs
- Combine with file operations
72. Web Search Tool
The Web Search tool enables AI agents to search the internet for current information. Overcomes LLM knowledge cutoff limitations.
Parameters
- Query: Search query
- Engine: google, bing, etc.
- Location: Geographic location
- Number of Results: Results to return
Credentials
SerpAPI credentials
Example
Agent researches topic: Query: latest AI developments 2024 → Returns current search results
Use Cases
- Current events research
- Market research
- Competitive analysis
- News aggregation
- Fact checking
Pro Tips
- Rate limits apply
- Verify search results
- Use specific queries
- Combine with summarization
- Consider SerpAPI costs
73. Custom Tool Node
The Custom Tool (Workflow Tool) node allows AI agents to call other n8n workflows as tools. Enables complex, custom operations within AI agent workflows.
Parameters
- Name: Tool name for agent
- Description: What the tool does (for agent)
- Workflow: Target workflow to execute
- Input Schema: Expected input parameters
Example
Custom database lookup tool:
Name: CustomerLookup
Description: Retrieves customer information by email
Workflow: customer-lookup-workflow
Input: { email: string }
Use Cases
- Database queries
- API integrations
- Custom business logic
- External service calls
- Complex operations
Pro Tips
- Clear tool descriptions for agent
- Define input schema precisely
- Sub-workflow needs trigger
- Return structured data
- Test workflow independently
74. Ollama Node
The Ollama node connects to local Ollama instances for running open-source LLMs. Enables private, cost-free AI with models like Llama, Mistral, and CodeLlama.
Parameters
- Base URL: Ollama server URL
- Model: llama2, mistral, codellama, etc.
- Temperature: Response randomness
- Options: Top K, Top P, Context length
Credentials
Ollama configuration (base URL)
Example
Local code assistant:
Model: codellama
Prompt: Explain this Python code: {{$json.code}}
Temperature: 0.3
Use Cases
- Private/local AI
- Cost-free inference
- Specialized models
- Offline operation
- Data privacy
Pro Tips
- Self-hosted only
- GPU recommended
- Pull models first
- Lower temps for code
- Context size varies by model
75. Hugging Face Node
The Hugging Face node connects to Hugging Face Inference API for accessing thousands of open-source models. Great for specialized tasks like translation, summarization, and image analysis.
Parameters
- Model: Model ID from Hugging Face Hub
- Task: Text Generation, Summarization, Translation, etc.
- Options: Model-specific parameters
- Endpoint: Inference Endpoint URL (optional)
Credentials
Hugging Face API Token
Example
Translation with mBART:
Model: facebook/mbart-large-50-many-to-many-mmt
Task: Translation
Input: {{$json.text}}
Source Language: English
Target Language: French
Use Cases
- Specialized NLP tasks
- Translation
- Summarization
- Classification
- Open-source models
Pro Tips
- Free tier has rate limits
- Check model requirements
- Inference Endpoints for production
- Model warm-up time
- Thousands of models available
76. Error Trigger Node
The Error Trigger node starts a workflow when another workflow encounters an error. Essential for error handling, alerting, and recovery automation.
Parameters
- No configuration needed - automatically captures workflow errors
- Receives: Workflow ID, Execution ID, Error message, Node name
Example
Error notification workflow: Error Trigger → Parse error details → Send Slack alert with workflow name and error message
Use Cases
- Error alerting
- Failure logging
- Automatic recovery
- Error analytics
- On-call notifications
Pro Tips
- Create dedicated error workflow
- Include workflow ID in alerts
- Log to database for analysis
- Implement retry logic
- Don't create error loops
77. Execute Command Node
The Execute Command node runs shell commands on the n8n server. Enables system operations, script execution, and tool integration. Use with caution for security.
Parameters
- Command: Shell command to execute
- Execute Once: Run once or per item
- Options: Timeout, Working directory
Example
Generate PDF report:
Command: wkhtmltopdf {{$json.htmlPath}} /tmp/report-{{$json.id}}.pdf
Timeout: 30000
Use Cases
- PDF generation
- Image processing
- Script execution
- System administration
- Tool integration
Pro Tips
- Security risk - validate inputs
- Self-hosted only
- Set appropriate timeouts
- Handle stdout/stderr
- Use absolute paths
78. SSH Node
The SSH node connects to remote servers via SSH for command execution and file transfer. Enables server management and remote operations.
Parameters
- Operation: Execute Command, Download File, Upload File
- Command: Remote command to run
- Resource: Commands or Files
- Path: Remote file path
- Binary Property: For file transfers
Credentials
SSH credentials (host, user, password/key)
Example
Deploy update to server: Operation: Execute Command Command: cd /app && git pull && pm2 restart all
Use Cases
- Server deployment
- Log retrieval
- Database backups
- System monitoring
- Remote administration
Pro Tips
- Use SSH keys over passwords
- Set command timeouts
- Handle connection failures
- Secure credential storage
- Test in development first
79. GraphQL Node
The GraphQL node executes GraphQL queries and mutations against any GraphQL API. More flexible than REST for complex data requirements.
Parameters
- Endpoint: GraphQL API URL
- Query: GraphQL query or mutation
- Variables: Query variables (JSON)
- Request Format: JSON or GET
- Response Format: Full or Data only
Credentials
HTTP Authentication or custom headers
Example
Query GitHub GraphQL:
Endpoint: https://api.github.com/graphql
Query: query { viewer { login repositories(first: 5) { nodes { name } } } }
Headers: Authorization: Bearer {{$env.GITHUB_TOKEN}}
Use Cases
- GitHub API v4
- Shopify Storefront
- Hasura queries
- Custom GraphQL APIs
- Complex data fetching
Pro Tips
- Use variables for dynamic values
- Introspection for schema discovery
- Handle errors in response
- Batching reduces requests
- Query complexity limits
80. MQTT Trigger Node
The MQTT Trigger node subscribes to MQTT topics and triggers workflows when messages arrive. Essential for IoT, real-time messaging, and event-driven architectures.
Parameters
- Topics: MQTT topics to subscribe (wildcards supported)
- Options: QoS, Only Message, JSON Parse Message
Credentials
MQTT broker credentials (host, port, username, password)
Example
IoT sensor data: Topics: sensors/+/temperature, sensors/+/humidity QoS: 1 → Process sensor readings
Use Cases
- IoT data collection
- Real-time messaging
- Home automation
- Industrial monitoring
- Event streaming
Pro Tips
- Use + for single-level wildcard
- Use # for multi-level wildcard
- QoS affects delivery guarantee
- Handle connection drops
- Parse JSON messages
81. RabbitMQ Trigger Node
The RabbitMQ Trigger node consumes messages from RabbitMQ queues. Perfect for message-driven architectures and background job processing.
Parameters
- Queue: Queue name to consume from
- Options: Auto-acknowledge, Parallel Processing, JSON Parse
- Acknowledge Mode: Automatic or Manual
Credentials
RabbitMQ credentials (host, port, username, password, vhost)
Example
Process background jobs: Queue: email-jobs Acknowledge: After successful processing Parallel: 5 concurrent messages
Use Cases
- Background job processing
- Event sourcing
- Microservices communication
- Task queues
- Decoupled systems
Pro Tips
- Handle message acknowledgment
- Dead letter queues for failures
- Parallel processing for throughput
- Durable queues for reliability
- Monitor queue depth
82. Kafka Trigger Node
The Kafka Trigger node consumes messages from Apache Kafka topics. Designed for high-throughput, distributed event streaming scenarios.
Parameters
- Topic: Kafka topic to consume
- Group ID: Consumer group identifier
- From Beginning: Start from earliest or latest
- Options: JSON Parse, Parallel Processing
Credentials
Kafka credentials (brokers, SSL, SASL)
Example
Event streaming: Topic: user-events Group ID: n8n-processor From Beginning: false → Process user activity events
Use Cases
- Event streaming
- Log aggregation
- Real-time analytics
- Data pipelines
- Microservices events
Pro Tips
- Consumer groups enable scaling
- Partition assignment matters
- Handle offset commits
- Monitor consumer lag
- Dead letter topic for failures
83. AWS SNS Trigger Node
The AWS SNS Trigger node receives notifications from Amazon SNS topics. Enables AWS service event handling and pub/sub patterns.
Parameters
- Topic ARN: SNS topic ARN
- Options: Verify signature, subscription confirmation
Credentials
AWS credentials
Example
S3 event notification: Topic: arn:aws:sns:us-east-1:123456789:s3-events → Trigger on file uploads
Use Cases
- S3 event processing
- CloudWatch alarms
- Lambda triggers
- AWS service events
- Application notifications
Pro Tips
- Confirm subscription first
- Verify SNS signatures
- Handle different message types
- Parse SNS message body
- Consider SQS for reliability
84. AWS Lambda Node
The AWS Lambda node invokes AWS Lambda functions. Execute serverless functions for custom processing, integrations, and AWS service access.
Parameters
- Function Name: Lambda function name or ARN
- Qualifier: Version or alias
- Invocation Type: Request-Response, Event, DryRun
- Payload: JSON input to function
Credentials
AWS credentials with Lambda permissions
Example
Invoke image processor:
Function: image-thumbnail-generator
Payload: { 's3Key': '{{$json.key}}', 'bucket': '{{$json.bucket}}' }
Invocation: Request-Response
Use Cases
- Custom processing
- AWS service integration
- Serverless backends
- Image/video processing
- Data transformation
Pro Tips
- Request-Response for sync
- Event for async/fire-forget
- Handle Lambda timeouts
- Check IAM permissions
- Parse response payloads
85. Google Cloud Functions Node
The Google Cloud Functions node invokes GCP Cloud Functions. Execute serverless functions for custom logic and Google Cloud integrations.
Parameters
- Project ID: GCP project
- Region: Function region
- Function Name: Cloud Function name
- Trigger Type: HTTP, PubSub, etc.
- Body: Request body
Credentials
Google Cloud Service Account
Example
Invoke processing function:
Project: my-project
Region: us-central1
Function: process-document
Body: { 'documentUrl': '{{$json.url}}' }
Use Cases
- Custom processing
- GCP integrations
- Serverless compute
- Event handling
- Data pipelines
Pro Tips
- Check function permissions
- Handle timeouts
- Monitor execution logs
- Use appropriate regions
- Parse function responses
86. Linear Node
The Linear node integrates with Linear for issue tracking and project management. Create issues, update status, and manage workflows.
Parameters
- Resource: Issue, Project, Team, User, Comment
- Operation: Create, Get, Get Many, Update, Delete
- Team: Target team
- Title: Issue title
- Description: Issue description (Markdown)
- State: Issue state/status
- Priority: Issue priority
Credentials
Linear API Key
Example
Create bug from alert:
Resource: Issue
Operation: Create
Team: Engineering
Title: [Alert] {{$json.alertName}}
Description: {{$json.details}}
Priority: Urgent
Use Cases
- Issue automation
- Sprint planning
- Bug tracking
- Feature requests
- Status syncing
Pro Tips
- Use team ID for operations
- Markdown in descriptions
- Webhooks for triggers
- Cycle/Sprint integration
- Labels and assignees
87. Asana Node
The Asana node connects to Asana for task and project management. Create tasks, update projects, and automate workflows.
Parameters
- Resource: Task, Project, Section, User, Tag, Subtask
- Operation: Create, Get, Get Many, Update, Delete, Move
- Workspace: Asana workspace
- Project: Target project
- Name: Task name
- Notes: Task description
Credentials
Asana OAuth2 or Personal Access Token
Example
Create task from form:
Resource: Task
Operation: Create
Project: {{$json.projectId}}
Name: {{$json.taskTitle}}
Assignee: {{$json.assigneeEmail}}
Due Date: {{$json.dueDate}}
Use Cases
- Task automation
- Project tracking
- Sprint management
- Cross-team coordination
- Deadline management
Pro Tips
- Use GIDs for resources
- Sections organize tasks
- Rich text in notes
- Custom fields available
- Webhooks for events
88. ClickUp Node
The ClickUp node integrates with ClickUp for task and project management. Manage tasks, lists, and spaces programmatically.
Parameters
- Resource: Task, List, Folder, Space, Team, Goal, Checklist
- Operation: Create, Get, Get Many, Update, Delete
- Team: ClickUp team
- Space: Target space
- List: Target list
- Name: Task name
- Description: Task description
Credentials
ClickUp API Key or OAuth2
Example
Create task with checklist:
Resource: Task
Operation: Create
List: {{$json.listId}}
Name: Review: {{$json.documentTitle}}
Priority: High
Due Date: {{$json.deadline}}
Use Cases
- Task automation
- Project management
- Sprint planning
- Time tracking
- Goal tracking
Pro Tips
- Hierarchy: Team > Space > Folder > List > Task
- Custom fields for metadata
- Webhooks for events
- Time tracking available
- Relationships between tasks
89. Monday.com Node
The Monday.com node connects to Monday.com for work management. Create items, update columns, and manage boards.
Parameters
- Resource: Board, Board Column, Board Group, Board Item
- Operation: Create, Get, Get Many, Get By, Delete, Update
- Board ID: Target board
- Group ID: Target group
- Item Name: Item name
- Column Values: Column data
Credentials
Monday.com API Token
Example
Create item from lead:
Resource: Board Item
Operation: Create
Board: CRM Board
Group: New Leads
Name: {{$json.companyName}}
Column Values: { 'email': '{{$json.email}}', 'phone': '{{$json.phone}}' }
Use Cases
- CRM automation
- Project tracking
- Sales pipelines
- Marketing workflows
- Team coordination
Pro Tips
- Column IDs vs names
- Column values format varies
- Use board templates
- Automations complement n8n
- GraphQL API for complex queries
90. Todoist Node
The Todoist node integrates with Todoist for personal and team task management. Create tasks, manage projects, and automate to-do workflows.
Parameters
- Resource: Task, Project, Section, Comment, Label
- Operation: Create, Get, Get Many, Update, Delete, Close, Reopen
- Project: Target project
- Content: Task description
- Priority: Task priority (1-4)
- Due: Due date/time
Credentials
Todoist API Token
Example
Add daily task: Resource: Task Operation: Create Project: Work Content: Review inbox and respond to emails Priority: 2 Due: today
Use Cases
- Task automation
- Daily routines
- Email to task
- Project management
- Personal productivity
Pro Tips
- Natural language dates
- Labels for categorization
- Sections organize tasks
- Recurring dates supported
- Priority 1 = highest
91. Calendly Node
The Calendly node integrates with Calendly for scheduling automation. Retrieve events, manage invitees, and automate meeting workflows.
Parameters
- Resource: Event, Invitee
- Operation: Get, Get Many
- Event URI: Specific event
- User: Calendar owner
- Filters: Date range, status
Credentials
Calendly API Token
Example
New booking workflow: Calendly Webhook (booking created) → Get event details → Create CRM contact → Send confirmation email
Use Cases
- Meeting automation
- Lead capture
- CRM integration
- Calendar sync
- Onboarding workflows
Pro Tips
- Use webhooks for triggers
- Parse event for details
- Sync with CRM
- Handle cancellations
- Time zone awareness
92. Google Calendar Node
The Google Calendar node manages events in Google Calendar. Create, update, and query calendar events programmatically.
Parameters
- Resource: Event, Calendar
- Operation: Create, Get, Get Many, Update, Delete
- Calendar: Target calendar
- Title: Event title
- Start: Start date/time
- End: End date/time
- Attendees: Invite emails
- Options: Location, Description, Recurrence
Credentials
Google OAuth2 credentials
Example
Schedule meeting:
Operation: Create
Calendar: primary
Title: Team Standup
Start: {{$json.meetingTime}}
Duration: 30 minutes
Attendees: team@company.com
Use Cases
- Meeting scheduling
- Appointment booking
- Calendar sync
- Event reminders
- Resource booking
Pro Tips
- 'primary' for default calendar
- RFC3339 date format
- Recurring with RRULE
- Conference links available
- Free/busy queries
93. Webflow Node
The Webflow node integrates with Webflow CMS for content management. Create, update, and manage CMS items programmatically.
Parameters
- Resource: Item, Site, Collection
- Operation: Create, Get, Get Many, Update, Delete, Publish
- Site: Webflow site
- Collection: CMS collection
- Fields: Item field values
- Options: Live, Draft, Archived
Credentials
Webflow API Token
Example
Publish blog post:
Resource: Item
Operation: Create
Collection: Blog Posts
Fields: title = {{$json.title}}, content = {{$json.content}}, publish-date = {{$now}}
Live: true
Use Cases
- CMS automation
- Content publishing
- Dynamic collections
- E-commerce sync
- Site updates
Pro Tips
- Use collection field IDs
- Publish after changes
- Handle rate limits
- Image URLs for media
- Staging vs production
94. WordPress Node
The WordPress node manages WordPress sites via REST API. Create posts, manage pages, handle media, and automate content workflows.
Parameters
- Resource: Post, Page, User, Media
- Operation: Create, Get, Get Many, Update, Delete
- Title: Post/page title
- Content: HTML content
- Status: draft, publish, private
- Categories: Post categories
- Tags: Post tags
Credentials
WordPress credentials (Application Password or OAuth)
Example
Auto-publish article:
Resource: Post
Operation: Create
Title: {{$json.title}}
Content: {{$json.htmlContent}}
Status: publish
Categories: [{{$json.categoryId}}]
Use Cases
- Content publishing
- Blog automation
- Media uploads
- Multi-site management
- Content syndication
Pro Tips
- Application passwords recommended
- HTML in content field
- Featured image via media
- Category/tag IDs required
- Custom fields with ACF
95. Mailchimp Node
The Mailchimp node integrates with Mailchimp for email marketing. Manage subscribers, lists, campaigns, and automations.
Parameters
- Resource: Member, List/Audience, Campaign, Tag
- Operation: Create, Get, Get Many, Update, Delete, Upsert
- List: Target audience
- Email: Subscriber email
- Status: subscribed, pending, unsubscribed
- Merge Fields: Custom field values
Credentials
Mailchimp API Key
Example
Add subscriber:
Resource: Member
Operation: Upsert
List: {{$json.listId}}
Email: {{$json.email}}
Status: subscribed
Merge Fields: FNAME = {{$json.firstName}}, LNAME = {{$json.lastName}}
Use Cases
- Subscriber management
- List building
- Campaign triggers
- Tag management
- Sync with CRM
Pro Tips
- Upsert prevents duplicates
- Double opt-in recommended
- Merge field names uppercase
- Webhooks for events
- Segment for targeting
96. ConvertKit Node
The ConvertKit node integrates with ConvertKit for creator email marketing. Manage subscribers, tags, sequences, and broadcasts.
Parameters
- Resource: Subscriber, Tag, Form, Sequence, Broadcast
- Operation: Add, Get, Get Many, Remove, Update
- Email: Subscriber email
- First Name: Subscriber name
- Tags: Tag IDs to add/remove
- Custom Fields: Additional data
Credentials
ConvertKit API Key
Example
Add lead to sequence:
Resource: Subscriber
Operation: Add to Sequence
Email: {{$json.email}}
First Name: {{$json.firstName}}
Sequence: Welcome Sequence
Use Cases
- Lead nurturing
- Course delivery
- Newsletter automation
- Subscriber tagging
- Landing page follow-up
Pro Tips
- Tags for segmentation
- Sequences for automation
- Custom fields for data
- Forms for opt-in tracking
- Creator-focused platform
97. Cron Node (Legacy)
The Cron node (legacy) triggers workflows on complex time-based schedules using cron expressions. Now superseded by Schedule Trigger but still functional.
Parameters
- Mode: Every X, Cron Expression, Custom
- Trigger Times: Multiple schedules
- Cron Expression: Standard cron format
Example
Complex schedule: - Weekdays at 9am: 0 9 * * 1-5 - First Monday monthly: 0 10 1-7 * 1 - Every 15 minutes: */15 * * * *
Use Cases
- Complex schedules
- Business hours only
- Monthly reports
- Maintenance windows
- Multi-schedule workflows
Pro Tips
- Use Schedule Trigger for new workflows
- Crontab.guru for validation
- Server timezone applies
- Multiple schedules per node
- Test with shorter intervals first
98. Function Node (Legacy)
The Function node (legacy) runs JavaScript code for data transformation. Superseded by Code node but still available for compatibility.
Parameters
- Function Code: JavaScript code
- Available: items, $item(), $node, $workflow
Example
Transform items:
return items.map(item => {
return {
json: {
fullName: item.json.first + ' ' + item.json.last,
email: item.json.email.toLowerCase()
}
};
});
Use Cases
- Legacy workflow support
- Simple transformations
- Custom logic
- Data formatting
- Calculations
Pro Tips
- Use Code node for new work
- Return array of items
- items[0].json for data access
- Error handling important
- No async/await in legacy
99. Sticky Note Node
The Sticky Note node adds visual documentation to workflows. Write notes, instructions, and explanations directly on the canvas for team collaboration.
Parameters
- Content: Markdown text
- Color: Note background color
- Height: Note height
- Width: Note width
Example
Document workflow section: ## Data Validation This section validates incoming data: - Checks required fields - Validates email format - Filters duplicates
Use Cases
- Workflow documentation
- Team communication
- Section labels
- Instructions
- Change notes
Pro Tips
- Markdown formatting supported
- Color-code by purpose
- Group related nodes
- Document complex logic
- Update when workflow changes
100. n8n Node
The n8n node provides access to n8n's own API for workflow management. List, get, activate, and manage workflows programmatically.
Parameters
- Resource: Workflow, Execution, Credential, Audit
- Operation: Get, Get Many, Create, Update, Delete, Activate, Deactivate
- Workflow ID: Target workflow
- Filters: Status, tags, dates
Example
Monitor failed executions: Resource: Execution Operation: Get Many Status: error Limit: 10 → Send alerts for failures
Use Cases
- Workflow management
- Execution monitoring
- Automated deployment
- Self-healing workflows
- Admin automation
Pro Tips
- API key required
- Self-hosted for full access
- Monitor execution status
- Backup workflows as JSON
- Automate activation
Key Learning Outcomes
- Understanding n8n's workflow automation architecture
- Building trigger-based automations with webhooks and schedules
- Making HTTP requests and working with REST APIs
- Implementing conditional logic with IF and Switch nodes
- Transforming and manipulating data efficiently
- Connecting to popular apps and services
- Building AI-powered workflows with LLM integration
- Creating reusable sub-workflows and error handling
- Working with databases, files, and cloud storage
- Scaling automations for production use
Who This Tutorial Is For
- Complete beginners wanting to learn workflow automation
- Professionals looking to automate repetitive tasks
- Developers building integrations and automations
- Business owners streamlining operations
- Marketers automating campaigns and workflows
- Data analysts building data pipelines
- DevOps engineers implementing CI/CD automation
- Anyone wanting to leverage no-code/low-code automation
Get Started with n8n
n8n is free to use with their cloud platform or self-hosted option. Start building powerful automations today: