Action nodes
An action does something to the outside world in the middle of a flow — and does it every time execution reaches it. Flux ships two: API and Email.
API action
Makes an HTTP request as a step in the workflow. Use it when the call is not optional: always fetch this record, always post this update.
| Setting | Notes |
|---|---|
| URL | Can be built from template expressions, so it varies per run |
| Method | The HTTP verb |
| Headers | Where a {{CREDENTIAL ...}} expression usually goes |
| Body | Built with {{IN ...}} and {{POUT ...}} expressions |
| Response template | Shapes what this node passes on, so the next node gets a clean structure |
The API action node form with URL, method, headers, body and response template fields, and template expressions visible in several of them
Screenshot to be added{{POUT}}
expressions then stay short and survive changes in the upstream API.
Email action
Sends an email as a step in the workflow. Recipients, subject and body can all be built from template expressions, so the message is specific to the run.
Use it for notifications that must always go out: a confirmation after a form is processed, an internal alert when a job finishes, a digest at the end of an interval run.
Action or tool?
Both API and Email exist in a tool version as well, and the difference is who decides:
| Action | Tool | |
|---|---|---|
| Wired to | The input chain | An AI node's tool connector |
| Runs | Every time flow reaches it | Only when the model decides to |
| Parameters | You set them, with templates | The model fills them in, guided by DESC |
| Use when | The step is mandatory | The step depends on what was asked |
"Always log the enquiry" is an action. "Look up the order, if they mention an order" is a tool. See Tool nodes.