Workflows
Build pipelines from nodes, run them on a schedule or a trigger, and route their outputs.
- WorkflowsWhat a workflow is, how the Workflows list and the editor are laid out, what a version is, and what every run leaves behind.
- Build a workflowCreate a workflow in the editor: add nodes, wire their ports, set each node, declare an Output, save, run it and read the Console.
- Node referenceEvery node in the workflow editor's Nodes panel, section by section: what each one does and which ones appear only when an app is on.
- SchedulesRun a workflow at set times: calendar or exchange timing, run times in a time zone, the run policy, and the version every scheduled run uses.
- Webhooks and signalsStart a workflow from another system's request or from a market signal. Set up an incoming webhook or a signal monitor under Automations, with its checks, duplicate handling and limits.
- Outputs, alerts and actionsWhere a workflow's result goes: the Output node, the Alert node, watchlist and metric writes, HTTP calls and child workflows.
- Runs and versionsWhat each run status means, how to read Run History, what the timeouts and On node failure do, and how versions and main decide what a run executes.
- Troubleshooting workflowsSymptom by symptom: a failed, paused, held or timed-out run, a scheduled run that did not start, a workflow marked Needs attention, a refused webhook, and a node whose app is off.