Auto refresh a page and click a button
A common job: reload a page every so often and press a button once it is there — "Check again", "Load new items", "Claim slot". A LoopClicker scenario can do this, carrying on across reloads on that one site.
Step by step
- Open the page and start a new scenario for this site with Record, or on LoopClicker's Scenarios page.
- Add a Reload page step. It reloads the page, waits for it to load and carries on where the page was scrolled to.
- Add a Wait step long enough for the button to appear, or with Pro a Wait until step that waits for it.
- Add a Click step on the button you want pressed after each reload.
- Set the loop to ∞ with a pause between passes, such as 60 seconds, and allow this one site when Chrome asks: the scenario needs it to carry on after the reload.
- Press Run. Esc stops it.
Want to try it first? The test page has buttons, a click area, a form and more to practise on — nothing on it is sent anywhere.
Why it asks for the site
A reload ends everything running in the page, LoopClicker's part included. To pick up at the next step once the page is back, LoopClicker needs permission for that one site; it asks only when the scenario first needs it, and you can remove it in Chrome's extension settings.
Only click once the text is there (Pro)
If the button shows up only sometimes, a Reload until step reloads until a text or an element appears and only then goes on to the click — see reload a page until text appears, then click.
Every N minutes, even with the tab closed (Pro)
With Pro, a schedule runs the scenario at set times or every so many minutes. If no tab of the site is open, LoopClicker opens one at the scenario's start address first — which loads the page fresh each time.
What it cannot do
- If your session on the site expires, the button may no longer be there; the run stops with an error rather than clicking something else.
- Keep the pause between passes reasonable. Reloading a site many times a minute can break its rules and get your access limited.
- Without the site permission the scenario stops at the first reload — on purpose, so nothing runs on a site you have not allowed.
Checked against LoopClicker on .