Test nodes

You can test data from individual nodes in a flow before publishing the whole flow. Testing individual nodes helps you catch misconfigurations, permission issues, or wrong parameters early, so you don't discover them only when the flow runs in production. For example, you might test an EC2 DescribeInstances node to confirm it returns the expected instances and fields, or test a step that deletes or tags resources to verify it targets the right IDs—without running the full flow or affecting other steps.

Furthermore, you can choose to save a node's test output so the data is automatically available when you test downstream nodes. CloudFlow automatically builds the payload for the test using the data from upstream nodes. For action nodes (for example, AWS or Google Cloud nodes), you can optionally use custom input parameters for the test without changing the node configuration.

Caution

Running a test performs a full execution of the node and can initiate real actions, such as deleting resources or modifying data. Consider the results of the action before you run a test and before continuing to downstream nodes.

Tip

• You must fill all parameters and connections before testing.

• For action nodes, you can choose to use parameters from the node configuration or your own parameters for the test only. When you use your own parameters, the Test tab is pre-filled with the current node's parameters; you can edit them or add additional parameters (for example, from upstream nodes). References to variables or other nodes are resolved when you run the test.

• Select Save as test data to make the test data from one node available when testing downstream nodes.

1. Either select Go to test from the node configuration tab or select the Test tab.

2. (Optional) For action nodes: Choose whether to use the parameters from the current node configuration or your own parameters. If you use your own parameters, the Test tab is pre-filled with the current node's parameters; you can edit them or add additional parameters (for example, from upstream nodes). References to variables or other nodes are resolved when you run the test.

   

3. (Optional) Select Save as test data to make the test data available when testing downstream nodes.

4. Select Test.

5. Select Test results to validate the node behaves as expected.

   

6. (Optional) Select Test data. You can:

   • Select Copy to copy the test data. For example, if a node needs test data from a node where you do not want to run a test, because it's slow/expensive, then you can paste a known payload from another run as that node's test data so the downstream test can run.

   • Select Edit to edit the test data. For example, you may want to test another use case, (a different ID, date, or flag) or reproduce a bug. You can edit the test data and run the test again instead of re-running the upstream node.

7. Edit a downstream node and select Test. If you selected Save as test data, the referenced node is listed.

   

8. Repeat these steps for each node in the flow you want to test.