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
Scheduler Connector
Provides time-based automation for triggering runbooks at regular intervals using static or dynamic schedules.
🔌 Scheduler Connector
The Scheduler allows for the automation of runbooks based on a fixed recurring basis or via schedules created programmatically during runtime.
⚡ Triggers
Scheduler
Defines a recurring schedule to fire a runbook at regular intervals, such as hourly or daily.
Dynamic Scheduler
Executes runbooks based on schedules that are created or managed programmatically at runtime.
⚡ Actions
Create Schedule
Programmatically creates a new recurring schedule for a specified target runbook.
Update Schedule
Modifies the timing, frequency, or recurrence settings of an existing schedule.
Delete Schedule
Removes an existing schedule using its unique reference identifier.
📥 Input Parameters
- schedule (Recurrence, required): The definition of frequency, interval, day, time, and time zone.
- runbook_uuid (String, required for Create): The unique identifier of the runbook to be scheduled.
- schedule_reference (String, required): A unique identifier used to manage, update, or delete the schedule.
- request_body (Hash, optional): An optional payload to include with each scheduled trigger event.
📤 Output
- triggered_at: The timestamp of when the trigger event occurred.
- next_occurrence_at: The next scheduled execution time for the created schedule.
- success (Boolean): Indicates whether a delete or update action was successful.
📌 Use Cases
- Periodic Syncing: Running daily data synchronizations between different systems.
- Health Checks: Performing scheduled status polling or health checks on services.
- Lifecycle Management: Programmatically managing recurring automations based on external events.
⚠️ Notes
- Provisioning: The standard Scheduler trigger creates a schedule upon provisioning and removes it upon deprovisioning.
- Soft Delete: The "Delete Schedule" action performs a soft-delete, marking the schedule as deleted rather than permanently removing it.
- Scheduling Delays: The actual wait duration or trigger time may be slightly longer than requested due to internal system scheduling.
Open Modal
