Additional Parameters in Action Node

Totalcloud Updated by Totalcloud

You can pass additional parameters, as a query, specifying the details of the action to be performed.
Points to remember:
  1. You can pass name and description in the JSON query. Else, it is auto generated. You can either use them or overwrite them according to your needs.
  2. Other essential parameters will be automatically fetched from the previous Resource/Filter node. For example: Resource IDs
  3. If you do not have a Resource node as part of the workflow, you can specify parameters in the Addition Parameters section.

Example: If you want to take action on only two specific volumes of EC2 instances instead of all the volumes, you can pass an additional query, such as Volume IDS, in the Additional Parameters section. This narrows down the action to only these two volumes.

{
"VolumeIds": [
"vol-0463cb2f6a37175dd",
"vol-0bc49a5417b57d51c"
]
}

The following scenarios explain the usage of Additional Parameters in detail:

Scenario 1: If the preceding node is Trigger node and you input additional parameters to Action node

You can directly fetch any AWS service and define the action in the Action node. When you pass additional parameters to Action node, the action will be performed only as per the parameters passed in the Additional Parameters input window.

Example: If you want to take action on only two specific volumes of EC2 instances instead of all the volumes, you can use the Action node and pass an additional query in the Additional Parameters window, like Volume IDS belonging to Tags Stack:Test.

{
{
"VolumeIds":
[
"vol-0463cb2f6a37xxxxx",
"vol-0bc49a5417b5xxxxx"
]
}

"Description": "VALUE", /* Description can be autogenerated with timestamp */
"TagSpecifications":
[
{
"ResourceType": "VolumeID",
"Tags": [
{
"Key": "Stack",
"Value": "Test"
}
]
}
]
}

The sequence of steps essential to carry out this use case is as follows:

The Create Snapshot action will run on only those volume IDs belonging to Oregon region with Tags "Stak:Test" as specified in the Additional Parameters.

Scenario 2: If the preceding node is a Resource node and you add Additional Parameters in Action node

You can perform partial filtering of resources in the Resource node and partial filtering of resources in Action node's Additional parameters feature.

Let's consider the same use case where we take snapshots of EC2 volumes that belong to Tags User.Stack: Test. In this scenario, you can:

  1. Filter Volume IDs in Resource node's Advanced Filters using the following data:
{
"VolumeIds":
[
"vol-0463cb2f6a37175dd",
"vol-0bc49a5417b57d51c"
]
}
  1. Filter them further with Tags User.Stack: Test in Action node's Additional Parameters using the below data:
"Description": "VALUE",		/* Description can be autogenerated with timestamp */
"TagSpecifications":
[
{
"ResourceType": "VolumeID",
"Tags": [
{
"Key": "Stack",
"Value": "Test"
}
]
}
]

The sequence of steps essential to carry out this use case is as follows:

In this node, the Create Snapshot action will run on only those volume IDs belonging to Oregon region with Tags "Stak:Test" as specified in the Additional Parameters.

How did we do?

Action Node

Usage Examples of Action Nodes

Contact