Types of n8n Workflows: Triggers, Branches & Sub-Workflows

n8n categorizes workflows by their trigger mechanism, execution logic, and structural role within an automation ecosystem. You can classify any workflow into one of five primary types: manual trigger, schedule trigger, webhook trigger, sub‑workflow, or error workflow. Branching constructs like the IF and Switch nodes add decision logic across all types.

When should you use a manual trigger workflow in n8n?

Use a manual trigger workflow when you need on‑demand execution without an external schedule or event. You click the “Execute Workflow” button in the n8n canvas, and the entire node sequence processes immediately. This type suits data migration scripts, one‑time reports, or prototyping before adding a production trigger. [1]

Once validated, you can switch to an automated schedule trigger or n8n node testing and debugging techniques for further refinement.

How do you set a schedule trigger to run n8n workflows automatically?

A schedule trigger executes workflows at fixed intervals using cron expressions. n8n evaluates the cron syntax, and the workflow starts at the next matching time. Common schedules include “every 5 minutes” */5 * * * *, hourly 0 * * * *, and daily at 8 AM 0 8 * * *. You can also specify a timezone for precise local timing. [2]

Schedule triggers are resource‑efficient because n8n only activates the workflow at the designated moment, avoiding constant polling. For in‑depth cron examples, the official documentation provides a full reference.

What makes webhook triggers different from other n8n workflow types?

Webhook triggers start workflows immediately when an external service sends an HTTP POST request to n8n’s unique webhook URL. This event‑driven mechanism supports real‑time data sync, payment notifications, and form submissions. Unlike schedule triggers, execution occurs only upon an incoming request, reducing latency to near zero. [3]

You can secure webhook URLs with HMAC signatures, Basic Auth, or Header Auth. See the n8n webhook authentication hardening guide for production setups.

How do sub-workflows modularize complex n8n automations?

Sub‑workflows allow one parent workflow to call another, passing data as input and receiving a response. This design pattern isolates reusable logic—like data enrichment or error formatting— into a separate workflow, simplifying maintenance and enabling parallel execution of independent tasks. The parent workflow continues once the sub‑workflow completes. [4]

Sub‑workflows reduce node duplication and centralize updates. They are invoked via the Execute Workflow node. More on modular design patterns in the n8n architecture and scaling guide.

What is an error workflow and how does it handle n8n failures?

An error workflow is a dedicated workflow triggered automatically when another workflow fails. It receives the error message, input data, and execution context. You configure it to send alerts via Slack, log errors to a database, or attempt a retry with exponential backoff. Every production workflow should pair with an error workflow. [5]

Error workflows eliminate silent failures and provide a centralized error‑management layer. Combine them with IF nodes for conditional branching on specific error codes.

How do IF and Switch nodes add branching logic to n8n workflows?

IF nodes evaluate a true/false condition and route data along two separate paths, enabling binary decision‑making. Switch nodes extend this to multiple conditions, routing data to one of several output branches based on a field’s exact value or range. Both nodes insert decision intelligence into any workflow type, from manual triggers to webhooks. [6]