Automate your scraps so they run on their own — no manual clicks, no cron tabs on your server, just set it and forget it.

Enabling a schedule

Open your scrap's Settings → Automation and toggle Schedule. Pick a preset frequency or enter a custom cron expression.

Preset frequencies

Preset	Cron expression	Good for
Every 5 minutes	*/5 * * * *	Real-time price tracking, stock alerts
Every 15 minutes	*/15 * * * *	News monitoring, social feeds
Every 30 minutes	*/30 * * * *	Marketplace listings
Hourly	0 * * * *	General-purpose monitoring
Every 6 hours	0 */6 * * *	Daily check-ins without overload
Every 12 hours	0 */12 * * *	Twice-a-day snapshots
Daily	0 0 * * *	Daily digests, reports
Weekly	0 0 * * 0	Weekly roundups

Presets receive a per-scrap jitter offset so runs are spread across the window instead of piling up at the top of the minute. The expression stored on the scrap is the canonical one; the runtime applies the offset transparently when dispatching.

Custom cron expressions

Need something specific? Enter any valid 5-field cron expression:

┌───────── minute (0-59)
│ ┌─────── hour (0-23)
│ │ ┌───── day of month (1-31)
│ │ │ ┌─── month (1-12)
│ │ │ │ ┌─ day of week (0-6, Sunday=0)
│ │ │ │ │
* * * * *

Examples:

• 30 9 * * 1-5 — weekdays at 9:30 AM
• 0 8,20 * * * — twice a day at 8 AM and 8 PM
• 0 0 1 * * — first day of every month at midnight

Timezone

Schedules run in UTC by default. Configure a timezone in Settings → Automation → Timezone to align with your local time. All standard IANA timezone names are supported (e.g. Europe/Paris, America/New_York).

Quota and subscription

Scheduling requires an active subscription with available quota. Each scheduled execution counts against your plan's run allowance. If your quota is exhausted, scheduled runs are paused until the next billing cycle or until you upgrade.

What happens on each run

1. The cron triggers the scrap at the scheduled time.
2. A worker executes the request script.
3. The result is stored in History with its status.
4. If configured, notifications are sent (email results, alerts).
5. If enabled, AI Digest summarizes the data and emails it.

All executions — manual, scheduled, and API-triggered — appear in the same History timeline.

---

See also: Notifications · AI Features · Scraping

Next step → Notifications