# Scheduled runs API

Source: https://neondeerdata.com/docs/api/scheduled-runs/

Schedule Attio records into workflows and manage the runs your connection controls.

## Access

This API requires alpha access. The connection needs the relevant scheduling permissions and access to the intended Attio workflow. Read [available workflows](https://neondeerdata.com/docs/api/scheduled-runs/workflows/) before scheduling anything.

## Schedule a batch

Read the target workflow and use its ID, target version, and `workflow_version_id`. Choose the records, scheduled time, and time zone, then [create a batch](https://neondeerdata.com/docs/api/scheduled-runs/batches/). If the workflow changed after your read, inspect it again before trying to schedule the records.

A scheduled batch starts that workflow once for each record. This can trigger the workflow's emails, updates, and other actions in Attio. Confirm the workflow, records, and time before creating it.

Use the returned operation and batch state to follow progress. Scheduling a record is not confirmation that its Attio workflow completed successfully.

## Move, cancel, or transfer work

[Batch operations](https://neondeerdata.com/docs/api/scheduled-runs/batches/) can change a pending batch's time, cancel it, or transfer control to another key with the required access. A key that can read a batch does not automatically control it.

Use [run and record cancellation](https://neondeerdata.com/docs/api/scheduled-runs/runs/) for individual records. Record-wide cancellation first needs its cancellation-control response; pass the versions it returns. Canceling pending work does not undo an Attio workflow that has already started.

## Automations task setup and failures

The [Automations endpoints](https://neondeerdata.com/docs/api/automations/) repeat the existing app's task setup and inspect reported failures.