n8n & Automation Glossary

A set of rules that lets two software applications communicate. REST APIs use HTTP endpoints; GraphQL APIs use queries. n8n connects to hundreds of APIs through its nodes and the HTTP Request node.

A secret token used to authenticate API requests. Typically passed as a header (Authorization: Bearer <key>) or query parameter. n8n stores API keys securely as credentials.

A type of access token used in OAuth2 and API authentication. Sent in the Authorization header as 'Bearer <token>'. The most common authentication method for modern REST APIs.

An n8n trigger that executes a workflow on a recurring schedule using cron syntax — e.g., every 15 minutes, daily at 9 AM, first Monday of the month.

An n8n node that lets you write custom JavaScript/Python to manipulate data, make API calls, or implement logic not available in built-in nodes. Full access to workflow data and node modules.

Stored authentication details (API keys, OAuth tokens, usernames/passwords) that n8n nodes use to connect to external services. Credentials are encrypted and managed centrally in the n8n UI.

An automated pipeline that builds, tests, and deploys code changes. n8n workflows can integrate with CI/CD tools (GitHub Actions, GitLab CI) to trigger deployments, run tests, and send notifications on pipeline events.

A containerization platform that packages applications with all dependencies. n8n provides official Docker images — the most common self-hosting deployment method. Easy to run with a single docker-compose command.

The process of converting data from one format or structure to another. In n8n, this happens in Function/Code nodes, using JSONata expressions, or through dedicated transform nodes — mapping API responses into the shape downstream nodes expect.

An n8n node category that connects to SQL databases (PostgreSQL, MySQL, SQLite) and NoSQL stores (MongoDB, Redis). Used to store workflow results, look up reference data, and maintain state between executions.

An n8n node that triggers another n8n workflow (sub-workflow pattern). Good for modular design — keep common logic in one workflow and call it from many others.

A single run of an n8n workflow from trigger to completion. Each execution has an ID, status (success/error/waiting), and detailed log showing input/output at each node — critical for debugging.

A data pipeline pattern: Extract raw data from sources, Transform it into a usable format, Load it into a destination. n8n workflows can implement complete ETL pipelines using HTTP Request, Code, and database nodes.

A specific URL path on a server that accepts API requests. Example: /api/users for listing users or /api/users/42 for a specific user. Every n8n Webhook node exposes a unique endpoint URL.

A configuration value set outside the application (in .env files or the OS) that controls behavior at runtime. n8n uses environment variables for database URLs, encryption keys, API keys, and deployment settings.

The process of encoding data so only authorized parties can access it. n8n encrypts all stored credentials at rest using AES-256. Workflow data in transit is protected by HTTPS/TLS encryption.

An n8n node for writing custom JavaScript that transforms data from previous nodes. Simpler than the Code node — designed for data manipulation rather than full control over workflow execution.

A query language for APIs that lets clients request exactly the data they need — no over-fetching or under-fetching. n8n supports GraphQL through custom HTTP Request nodes with structured queries.

An n8n node that sends HTTP requests (GET, POST, PUT, PATCH, DELETE) to any REST API endpoint. Supports headers, authentication, query parameters, and response parsing — making n8n compatible with any service that has an API.

The foundational protocol of the web. Uses request-response pattern between clients and servers. n8n communicates with all external services over HTTP/HTTPS through its nodes.

An n8n logic node that routes workflow execution based on a condition. Compares data values and sends true results down one path, false results down another — enabling branching logic.

If This Then That — a simple consumer-grade automation tool using if/then applets. Best for individuals connecting smart home devices and social media. Less suitable for business-critical workflows.

A property of an operation where performing it multiple times produces the same result as doing it once. Critical for workflow reliability — e.g., you want duplicate webhook deliveries to create only one invoice, not five.

A lightweight, human-readable data interchange format. Nearly every API returns JSON, and n8n nodes pass JSON objects between each other. Understanding JSON structure is essential for n8n workflow design.

A lightweight query and transformation language for JSON data, deeply integrated into n8n. Used in expression fields to extract, reshape, and compute values from workflow data without writing full JavaScript.

A compact, URL-safe token format used for authentication and information exchange. JWTs contain signed claims about a user or session. n8n can generate and validate JWTs in Code nodes for custom authentication flows.

A development approach combining visual builders with optional custom code. n8n is low-code: most workflows use drag-and-drop nodes, but the Code Node allows custom JavaScript when needed.

An n8n node that combines multiple data streams into one. Supports various merge modes: append, merge by index, merge by key, and wait — useful when you need to gather data from parallel branches.

A visual automation platform with an intuitive drag-and-drop scenario builder. Strong visual design tools and real-time execution viewer. Often compared to n8n for complex multi-step workflows.

Fair-code licensed workflow automation platform that connects apps and services through visual node-based workflows. Supports 400+ integrations, self-hosting, and code-free automation design.

An individual building block in an n8n workflow. Each node performs one specific action: trigger an execution, fetch data from an API, transform data, apply logic, or send output to another service.

A development approach that allows users to build applications and automations through visual interfaces without writing programming code. n8n's visual workflow builder is a no-code automation tool.

An authorization framework that lets applications obtain limited access to user accounts on external services without exposing passwords. n8n supports OAuth2 for many nodes, handling token refresh automatically.

A technique for handling large API result sets by breaking them into pages. n8n's HTTP Request node and many built-in nodes support cursor-based and offset-based pagination to fetch all records automatically.

The actual data carried in an API request or response body, typically in JSON format. In n8n, the payload is what a webhook receives (the POST body) or what an HTTP Request node sends to an API.

A restriction on how many API requests a client can make in a time window (e.g., 100 requests/minute). n8n workflows must handle rate limits with retry logic, batch splitting, and exponential backoff to avoid failures.

Representational State Transfer — the most common API architecture using HTTP methods (GET, POST, PUT, DELETE) on URL endpoints. Stateless, resource-oriented, and the backbone of most web service integrations.

An n8n node that routes data to different output branches based on multiple conditions. Unlike the IF node (binary), Switch handles many possible paths — ideal for categorizing, bucketing, or multi-way routing.

An n8n utility node that breaks large datasets into smaller batches for processing. Prevents API rate limits and timeout errors by sending manageable chunks through downstream nodes.

A protocol where a server pushes real-time updates to clients over a single HTTP connection. n8n supports SSE for streaming AI responses and real-time workflow monitoring.

The standard protocol for sending email. n8n's Email node uses SMTP to send transactional emails, reports, and notifications directly from workflows.

Running n8n on your own server (VPS, Docker, Kubernetes) rather than using n8n Cloud. Provides unlimited workflows, full data control, and fixed hosting costs. Central to FlowForge's cost-saving proposition.

A formal description of data structure — what fields exist, their types, and constraints. JSON Schema and OpenAPI specs define API contracts. Understanding schemas helps n8n users map data between nodes correctly.

The first node in an n8n workflow — it determines what starts a workflow run. Common triggers: Webhook (incoming HTTP request), Cron (scheduled time), or app-specific events like new email or form submission.

The cryptographic protocol that secures HTTPS connections — encrypting data between client and server. All n8n API communications should use HTTPS/TLS, especially when transmitting API keys and sensitive workflow data.

A virtual machine you rent from a cloud provider (Hetzner, DigitalOcean, AWS). The lowest-cost way to self-host n8n — typically $4-6/month for sufficient resources to run dozens of workflows.

A sequence of automated steps (nodes) that execute in order or based on conditions. In n8n, workflows are built visually by connecting nodes representing triggers, actions, and logic.

An n8n trigger that listens for incoming HTTP POST requests on a unique URL. When data hits that URL, the workflow executes. Used for real-time integrations with external services.

The practice of using software to execute repetitive multi-step business processes without human intervention. Examples: invoice generation, lead routing, data syncing between tools, and scheduled reporting.

A user-defined HTTP callback — when an event happens in Service A, it sends an HTTP POST to a URL in Service B. n8n uses webhooks both as triggers (receiving data) and as actions (sending data to external endpoints).

A protocol providing full-duplex (two-way) communication over a single TCP connection. Unlike HTTP's request-response pattern, WebSockets maintain persistent connections — used for real-time chats, live dashboards, and streaming data.

A popular cloud-based SaaS workflow automation platform with 7,000+ app integrations. Priced per-task. Often compared to n8n on cost, self-hosting capability, and complexity ceiling.