# 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 today. The proposed Scheduling rebuild brings reminders, assistant jobs, Gmail, Calendar, Zoom, saved browser logins, confirmations, approvals, and results into one governed plan.

Open scheduled actions Explore connections

mcpscraper.dev/scheduled-actions

“summarize GA4 and YouTube performance every Monday”

Execution path Scheduled Action → selected GA4 + YouTube reads → Projects vault

Google Analytics YouTube reads only

Conversions 184 +12% week over week

Video views 42.8k 3 videos published

Filed to Projects 2026-W28 marketing pulse

Selected account reads and the resulting report are stored with the run status in Memory.

Available today: scheduled provider syncs and bounded agent work. Proposed rebuild capabilities are labeled throughout this page.

75 credits per started run

1.5× OpenRouter-reported model cost

15,000 Credits per active connection / month

369 tools in the unified MCP catalog

Proposed · personal assistant

## Describe the outcome once. Review exactly how it will happen.

The rebuild is designed to make Scheduling the single setup and management surface. Assistant is the capability behind interpretive work—not a second automation product the user has to understand.

1. Describe the outcome
   Choose a deterministic Reminder or an interpretive Assistant job, then state what should happen and when.
2. Connect exact context
   Select Gmail, Calendar, Zoom, a destination vault, or a named saved login—not an undifferentiated account pool.
3. Review readiness
   Check timing, account health, destination, model use, spend ceiling, exact grants, and any required Approval.
4. Confirm accepted state
   Activation re-checks the plan server-side and reads the accepted revision back before showing Scheduled.
5. Receive a Result
   The job stores progress and its result—or pauses in Needs attention with a safe Watch, Take over, reconnect, or approve step.

Proposed · connected context

## Gmail, Calendar, and Zoom can become one working brief.

Each Connection stays owner-bound and each schedule receives only its reviewed tools. Connecting an account does not silently grant every read or action. Sending, publishing, and other writes still require explicit authority.

### Morning operating brief

Review approved Gmail, Google Calendar, and Zoom activity, then place a prioritized brief in the selected vault.

Every weekday at 7:30, prepare my day from Gmail, Calendar, and Zoom

### Meeting follow-through

Compare a Zoom result with the calendar event and approved inbox context, then surface follow-ups for confirmation.

After my client calls, draft the follow-up tasks and ask before sending anything

### Simple reminder

Deliver a stored message at the right time without a model call or browser authority.

Remind me to call Sam at 3 PM

### Saved-login work

Use one exact saved login for a bounded site task while unrelated logins in the same browser profile remain outside the grant.

Check the approved client portal every Friday and store what changed

Proposed · browser access

## One assistant browser. Many saved doors.

A Browser profile is the durable environment. Each Saved login is a separate named binding with its own health and identity.

Exact login grants

A job receives the saved login, domain, and action it needs—not blanket access to the profile.

Kernel hosted

Kernel is the intended multi-user hosted runtime. Tenant-safe namespacing and denial proofs remain release gates.

Private Mac

The optional Mac adapter is designed for one configured owner or a deliberately private installation, never unrelated customers.

Codex browser

The Codex browser can help with manual setup or debugging, but it is not a current dependency of unattended Scheduling.

Proposed · confirmation and supervision

## A verified commitment, not scheduled hope.

Before activation, Scheduling is designed to re-check account and login health, timing, destination, model use, spend, exact grants, and Approval policy. It then reads the accepted revision back before showing success. That proves readiness at confirmation time, not permanent provider availability.

Watch

### Read-only and short-lived

A proposed owner-authenticated viewing lease resolves the hosted live view just in time. Raw provider links are not sent by message.

Take over

### Control only when the human step requires it

A separate proposed control lease expires, the session is deleted at its deadline, and only the matching paused run may resume.

Needs attention

### A useful pause, not a vague failure

Expired authentication, missing approval, or a blocked prerequisite names the problem and offers reconnect, approve, Watch, or Take over.

Result

### Progress and outcomes remain durable

Completed work, accepted revision, provider errors, and next steps stay attached to the schedule instead of disappearing into a success toast.

Proposed · two execution types

## Use intelligence only where judgment is required.

A Reminder is deterministic and forbids model use and browser grants. An Assistant job names its model, context, authority, approvals, destination, and maximum spend. This is not an AI call wrapped around every timer.

Reminder

### Predictable delivery

No model No browser

Stored message · time · timezone · destination

Assistant job named model only when interpretation is required

plus

Context exact connections + saved logins

and

Authority bounded approvals + spend ceiling

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

### Keep watch without reopening dashboards

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

Compare

### Turn repeated observations into history

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

Act

### Use only an explicitly enabled write

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

Remember

### File the result where the next agent looks

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.

Connected account Resend · Production official OAuth grant

Six datasets

### Sent email · inbound email · logs · contacts · broadcasts · templates

Request logs are the available delivery audit trail; the official MCP does not expose a separate delivery-event history reader.

Bounded occurrence

### 30 provider calls

Each list request asks for 10 records. Oversized individual records stop at 96 KiB, and exact cursors resume unfinished work.

Separate authority

### 33 reads · 45 gated actions

Credential, OAuth-administration, raw editor-session, and secret-creating tools remain blocked from the scheduler and external MCP bridge.

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.

America/Denver

### Operations data pull

08:00 12:00 16:00

Gmail · Google Calendar · Search Console · Zoom · GitHub · Resend

Scheduled occurrence 1 75-Credit base

plus

Provider pages measured 2 Credits / proxy request

and

Function work measured runs + compute milliseconds

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.

The browser manager handles read grants today. Gated write grants are available through the MCP/control API and require both the account switch and the exact action name.

- **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 current schedule now. The unified personal-assistant setup, saved-login controls, readiness confirmation, and supervised takeover described above remain proposed until their implementation and security gates pass.

Open scheduled actions