Qualys Flow categorizes nodes based on the type of function they perform.
To access the nodes,
1. Log in to your Qualys Flow account.
2. Go to the Editor tab and click the explore nodes icon located at the top left corner of the Editor window.
The Explore Nodes pop-up window is displayed.
To know the function of these nodes, refer to the following table.
Node |
Function |
Trigger |
By default, is the first node present in the editor for any QFlow. The trigger can be time-based, AWS event-based, manual, or TotalCloud .
|
AWS Nodes (Cloud-Specific Nodes) |
|
AWS Resource |
It fetches the resources that belong to a specific AWS service. The node can access all AWS services and resources available to you. For example, you can select the RDS service and use DB instances as a method in the AWS resource node to get metadata of RDS DB instances. |
AWS Action |
It performs the action you define on the selected resources; the actual automation is accomplished in this node. For example, after identifying the list of publicly available RDS DB instances, you can perform the action i.e. delete DB Instances. |
Azure Nodes (Cloud-Specific Nodes) |
|
Azure Resource |
It fetches the resources that belong to a specific Azure service. The node can access all Azure services and resources available to you. It fetches all the resources provided by Azure Software Development Kit (SDK) that belong to a specific Azure service. |
Azure Action |
It performs the action you define on the selected resources; the actual automation is accomplished in this node. It performs all the actions that are part of Azure SDK defined in the selected resources. |
GCP Nodes (Cloud-Specific Nodes) | |
GCP Resource |
It fetches the resources that belong to a specific GCP service. The node can access all GCP services and resources available to you. For example, you can select the Google Compute Engine for service, Instances for resources, and the specific API that you want to execute (For example, List to get all the VM instances under Google Compute Engine) |
GCP Action |
It performs the action you define on the selected resources; the actual automation is accomplished in this node. The GCP Action node can perform any action that is available for a resource, in the GCP SDK. |
General Nodes |
|
Filter |
It performs filtering of the resources based on a set of conditions. You can combine criteria using logical AND/OR conditions to filter this data. For example, you can filter publicly available RDS DB instances from all RDS DB instances using the Filter node. Use the following filters based on various fields:
|
Report |
It allows users to generate and download reports of the selected data in CSV or JSON format. |
Custom |
It is used to write scripts to create complex filters, customize the selected data, data transformation like XML to JSON, etc. It supports java script code, and some libraries of nodes. |
HTTP |
It makes HTTP(S) calls from a QFlow. This allows you to integrate the third-party application or service with an HTTP endpoint via API Calls. You can place the HTTP node anywhere in the QFlow. |
Workflow Trigger |
It is used to trigger another workflow (QFlow) present within the QFlow application. |
Data Formatter |
It takes in the output of the previous node as input and allows to format it as per requirement. |
Data Joiner |
It joins data from two previous nodes. |
TotalCloud |
It is the TotalCloud-specific node. When you want to use QFlow in the TotalCloud application, you need to add the TotalCloud node. |
RAW |
It is an API node that allows you to call any API function supported by the cloud service platform and perform the action on the resources. |