Groups, rules and exports

Schedules

A schedule starts the scrapers by themselves, so your data stays fresh without you pressing Run group. You set it once on the group. The group schedule then governs every scraper in it. A scraper whose group has a schedule shows “This scraper is scheduled by its group” and you change it from the group.

A scheduled run costs the same as a run you start by hand. It starts only if the wallet has a balance, see Wallet and billing. Upload scrapers are never scheduled, because they only read a file when you send one, see Upload a file.

The schedule here is for scraping. Matching has its own schedule, see Schedule and history. AI control has its own check rhythm, see AI control.

Open the 3-dots menu of the group box and pick Schedule.
Pick an Automation:
- No automation: the group has no schedule and each scraper decides for itself. With no schedule a scraper runs only when you start it.
- Daily: every day.
- Every N days: set Run every (days), 1 or more.
- Weekly (pick days): tick the days Mon to Sun. Pick at least one.
- Monthly: pick First day or Last day of the month.
Read the line Next run. It shows the day of the next run.
Press Save. The button says Save and run when it also starts a run now. Close leaves without saving.

To give one scraper its own schedule, open the 3-dots menu on its box, pick Schedule and choose the same options. This works only when the group is set to No automation. You can also use Schedule scraper after you have made a scraper, see Read a website.

The dialog sets days, not a time of day.

Base address https://portal.scrapewise.ai/api/scraper-api, header Authorization: Bearer <key>. Which key: a Read key looks, a Full key also changes things, see Read or Full.
With a Full key, set the group schedule: PUT /api/scraper/group/{id}/schedule with startType and scheduleDetails, and a new Idempotency-Key.
With a Full key, send startType NONE to switch the group schedule off. Each scraper then follows its own schedule.
Read the result with GET /api/scraper/group/list (Read). A group has startType, scheduleDetails and groupGovernsSchedule.
For one scraper, change config.startType and config.scheduleDetails and save the whole scraper with PUT /api/scraper (Full), see Read a website. The group value wins when the group governs.

bash

curl -X PUT "https://portal.scrapewise.ai/api/scraper-api/api/scraper/group/[GROUP ID]/schedule" \
  -H "Authorization: Bearer $SCRAPEWISE_FULL_KEY" \
  -H "Idempotency-Key: [NEW UUID]" \
  -H "Content-Type: application/json" \
  -d '{ "startType": "WEEKLY", "scheduleDetails": { "daysOfWeek": ["MONDAY", "THURSDAY"] } }'

`startType`	`scheduleDetails`
`NONE`	none. Turns the group schedule off
`DAILY`	none
`EVERY_N_DAYS`	`intervalDays`, 1 to 366
`WEEKLY`	`daysOfWeek`, at least one of `MONDAY` to `SUNDAY`
`MONTHLY`	`monthlyDay`, `FIRST` or `LAST`

The older call PUT /api/scraper/group/{id}/start-type/{startType} (Full) sets only the type MANUAL, DAILY, WEEKLY or NONE for every scraper. Use /schedule for the other choices and for the details.

Connect your assistant with a Full key. See Connect Claude.
Ask it to set the schedule: scrapewise_update_scraper_group_schedule (Full) with id, a new idempotency_key and a body with startType and scheduleDetails.
To switch it off (Full key), send startType NONE.
Ask it to confirm: scrapewise_get_scraper_group_list (Read) shows the schedule of each group.

json

scrapewise_update_scraper_group_schedule
{
  "id": "[GROUP ID]",
  "idempotency_key": "[NEW UUID]",
  "body": { "startType": "EVERY_N_DAYS", "scheduleDetails": { "intervalDays": 2 } }
}

An assistant should keep scrapers on manual until you ask for a schedule, and ask you first, because every scheduled run costs money. scrapewise_update_scraper_group_start_type (Full) is the older call for the type only.

Errors you may see

Enter a number of days (1 or more).

Every N days needs a number from 1 up. Over the API the limit is 366.

Pick at least one weekday.

A weekly schedule needs a day.

This scraper is scheduled by its group.

Change the schedule from the group menu. Set the group to No automation if the scraper should have its own.

402 on a legacy plan

Older accounts need the plan feature for the chosen rhythm. Accounts with a wallet have no such limit.

400 on save

The group was not found in your account, or the details do not fit the type.

Questions

What happens if my wallet is empty at run time?

The scheduled run does not start. Top up and the next scheduled run starts as normal.

Does a schedule run my upload scrapers?

No. Upload scrapers only change when you send a new file.

Can scrapers in one group have different schedules?

Yes, when the group is set to No automation. Each scraper then uses its own schedule.

How do I stop all schedules?

Pick No automation on the group and on each scraper, or send startType NONE for the group.

Everything on this screen

Schedule dialog:

Tue, Wed, Thu, Fri and Sat: the weekday ticks that go with Mon and Sun in the steps above.
Time and Timezone: where they show, they set the time of day for the start and the time zone it counts in.
Message “This scraper is scheduled by its group”: the scraper’s own schedule is locked. Change the group schedule instead, or set the group to No automation.
Message “Applies to every scraper in this group”: the group dialog says that its schedule covers all scrapers. No automation lets each scraper keep its own.

Group schedule on the data screen:

The group schedule window opens from the group menu. It applies to every scraper in the group. Choose No automation to let each scraper keep its own.
A scraper that follows the group schedule shows: This scraper is scheduled by its group. Change it from the group scheduler.
Mon, Tue, Wed, Thu, Fri, Sat and Sun: the days of a weekly schedule.
First day and Last day: a monthly schedule runs on the first or last day of the month.

Last updated 4 November 2026