Schedule browser tasks to run automatically

Scheduled browser automation normally means standing up infrastructure: a machine, a headless browser, a way to store credentials, and a maintenance burden every time the target site changes. For a recurring personal task, that is an enormous amount of machinery for a job that takes ninety seconds by hand.

Replayo schedules the macro where you recorded it — in your own browser, in your existing logged-in session.

Schedule options

• Every 30 minutes — for things that change through the day: a queue, a live count, a status.
• Hourly — the middle ground for monitoring during working hours.
• Daily at a set time — the morning report pull, the 9:00 AM revenue check, the end-of-day update.

How to schedule a macro

1. Record the task once — open Replayo, press Record, do the task, stop.
2. Optionally pick a value to capture while recording, so each run emails you the result.
3. Open the macro's schedule and choose every 30 minutes, hourly, or daily at a time.
4. Save the schedule. That is the whole setup — no cron syntax, no runner, no credentials to store anywhere.

Why running locally is often the right trade

There is a real trade-off here, and it goes both ways.

What you gain

• No credential handling. The macro uses the session you are already signed into — nothing to store in a secrets manager.
• No bot friction. It is your real browser doing what you would have done manually.
• Nothing to maintain. No container, no runner, no scheduler service.
• Data stays local. Macros and schedules live in your browser's extension storage.

What you give up

• Your browser has to be running when the schedule fires. A laptop that is closed does not run macros.
• No high-frequency polling — 30 minutes is the shortest interval.
• No cloud fleet — this is one browser, not a farm of them.

For a daily 9:00 AM report pull on a machine you are sitting at anyway, that trade is almost always worth it.

Good candidates for a schedule

• A price or metric you check every morning.
• A report you export on the same day each week.
• A stale-session or queue cleanup in an admin panel.
• A standing entry whose values never change.

Frequently asked questions

Do scheduled macros run when my browser is closed?

No. Replayo runs macros inside Chrome, so the browser needs to be running when a scheduled run fires. That is the trade for not needing a server or stored credentials.

What schedule intervals are available?

Every 30 minutes, hourly, or daily at a time you choose.

Do I need to be logged into the site for a scheduled run?

The macro uses your existing browser session, so if you are still signed in it just works. If the site logs you out, either record the login into the macro or re-authenticate before the run.

Will I know the macro ran?

If the macro includes a capture step, each run emails you the captured value — which doubles as confirmation that the run happened and what it found.