DocsNodesOverview

Node reference

A workflow is a chain of nodes, which the console calls steps. Every run starts at a trigger, and the steps after it change the flow, wait, keep a value, do something or stop. Here are all 24, in the same groups and colours as the console's palette. Open one for its settings, what it adds to the run and an example.

Starts the workflowFlowWaitsDataDoes somethingStops
CreditsStarting a run costs 1 credit, and each node it passes through costs more from your monthly allowance. Triggers are free, bookkeeping costs 0.1, a message to a client 1, Telegram, Discord, ntfy or a URL 5, and an email 10. See Plans and billing.

Ports

A port is where a run leaves a node. Most nodes have one output, default, drawn as a single dot on the card's edge. Nodes with more than one outcome list them, and a run that reaches a port with nothing connected ends there as done. The canvas shows some ports by a friendlier name, given first below; the workflow definition and the API use the id.

PortLeaves when
yes / no true / falseThe If node's conditions held, or didn't.
each item body, done, emptyOnce per item; after the last item; when the list had none.
called, received defaultThe call or signal a Wait for a call or Wait for signal step was waiting for arrived.
timed out timeoutA wait ran out before the callback, signal or acknowledgement arrived.
acked / failedThe client confirmed the command, or refused it (for example because it had expired).
errorThe URL answered with an error after its retries.