Resources · n8n integration

n8n Execute Workflow Trigger nodeConfigure Execute Workflow Trigger in n8n.

Some workflows are not meant to start on their own. The n8n Execute Workflow Trigger node opens a workflow that another workflow calls, with 0 parameters to fill in and nothing to authenticate. That is how modular, microservice-like automations get built.

Try the Execute Workflow Trigger node on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Execute Workflow Trigger node do?

It is the entry point of a sub-workflow, meaning a workflow built to be called by another one rather than started by hand. Drop this node on a blank canvas and the workflow becomes a named block that answers calls, the way a small service does. It ships with n8n, holds 0 parameters, and version 1 is the only version in the catalog. The nodes placed after it read what the caller sent with an expression such as {{ $json.email }}.

Take a company enrichment routine that three different pipelines need. Built once as a sub-workflow, it starts with this node and runs its HTTP Request call against the API you rely on. The day that API changes its path, one workflow gets edited instead of three.

Long canvases stop being readable fast. When a workflow carries five branches and each branch is worth a dozen nodes, the If node that splits them disappears in the noise. Move each branch into its own sub-workflow and the parent reads in one glance: a condition, a call, a block you can open on its own when it misbehaves.

The same split helps when several pipelines need the same normalization step before they move on. A shared sub-workflow opened by this node applies that step once, the way a Merge node combines branches within a single canvas. Each block stays testable alone, which is what you want on the morning only one of them breaks. You open that sub-workflow, you rerun it with the items it received, and you leave the other pipelines untouched while you work.

There is a price to pay, and it is worth naming. A sub-workflow is an extra execution to open when something goes wrong, and a block whose contract lives in your head: the node exposes 0 parameters, so nothing on screen states what the caller is supposed to send. For a three-node block used once, keep it inline. For anything reused twice or more, or anything you want to run on its own while you debug it, the split pays for itself quickly. n8n training covers that arbitration with real workflows.

Parameters

Execute Workflow Trigger

The Execute Workflow Trigger node has 0 parameters. For each one: the node as you configure it in n8n, what the parameter changes, and our field notes.

Need help

Need help automating Execute Workflow Trigger with n8n?

A person reads every message.

FAQ

Execute Workflow Trigger and n8n, the usual questions

01Is the Execute Workflow Trigger node free in n8n?
Yes. It is a core node, shipped with n8n itself, so there is nothing to install and no extra cost on the n8n side. It behaves the same on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance installed with Docker or npm under the Community Edition and its Sustainable Use license. A workflow built around this node is identical in both cases, which means a sub-workflow prototyped on Cloud moves to a self-hosted instance without being rewritten. What you pay for, if anything, is the hosting and the plan, never this node.
02What do you need to set up before using it?
Nothing, and that is a real argument rather than a gap. This node has no credential and no Authentication selector, so there is no account to connect and no key to store anywhere. It exposes 0 parameters too: its panel is empty, and the only thing left to decide is what comes after it on the canvas. Two practical points remain. The workflow has to be active for the node to listen in production. While you are still editing, a test execution starts a one-off listen, which is enough to check that the items arriving from the caller look the way you expected.
03What are the limits of this node?
The main one follows from the empty panel. With 0 parameters, nothing declares what the calling workflow should send, so the agreement between the two workflows is a convention you maintain yourself, in naming and in documentation. The node is also passive by design: it waits to be called and never calls anything itself, so it cannot be the entry point of a workflow that has to start on a schedule or on an inbound request. Last point, version 1 is the only version in the catalog, which at least means there are no version gaps to reconcile between two instances.
04When do you use the n8n Execute Workflow Trigger node rather than keeping the logic inline?
Use it as soon as the same block of logic is needed by more than one workflow, or as soon as a single workflow has grown past the point where you can read it. Reuse is the strongest signal: one enrichment routine, one notification routine, one cleanup routine, each living in a workflow of its own with this node at the top. Readability is the second one. If a branch is long enough that you scroll past it every time, it belongs in its own workflow. Below that, for three or four nodes used once, inline stays simpler and costs one execution less.
05n8n or Make for modular automations?
It depends on where your data is allowed to live and how you want to pay. Make is a hosted automation platform with no self-hosting option, billed per operation, so the cost follows volume and everything runs on their infrastructure. n8n runs on Cloud or on your own server with Docker or npm, which is what matters when the data crossing a sub-workflow cannot leave your environment. The visual logic differs too, and the honest answer is that both work. Splitting automations into reusable blocks is a habit you can hold either way, so pick on hosting, on data control and on the cost model.
Hack'celeration Lab

Get our weekly integration tips.

No spam. Unsubscribe anytime.

Same platform

Other docs you might need on this stack.

Browse all integrations