1. Help
  2. Integrations
  3. iPaaS
  4. connector-documentation
  5. Flow Connector

purple icon for coordination.
We’ve moved!
Our Help Center has a new home and our URLs have changed. Please update your bookmark to this page before April 30, 2026

Flow Connector

Provides flow control actions for building structured runbook workflows, including branching, looping, and error handling

🔌 Flow Connector

This connector provides the structural logic necessary to manage complex automation paths within a runbook.

⚡ Actions

If-then-else

Evaluates a boolean condition to route execution to a True or False path.

Loop

Iterates over each item in an array, executing successor actions once per item.

Try-catch

Executes actions in a "Try" block and handles any resulting errors in a "Catch" block.

Fork

Starts multiple action branches that execute in parallel for faster processing.

📥 Input Parameters

  • condition (Boolean, required for If-then-else): The condition to evaluate.
  • items (Array, required for Loop/Batch): The collection of items to iterate over.
  • nr_of_actions (Integer, required for Fork): Number of parallel branches (2-50).
  • seconds_to_wait (Integer, required for Wait): Minimum seconds to pause execution.

📤 Output

  • item: The current item from the array during a loop.
  • error: The error message received in a Catch block.
  • index: The zero-based index of the current item or branch.

📌 Use Cases

  • Conditional Branching: Executing different steps based on data values.
  • Batch Processing: Handling large arrays in smaller chunks for API efficiency.
  • Parallel Execution: Running independent actions concurrently.
  • Graceful Recovery: Retrying failed operations after catching an error.

⚠️ Notes

  • Nested Actions: Successor actions must be placed inside the branches of these flow controls.
  • Wait Duration: Actual wait time may be longer than requested due to system scheduling.
  • Retry: The Retry action must be placed specifically inside a Catch block.