Control
Button trigger
A button on the canvas. Press it and it turns on for a moment, then off again.
| Port | Side | What it carries |
|---|---|---|
enable | In | Optional. While it is off, the button cannot be pressed. If nothing is wired to it, the button is always enabled. |
label | In | Optional. Text for the button, in place of the label typed on the card. |
out | Out | On for half a second after each press, then off. |
What you choose
What the button says. Type a label on the card — Send summary, Ask now — or wire a Text box to label so it follows something else.
Then press it whenever you want the work done. It is the hand on the switch: an action you start yourself, rather than one a figure or a date starts for you.
What Fluidly decides
A press turns the button on for half a second and then off, so the action wired to it runs once per press. Holding it down does not repeat it.
Enable
Wire a trigger to enable and the button can only be pressed while that trigger is on. The button greys out otherwise, and the card's border shows why. A press then needs both: you, and the condition.
That is how to put a person in the loop. A Range trigger decides the transfer may happen; the button decides that it does.
Example
Button trigger → Ask AI, with ERP (unpaid invoices) → data: press the button and Claude reads the open receivables and answers your question about them. Nothing is sent until you press.