Scheduling Runs - Extralt Docs

A schedule automates recurring extractions. You link a schedule to a robot with a cadence, and Extralt automatically creates runs at the specified interval.

Creating a schedule

• Dashboard

Navigate to Extract > Schedules and click New Schedule.

Select the robot to use
Set the cadence (e.g. every 1 day, every 6 hours, every 1 week)
Optionally provide start URLs and a budget
Click Create

A name is auto-generated based on the cadence and robot (e.g. "Daily example-store.com run"). You can customize it.

New schedule form showing robot selector, cadence editor, URL input, and budget field

• API

export EXTRALT_API_KEY="your-api-key"

curl -s -X POST "https://api.extralt.com/v1/extract/schedules" \
  -H "Authorization: Bearer $EXTRALT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "robot_id": "your-robot-id",
    "cadence": {
      "interval_amount": 1,
      "interval_unit": "day"
    },
    "start_urls": ["https://example-store.com/products"],
    "budget": 50
  }' | jq

The response is 201 Created with { "id": "<schedule_id>" }.

Parameters

Parameter	Required	Description
`robot_id`	Yes	The robot to use for extraction
`cadence.interval_amount`	Yes	Number of intervals between runs (e.g. 1, 6, 12)
`cadence.interval_unit`	Yes	`hour`, `day`, `week`, or `month`
`name`	No	Display name (auto-generated if omitted)
`start_urls`	No	URLs to crawl. Must match the robot's host.
`budget`	No	Maximum URLs to extract per run. Each URL costs 1 credit.
`auto_enrich`	No	If `true`, automatically run enrichment after each scheduled run. Defaults to `false`.

Cadence options

Schedules support flexible cadence intervals:

Example	interval_amount	interval_unit
Every hour	1	`hour`
Every 6 hours	6	`hour`
Daily	1	`day`
Every 3 days	3	`day`
Weekly	1	`week`
Monthly	1	`month`

Managing schedules

• Dashboard

Navigate to Extract > Schedules to see all your schedules in a table.

Schedules list showing active and paused schedules

The table displays:

Column	Description
Name	Schedule name
Robot	Which robot the schedule uses
Cadence	How often the schedule runs
Status	Active, Paused, or Paused (no credits)
Next run	When the next run will be created
Last run	When the last run was created

Actions available:

Pause / Resume: toggle the schedule on or off
Edit: change the name, cadence, start URLs, or budget
Delete: remove the schedule permanently

• API

# List schedules
curl -s "https://api.extralt.com/v1/extract/schedules" \
  -H "Authorization: Bearer $EXTRALT_API_KEY" | jq

# Update a schedule (returns 204 No Content)
curl -s -X PATCH "https://api.extralt.com/v1/extract/schedules/$SCHEDULE_ID" \
  -H "Authorization: Bearer $EXTRALT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "cadence": { "interval_amount": 1, "interval_unit": "week" } }'

# Delete a schedule (returns 204 No Content)
curl -s -X DELETE "https://api.extralt.com/v1/extract/schedules/$SCHEDULE_ID" \
  -H "Authorization: Bearer $EXTRALT_API_KEY"

The PATCH body accepts any subset of the create fields: cadence, name, robot_id, budget, start_urls, auto_enrich.

The list/read response shape uses camelCase and nests the run config: { id, name, robotId, robotName, enabled, cadence: { intervalAmount, intervalUnit }, config: { startUrls, budget, ignoreRobotsTxt }, nextRunAt, lastRunAt, ... }.

Pausing and resuming

You can pause a schedule at any time. A paused schedule stops creating runs until resumed.

• Dashboard

Click the Pause or Resume button on any schedule in the list.

• API

# Pause
curl -s -X POST "https://api.extralt.com/v1/extract/schedules/$SCHEDULE_ID/pause" \
  -H "Authorization: Bearer $EXTRALT_API_KEY"

# Resume
curl -s -X POST "https://api.extralt.com/v1/extract/schedules/$SCHEDULE_ID/resume" \
  -H "Authorization: Bearer $EXTRALT_API_KEY"

Credits and auto-pause

Scheduled runs consume credits the same way as manual runs: 1 credit per URL extracted.

If your organization runs out of credits, all active schedules automatically pause. They show a Paused (no credits) status in the dashboard.

When credits become available again (through purchase or billing cycle), you can resume schedules manually. Schedules do not auto-resume.

See Credits & Billing for more on credit management.

Concurrency

If a schedule's previous run is still active when the next run is due, the schedule skips that execution and waits for the next interval. This prevents overlapping runs from the same schedule.