The Workflow Trigger Node allows an Application Workflow to trigger another Application Workflow to run.
There are two parts to configuring a Workflow Trigger Node - selecting the workflow and virtual button to trigger, and optionally creating a payload to be used for the trigger.
First step is selecting the workflow and virtual button to trigger. The dropdown will list all virtual buttons in all of the workflows in the current application. In the example above, the node is configured to trigger the button “Trigger Light” in workflow “Internet Button”.
The next step is configuring the payload. 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 - by payload path, string template or JSON template. In the above example, 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.