Onramp
Change trigger
Turns on when the number or records it watches change, and keeps a record of every change. Offered as Watch on a port.
| Port | Side | What it carries |
|---|---|---|
what to watch | In | A single number, such as a balance, or a set of records, such as transactions. |
changed | Out | On for a moment after a real change, then off again. |
changes | Out | What changed — the last difference, the latest new rows, a running total and the full history, each with its time. |
What you choose
Very little. Wire something in and the trigger watches it. The quickest way there is the port itself: on any number or records port, Watch is the last item in the menu.
The one choice is how long it stays on after a change. Double-click the card and set the cooldown in seconds. While it is on, further changes are noted but do not switch it on again; once it has gone off, the next change does. Leave the field empty and it stays on after the first change.
What Fluidly decides
Fluidly decides what counts as a change. A refresh that brings the same figure back is not one, and neither is the first value after the flow starts — that is the starting point, not news.
What it compares follows from what you wire:
| What you connect | A change is | What changes carries |
|---|---|---|
| A number | the figure moved | the difference, such as −2,500 |
| Records | new rows arrived | the new rows themselves |
If several rows arrive together, the trigger turns on once and changes carries all of them, so one email covers the whole batch.
Watch the records, not the total
To hear about new payments, put the Change trigger on the transactions themselves. Watching a total works only while payments arrive one at a time: two in the same refresh become one difference that matches neither.
Example
Bank Account (transactions) → Change trigger → Email: an email whenever new transactions arrive — once per batch, not once per row.