Resources · n8n integration

n8n Activation Trigger nodeConfigure Activation Trigger in n8n.

A workflow can react to its own activation. The n8n Activation Trigger node starts an execution when the workflow goes live, when it gets saved while active, or when n8n itself restarts. One parameter, 3 events, nothing to connect. Handy for warm-up routines, go-live notices and post-save checks.

Try the Activation Trigger node on n8nSee the 1 parameters

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the n8n Activation Trigger node actually do?

It watches the workflow itself. Where most triggers listen to an outside service, the Activation Trigger listens to the lifecycle of the automation it sits in: the workflow gets activated, the workflow gets saved while it is already active, or the n8n instance starts or restarts. Its description in n8n says it plainly, it executes whenever the workflow becomes active. That is the whole scope, and it is why the node has exactly 1 parameter.

The first thing it buys you is a startup routine. A workflow that you switch on at the beginning of a campaign can announce itself: one execution runs the moment the switch flips, posts a line in Slack so the team knows the automation is live, and the rest of the day belongs to the other triggers in the account. Nobody has to remember whether the thing was turned back on after maintenance.

The second is a warm-up step. Some automations need a value in memory before the real work starts, a reference list, a counter, a timestamp. Put the Activation Trigger at the head of that branch, shape the values with Edit Fields (Set), and every restart of the instance rebuilds the same starting state. An expression such as {{ $json.startedAt }} then carries that value to the nodes downstream, an expression being the small piece of code n8n evaluates inside a field.

The third is a sanity check after a save. With the update event ticked, saving an active workflow runs it once. Point it at a call that confirms the outside world is still reachable, an endpoint fetched with HTTP Request, which calls any HTTP endpoint and is the way in when no dedicated node covers an API operation. A failed run right after a save tells you something broke before the next real event does.

Where it stops is just as clear. This node carries no payload from a service, no filter, no schedule of its own. It knows that a workflow changed state, nothing more. If the automation has to start on a customer action or on a file landing somewhere, that job belongs to the trigger of the service in question, not here. And the workflow has to be active for the node to listen in production; inside the editor, a test execution starts a one-off listen so you can see the shape of the item it produces.

It is a core node, shipped with n8n, so it behaves the same on n8n Cloud and on an instance you host yourself with Docker or npm. Nothing to install, nothing extra to pay on the n8n side. If you are still deciding whether the tool fits the way your team works, the n8n review goes through that question at length.

Parameters

Which events can the node listen to?

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

01

Events

events

What you see in n8n

Notes & use cases

Events is the only parameter on the node, a multi-select of the conditions that wake the workflow up. It is required. Leave every box unticked and the execution is blocked. Tick one or several, and the node fires once for each.

Key parameters

  • Activation (activate): runs when the workflow gets activated, the classic switch-on moment.
  • Start (init): runs when n8n starts or restarts, which covers container restarts and upgrades.
  • Update (update): runs when the workflow gets saved while it is active, so an edit in production triggers a pass.
Use cases
tick Activation alone for a one-line launch notice, add Start when the same setup has to survive a restart of the instance.
Need help

Need help automating Activation Trigger with n8n?

A person reads every message.

FAQ

Questions people ask about this node

01Is the n8n Activation Trigger node included in n8n?
Yes. It is a core node, shipped with n8n, so there is nothing to install and nothing extra to pay on the n8n side. You get the same node on n8n Cloud, the hosted offer run by n8n, and on an instance you host yourself with Docker or npm under the Community Edition and its Sustainable Use license. A workflow built in one place behaves the same in the other, which matters if you prototype on Cloud and move to your own server later. The page describes version 1 of the node, the highest version in the catalog; an older workflow can show an earlier one, and a node never changes version by itself.
02What do you have to set up before it works?
Nothing on the account side. This node has no credential and no Authentication selector, a credential being the stored login n8n reuses to reach an outside service. There is simply no outside service here. Two things do matter. First, at least one box has to be ticked under Events, because a required field blocks the node when it stays empty. Second, the workflow has to be active for the node to listen in production. While you are still in the editor, a test execution starts a one-off listen, which is enough to check what the node hands to the next step.
03What are the limits of this node?
It reports a change of state, and that is all. The 3 conditions it knows are activation, save while active, and start or restart of n8n. There is no filter, no condition on who saved the workflow, no data about any external system in what it produces. It also has no schedule of its own, so it cannot stand in for a recurring run. Anything the branch needs after that has to be fetched by another node, and it exposes a single parameter, so the configuration surface is as small as it looks.
04When should you use it rather than another trigger?
Use it when the event you care about is the workflow's own lifecycle, not something happening in a tool. Switching an automation on, saving it while it runs, restarting the instance: those three moments belong to this node and to no other. As soon as the starting point is a message, a row or a payment, the trigger of that service is the right entry point, and the Activation Trigger at best complements it with a startup pass. If the starting point is an HTTP endpoint you want to call rather than an event you want to receive, that is HTTP Request territory, since it reaches any HTTP endpoint and covers API operations no dedicated node exposes.
05n8n or Make for a workflow like this?
It depends on where you want the automation to live. Make is a hosted automation platform with no self-hosting option, billed per operation, so the cost follows how often your scenarios run. n8n can run on its own server, which keeps the data on infrastructure you control, and it also has a hosted offer if you would rather not manage anything. Both give you a visual canvas, and the logic you build carries over conceptually. The honest way to decide is to look at hosting, data control and the cost model against your own volume, then pick the one that matches.
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