Runbook Manager Connector

🔌 Runbook Manager Connector

This connector enables advanced workflow orchestration by allowing runbooks to call other runbooks or respond to system-level lifecycle events.

⚡ Triggers

Runbook Action

• Enables a runbook to be invoked as an action from another runbook.
• Receives parameters defined in the trigger's configuration.

Runbook Stopped by System

• Fires when a monitored runbook is stopped by the system.
• Useful for triggering alerting or recovery actions when failures occur.

⚡ Actions

Runbook Action

• Invokes another runbook that has the "Runbook action" trigger configured.
• Passes parameters and receives a job reference (UUID) for the execution.

📥 Input Parameters

• runbook_action (Runbook, Required for Action): The specific runbook to invoke.
• parameters (Object, Required for Trigger): Schema definitions for the data the runbook accepts.
• runbooks (Array, Required for Monitoring): List of runbooks to monitor for system stops.

📤 Output

• job.uuid: The unique Job ID of the triggered runbook execution.
• message: The stop message or reason provided when a runbook fails.
• parameters: The actual values passed into a runbook by a caller.

📌 Use Cases

• Modular Workflow Design: Creating a library of reusable runbook components.
• Multi-Runbook Orchestration: Managing complex pipelines that span multiple runbooks.
• Error Monitoring: Automatically triggering recovery workflows when a critical runbook is stopped by the system.

⚠️ Notes

• Requirement: A target runbook must have the "Runbook action" trigger configured to be callable.
• Monitoring Limits: The system stop trigger only monitors "stopped-by-system" events, not manual user stops.
• Environment: Requires configuration of the target environment, such as EU Production or EU QA.

‍