The Workflow Trigger Node allows an Application Workflow to trigger another Application Workflow to run. It works by enabling one workflow to ‘press’ the Virtual Button of another workflow. Data from the payload can be sent between Workflows.
In this configuration, you are specifying which Application Workflow you want to trigger. To do so, you must select the workflow, workflow version, and virtual button to trigger. Each dropdown will be dynamically updated from the last to show your options.
For example, the “Workflow” dropdown shows all workflows in the current application, “Workflow Version” shows each version of the selected workflow, and “Virtual Button” shows each of the buttons in that version.
Optionally, you may enter a template for any of these values, however, the subsequent dropdowns will not dynamically populate if you do so.
You have the ability to send data from the payload to the Application Workflow. Here you may define what data to send.
Configuring the payload is optional - if there is no payload specified, the default payload for the given workflow and Virtual Button will be used.
There are a couple different ways to specify a payload:
In the example below, the node is configured to trigger the button “Trigger Light” in the “default” version of workflow “Internet Button”. Additionally, the node is using the value at the payload path
data.subPayload as the payload for the triggered workflow.
The Workflow Trigger Node has the same throttling rules as using the API to trigger a virtual button. It is limited to 100 calls in a 10-second window (per virtual button), on average, 10 calls per second.