The Workflow Trigger node triggers a second workflow from the first one, when the execution reaches that point in the workflow
You can choose any workflow that exists in your account, to be triggered by the node
Selecting the checkbox will ensure that the second workflow is triggered only after the first workflow is completely executed
This can be understood with an example:
Our goal is to copy an RDS DB cluster from a single availability zone to multi availability zone to increase reliability and then convert it back to a single availability zone for frugal usage.
For the first workflow
For the 2nd workflow
This is how the workflow will look:
The trigger is set to activate this workflow everyday (this may vary for each use-case).
In the resource node we pick the AWS resource on which we want to work. We have chosen RDS clusters.
In the filter node there are two parameters on the basis of which we separate the RDS clusters - the clusters that are in a single availability zone and the nodes which don't have an aurora engine.
The Action node is performing the action of converting the RDS cluster from single availability zone to multi-availability zone.
After the RDS clusters are converted from single availability zone to multi availability zone we will convert them back to single availability zone for frugal utilisation of our resource. This can be done with an existing workflow which we trigger through this node. The node has a drop down of all the workflows that you have in your account, and you can choose the next workflow to be triggered.
The second workflow that is being triggered looks like this:
Let's look at all the nodes:
The trigger node runs everyday (this may vary for different use cases)
In the resource node we pick the AWS resource on which we want to work - RDS instances in this case.
The Action node converts the RDS instance from multi-availability zone to single availability zone.
This node send a report of the workflow to the desired E-mail ID or Slack.