Scheduled Execution

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 a saved tool and click Deploy.
2. Select Schedule and click Add Schedule.
3. Select a preset or choose Custom cron. The available presets include every 5 minutes, every 30 minutes, hourly, daily, weekly, and monthly.
4. Choose the timezone.
5. Optionally, add the JSON input. This is the payload passed to every run. The editor validates that the value is valid JSON.
6. Optionally, configure the advanced options:
   • Completion action: Call an HTTP webhook or start another saved tool when the run completes.
   • Connections: Pin an accessible connection for each system ID 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.
7. Click Add Schedule. New schedules are enabled by default and receive their next run time immediately.

Common custom cron expressions

Expression	Runs
*/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.

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, connections, timeout, and completion action
• Edit the frequency, timezone, payload, or advanced options
• Enable or disable future executions
• Delete the schedule permanently

See all schedules

Capabilities → Schedules lists every schedule you can access, with its tool, frequency, next run and status. Filter by status or tool, search by tool ID or system, and select several schedules to enable, disable or delete them together.

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 connections must remain accessible to that user.
• Failures are recorded like any other run and can trigger configured notifications.

FAQ

What is the difference between disabling and deleting a schedule?

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

What happens to schedules when I archive or delete a tool?

Archiving a tool disables its schedules. Deleting a tool deletes its schedules.

Can I manage schedules outside the app?

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