# Scheduled Actions — Schedule the Outcome, Not the Busywork

Source: https://mcpscraper.dev/scheduler

Scheduling

# One place for the work that should keep happening.

Schedule bounded connected-data work with explicit account access, spend controls, and durable results.

Open scheduled actions Explore connections

mcpscraper.dev/scheduled-actions

Available today: scheduled provider syncs and bounded agent work with durable run results.

75 credits per started run

1.5× OpenRouter-reported model cost

15,000 Credits per active connection / month

367 tools in the unified MCP catalog

Available today

## Monitor. Compare. Act. Remember.

Current scheduled work includes model-free connected-data syncs and stored agent jobs. Agent mode receives a reviewed web and memory subset plus only its bound provider tools.

### Monitor

Re-run searches, pages, reviews, conversations, or connected-account reports on a cadence and keep a dated result from every execution.

### Compare

Read previous rows or notes, then record movement, additions, removals, or a concise change report.

### Act

Publishing and messaging actions fail closed unless the account switch is on and that exact mutation is granted to the schedule.

### Remember

Send narrative reports to a vault and recurring measurements to a table so future work starts with context.

Available today · Resend reconciliation

## Download the operating history. Keep sending separate.

A Resend sync is model-free: it pages six approved datasets, checkpoints progress, deduplicates raw records, detects changes, and mirrors the bounded result into the selected vault. A send or delete still requires agent mode, the account action switch, and an exact tool grant.

Available today · deterministic data pulls

## One occurrence. One scheduled event.

Each occurrence performs a bounded provider slice and stores an exact continuation when more history remains. Internal provider pages do not create extra 75-Credit base events, but measured proxy requests and compute remain visible usage units.

Each active Nango connection costs 15,000 Credits/month from your balance. Connected work debits 2 Credits per function run, 2 per provider proxy request, and 5 per compute-second, prorated from aggregate milliseconds. The scheduler calls model-free provider adapters directly for supported Gmail, Calendar, Search Console, Zoom, GitHub, and Resend datasets. Search Console rows are stored for later filtering; API-only batches do not write a database.

Available today · actual details

## Control is part of the scheduling primitive.

- **Cadences:** One time, daily, weekly, or monthly, with a stored time and timezone.
- **Run price:** 75 Credits per started occurrence. Connected work also uses 2 Credits per function run, 2 per provider proxy request, and 5 per compute-second, prorated from milliseconds. Deterministic syncs add no model charge; agent mode adds 1.5× OpenRouter's reported model cost.
- **Monthly quota:** None. Scheduling is included with every paid plan and uses the same Credit balance as the rest of MCP Scraper.
- **Connections:** Up to 20 exact account connections can be attached to one schedule. Each active Nango connection is a separate 15,000-credit/month add-on.
- **Current controls:** Pause, resume, or delete a schedule. Existing schedules are not edited in place today.
- **Default delivery:** Results and run status are written to Memory. Messages require an explicitly granted Gmail, Slack, or Resend action.

Available today · scheduled connected work

## Give the recurring work a permanent owner.

Create a schedule, bind only the account access it needs, and keep each run result available for review.

Open scheduled actions