Workflow Schedules

Run a workflow automatically on a cron schedule, with no cron infrastructure of your own.

API Reference

See the full request/response schema and parameters in the API Reference.

Schedule definition

A schedule binds a workflow_id to a cron_expression and timezone:

workflow_id — the workflow to run. It must exist in your organization.
name — required, up to 120 characters.
cron_expression — standard 5-field cron (minute hour day month weekday). An invalid expression or timezone returns 400.
timezone — IANA timezone, e.g. America/Los_Angeles. Defaults to UTC.
description — optional free-form text.
is_active — defaults to true. Set to false to save a schedule without activating it.

Schedules belong to their team. Removing their creator from the team or organization leaves them running unless an administrator selects the pause option. Key-bound schedules pause when their API key is revoked or expires. Archiving the team also pauses its schedules. An automatic pause sets disabled_reason on the response.

API keys remain valid after their creator leaves unless explicitly revoked. Anyone who still holds a key can continue using it. Selecting key revocation during member removal also pauses schedules bound to those keys.

Create schedule

Create a new schedule for a workflow.

POST https://api.sixtyfour.ai/schedules

Required body fields: workflow_id, name, and cron_expression. Returns 201 with the schedule, including up to three upcoming next_run_times.

Example request

{
  "workflow_id": "WORKFLOW_ID",
  "name": "Daily lead refresh",
  "cron_expression": "0 9 * * *",
  "timezone": "America/New_York",
  "description": "Re-enrich the prospect list every morning"
}

Example response

{
  "id": "a1b2c3d4-5e6f-4789-a123-b4c5d6e7f890",
  "workflow_id": "WORKFLOW_ID",
  "team_id": "3c4d5e6f-7a8b-4c9d-8e0f-1a2b3c4d5e6f",
  "name": "Daily lead refresh",
  "description": "Re-enrich the prospect list every morning",
  "cron_expression": "0 9 * * *",
  "timezone": "America/New_York",
  "is_active": true,
  "disabled_reason": null,
  "created_by": "f9e8d7c6-b5a4-4321-9876-543210fedcba",
  "api_key_id": null,
  "next_run_times": [
    "2026-07-17T13:00:00Z",
    "2026-07-18T13:00:00Z",
    "2026-07-19T13:00:00Z"
  ],
  "created_at": "2026-07-16T18:00:00Z",
  "updated_at": "2026-07-16T18:00:00Z"
}

List schedules

Retrieve the schedules of your active team.

GET https://api.sixtyfour.ai/schedules

Optional query parameter: workflow_id — filter to schedules for a single workflow.

Get schedule

Retrieve a single schedule by ID.

GET https://api.sixtyfour.ai/schedules/{schedule_id}

Update schedule

Update a schedule’s name, cadence, timezone, description, or active state.

PATCH https://api.sixtyfour.ai/schedules/{schedule_id}

All body fields (name, cron_expression, timezone, description, is_active) are optional — only include what you want to change.

Reactivating a paused schedule rebinds its execution identity to the current user or API key and clears disabled_reason. The schedule remains owned by its team.

Example request

{
  "is_active": false
}

Delete schedule

Permanently delete a schedule. Returns {"success": true, "id": "SCHEDULE_ID"}.

DELETE https://api.sixtyfour.ai/schedules/{schedule_id}

Deleting a schedule does not affect the underlying workflow or its run history.

Example usage

curl -X POST "https://api.sixtyfour.ai/schedules" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflow_id": "WORKFLOW_ID",
    "name": "Daily lead refresh",
    "cron_expression": "0 9 * * *",
    "timezone": "America/New_York"
  }'

import requests

API_KEY = "YOUR_API_KEY"
BASE_URL = "https://api.sixtyfour.ai"
headers = {"x-api-key": API_KEY, "Content-Type": "application/json"}

response = requests.post(
    f"{BASE_URL}/schedules",
    headers=headers,
    json={
        "workflow_id": "WORKFLOW_ID",
        "name": "Daily lead refresh",
        "cron_expression": "0 9 * * *",
        "timezone": "America/New_York",
    },
)
response.raise_for_status()
schedule = response.json()
next_run = schedule["next_run_times"][0] if schedule["next_run_times"] else "not yet computed"
print(f"Created schedule {schedule['id']}, next run at {next_run}")

const API_KEY = "YOUR_API_KEY";
const BASE_URL = "https://api.sixtyfour.ai";
const headers = { "x-api-key": API_KEY, "Content-Type": "application/json" };

const response = await fetch(`${BASE_URL}/schedules`, {
  method: "POST",
  headers,
  body: JSON.stringify({
    workflow_id: "WORKFLOW_ID",
    name: "Daily lead refresh",
    cron_expression: "0 9 * * *",
    timezone: "America/New_York",
  }),
});
if (!response.ok) {
  throw new Error(`Failed to create schedule: ${await response.text()}`);
}
const schedule = await response.json();
const nextRun = schedule.next_run_times[0] ?? "not yet computed";
console.log(`Created schedule ${schedule.id}, next run at ${nextRun}`);

Pricing

Scheduled runs are billed the same as manual runs. See Credits & Pricing Guide for credit costs.

Errors

For error responses (400, 401, 403, 422, etc.), see Handling Errors.

Get Started

Intelligence API

Search API

Workflows API

Monitors API

Webhooks

Troubleshooting

Developer Tools

API Reference

Schedule definition

Create schedule

Example request

Example response

List schedules

Get schedule

Update schedule

Example request

Delete schedule

Example usage

Pricing

Errors

API Reference

​Schedule definition

​Create schedule

​Example request

​Example response

​List schedules

​Get schedule

​Update schedule

​Example request

​Delete schedule

​Example usage

​Pricing

​Errors

Schedule definition

Create schedule

Example request

Example response

List schedules

Get schedule

Update schedule

Example request

Delete schedule

Example usage

Pricing

Errors