Workflows and components
A workflow is a graph of components. Messages enter at a trigger, move along the connections you draw, and each component transforms them or performs an action.
Build a flow
Open Workflows, create or open a workflow, and use the editor to add components. Connect an output port to the next component’s input port to define how messages move through the flow. Configure each component for your data.
Choose your components
The component catalog includes triggers, transformations, requests, debugging tools and DigiSense integrations.
Read each component’s own documentation for its expected input and output format. A component may require credentials or additional settings before it can work.
Components are executable code, not passive configuration. A component that calls an external service or controls a device will do so every time a message reaches it.
Test incrementally
Start simple
Begin with a trigger and a debug or print component — nothing else.
Send a sample message
Inspect its shape. Confirm the fields are what you expected before building on them.
Add one transformation at a time
Check the output after each addition.
Connect actions last
Only once the message shape is confirmed should you connect components that call services or control devices.
Save and check runtime status
A saved flow is not necessarily a running one — confirm its status.
The reason for this order is that a flow with an action at the end gives you no safe way to inspect an unexpected message: by the time you see the problem, the action has already run. Building forward from a debug node keeps every intermediate step observable.
Relationship to downlinks
A workflow can send commands, and so can a downlink triggered on measurements. Use downlinks for a direct device command tied to a device’s own outputs, and workflows when the logic spans several sources, requires transformation, or has to call external services.