Scheduled Automations are available in Your Rapport version 0.20.0. Scheduled Automations in Your Rapport will collect web pages when you specify. There are many ways to configure the automations to run within different intervals.
Scheduled Automations in Your Rapport turn your browser into a repeatable collection engine: you pick a URL, choose when you want it collected (autocollect vs “deep save”), and set a schedule so Your Rapport can revisit that page and preserve it over time. This is a big deal for web scraping workflows (collecting content across many URLs at consistent intervals) and data archiving (building a time-series record of a page as it changes). Your Rapport already leans into automation—its bulk collect workflow lets you “provide a list of URLs to scrape” so you can collect at scale without babysitting each page.
Why scheduling matters for archiving and scraping
Manual collection is fragile: you remember the important pages until you don’t, and you revisit them at inconsistent times. A scheduled job fixes that. It helps you:
- Build a timeline: capture the same page daily/weekly so you can compare what changed later.
- Reduce missed windows: some content appears briefly (limited-time notices, updates, edits, removals).
- Standardize collection cadence: scrape lists of URLs with consistent timing for cleaner downstream analysis.
- Scale your effort: let the browser do the repetitive “check + capture” while you focus on interpretation.
Cron schedules: expressive, compact, and familiar
Your Rapport schedules automations with crontab-style syntax, the classic 6-field format:
second minute hour day-of-month month day-of-week
A few examples you can drop directly into Your Rapport:
- *
* * * * *→ every minute * 0 * * * *→ at the top of every hour* 0 9 * * 1-5→ 9:00 AM, Monday–Friday* 0 11 * * *→ 11:00 AM every day (a nice default for daily archiving)
Powered by cron-parser
Under the hood, scheduled automations rely on the cron-parser library to interpret cron expressions, calculate upcoming run times, and handle tricky cases like time zones and daylight saving transitions. This is important because “cron-like” scheduling seems simple until you hit DST boundaries, skipped hours, or ambiguous local times—cron-parser is built to deal with those realities. Learn more at, https://github.com/harrisiirak/cron-parser
Why running scheduled automations locally beats many commercial solutions
A lot of hosted automation tools look great until you try to collect content behind logins, paywalls, MFA flows, or organization SSO. Your Rapport runs scheduled automations locally in your own browser, which means it can access the same authenticated sessions and page state that you can—no extra “headless cloud browser,” no brittle re-auth hacks, and no blocked content simply because a remote service can’t log in. Your Rapport is designed so collected content “stays on your machine,” leveraging the browser’s security model and your existing access.