Nodes are the building blocks of a workflow. You can pick and choose nodes and arrange them in a logical, sequential manner to create a workflow that satisfies a use case. We’ve basically broken down the entire cloud management layer into these building blocks - so any level of complexity can be achieved.
When you’re creating a workflow, think of how you’d execute the use case on your AWS CLI, or draw out the flow on your whiteboard. The same logic and pattern will enable you to create a workflow. When you go to the ‘Workflow Editor’ and select any node, you’ll notice that each node has a ‘Node name’ and a ‘Node ID’ below it. We’ve explained the Node ID below.
You can also see 'Description', which is an option for you to give a one-line description of the purpose of the node, which is usually just to help understand the workflow better (it's optional).
‘Set Conditions’ enables conditional execution of nodes. As of right now, you can set up to one condition. Every node has a 'Set Conditional' link on the top right that can be clicked to add a condition.
Some nodes will have a parameters box that is available for additional customization and information. These parameters are in line with the AWS API parameters. Whenever a parameter is optional, it is stated as ‘optional’.
When building out complex workflows with multiple nodes and actions, it becomes difficult for the sequence to be linear. That’s why we’ve developed ‘node referencing’.
Each node is given a unique identifier, which can be referenced while setting up other nodes. This essentially means that you can perform multiple actions on multiple resources, filtered or otherwise. The editor asks you to pick the specific resource on which the action is to be performed, and the applicable ID can be picked.