Action

Change gate

Fire when a value changes

Change gate only lets the workflow continue when a value it watches has actually changed since the last run; if nothing changed, the job stops there.

How it works

Change gate is a checkpoint that asks one question: is this different from last time? It remembers the value it watched on the previous run and, when a new job comes through, it compares. If the value moved, the job passes and the rest of the flow runs. If it is the same, the job stops at the gate.

This is what turns a repeating check into a quiet one. You might pull a page or a record on a schedule, but you only want to hear about it when something actually changed. Change gate holds back all the identical runs so your delivery steps only fire on real differences.

It sits well right before a notification or an output step, and right after whatever fetches the thing you are watching. The result is monitoring that stays silent until it has news, instead of pinging you every time it looks.

Common use cases

Real situations where this node earns its place in a flow.

Act only on real movement

Watch a fetched value and continue only when it changes past a threshold, so you react to signal not noise.

React to a status flip

Continue the flow only when a monitored status goes from one value to another.

Notify on a drop

Fire when a tracked figure (stock, balance, price) falls below a line you set.

Change gate in a workflow

A simple example of where this node sits in a flow.

Schedule Fired by an Event (cron) Web fetch Fetch a URL · call an API Change gate Fire when a value changes Email outbound Send report link

What you set up

  • Point the gate at the specific value it should watch for changes.
  • Decide what counts as a change (any difference, or only certain fields).
  • Connect the pass path to whatever should run when something is new.

Common questions

What happens on the very first run?

With nothing to compare against yet, the gate records the starting value. From the next run on, it has a baseline and passes the job only when the value differs from it.

Does it alert me when nothing changed?

No, and that is the point. Identical runs stop at the gate silently, so your notification steps only fire when there is a genuine change to report.