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

No items found.
No items found.
  1. Help
  2. Integrations
  3. iPaaS
  4. connector-documentation
  5. Runbook Variables 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

Runbook Variables Connector

Manages reusable variables that can be referenced in field mappings and connection configurations across a runbook

🔌 Runbook Variables Connector

This connector provides a centralized way to store and retrieve data within a single runbook execution, acting as a temporary storage for intermediate results.

⚡ Actions

Assign Runbook Variable

  • Sets a reusable value for a specific variable ID.
  • The stored value can be referenced in subsequent actions and outbound connection configurations.

📥 Input Parameters

  • id (Runbook Variable, Required): The unique identifier for the variable (maximum 256 characters).
  • value (Any, Optional): The value to assign; the input type adapts automatically to the variable's definition.

📤 Output

  • value (Any): Returns the assigned value, with the data type matching the variable's definition.

📌 Use Cases

  • Computed Values: Storing results from a script or calculation for reuse in later steps.
  • API Key Management: Holding temporary security tokens retrieved during a workflow.
  • Intermediate Results: Saving data collected from one system to be used across multiple different actions.

⚠️ Notes

  • Dynamic Typing: The value field is flexible and adapts its type based on how the variable was defined.
  • Safety Check: If you attempt to assign a value to an ID that hasn't been defined in the runbook, the system records a log message and returns nil.