Scheduled Execution

!

Cloud feature — Scheduled execution is available on superglue Cloud and is not available in the open-source version.

Schedules run saved tools automatically using a five-field cron expression and an IANA timezone. Every scheduled execution creates a run that you can inspect from Runs.

Create a schedule

1. Open the deployment dialog

   Open a saved tool, click Deploy, select Schedule, and click Add Schedule.

2. Choose the frequency and timezone

   Select a preset or choose Custom cron. The available presets include every 5 minutes, every 30 minutes, hourly, daily, weekly, and monthly.

   Common custom expressions:

   • */5 * * * * — Every 5 minutes
   • 0 9 * * 1-5 — Weekdays at 9:00
   • 0 */6 * * * — Every 6 hours
   • 0 0 1 * * — First day of every month
   i

   The selected timezone determines when the cron expression is evaluated. Use crontab.guru to check an expression.

3. Add the JSON input

   Optionally provide the payload passed to every run. The editor validates that the value is valid JSON.

4. Configure advanced options

   • Completion action: Call an HTTP webhook or start another saved tool when the run completes.
   • Credentials: Pin an accessible credential set for each system used by the tool, or keep the user’s default.
   • Run timeout: Set the maximum duration in seconds, or leave it empty to use the deployment default.

5. Save the schedule

   Click Add Schedule. New schedules are enabled by default and receive their next run time immediately.

Manage and test schedules

The Schedule tab shows the human-readable frequency, next run, completion action, and current status. From there you can:

• Run an immediate Test using the schedule’s payload, credentials, timeout, and completion action
• Edit the frequency, timezone, payload, or advanced options
• Enable or disable future executions
• Delete the schedule permanently

Disabling a schedule preserves it without claiming future runs. Deleting it removes the schedule but does not delete existing run history.

Execution behavior

• Scheduled runs use the scheduler request source and appear in Runs.
• A schedule executes with the access of the user who created it. Pinned credentials must remain accessible to that user.
• Archiving a tool disables its schedules. Deleting a tool deletes its schedules.
• Failures are recorded like any other run and can trigger configured notifications.

Schedules can also be created and managed through the CLI schedule commands or REST API.