How to auto click a button in Chrome

Chrome has no built-in setting to auto click a button on a repeating timer. In Tab Automation, Pick on page one button, add Click Element, set Repeat, and click Start.

That click is one control you chose. It is not an autoclicker that presses every match on the page. You can also paste a console script for a quick experiment, but that script dies if the click leaves the page.

Set up a repeating click in the side panel

1. Open the tab that holds the button — a queue Refresh, a Load more control, or another page you leave running.
2. Open Tab Automation from its toolbar action. The extension opens in Chrome’s side panel.
3. Click New Automation and pick the open tab. It becomes the Start card.
4. Click Add Step, then choose Click Element.
5. Click Pick on page, then click that one button. The picker writes the selector. The eye button highlights the match.
6. If the selector matches more than one control, use Which match to use and choose This one.
7. Configure Repeat at the End block. A new automation starts with a 30-second Fixed wait. You can choose No wait, Fixed, or Random range, in seconds from 0 to 3600 where allowed.
8. Click Start.

The graph runs, clicks the picked button, reaches Repeat, waits, and begins the next cycle. Pause stops the current run until you Resume it. Remove Automation deletes it.

Repeat can also stop after a set number of cycles or after a duration. Turn Repeat off when you want the graph to run once. The End block controls another cycle; it does not click the button by itself.

Auto click without an extension

For a temporary test, open DevTools, select Console, and paste:

setInterval(() => document.querySelector("button").click(), 30000);

The delay is 30,000 milliseconds, or 30 seconds. Change "button" to a selector that matches the control you want.

That timer dies if the click leaves the page. A navigation or reload replaces the document. The new page does not have your interval. You paste it again, or you stop using the console for a click you wanted to leave running.

Hidden tabs add another limitation: Chrome can throttle page timers. An extension timer lives outside the page, so it can click the assigned tab after you switch away. See auto refresh a background tab for discarded versus hidden tabs.

Reload, then click

Some pages need a fresh load before the button is safe to press.

1. Add Refresh Page first.
2. Add Wait / Delay as a Delay so charts or the queue can finish painting.
3. Add Click Element for the button.
4. Leave Repeat on so the graph starts again after the wait.

This still clicks one picked control on the assigned tab. It does not open every link in the window. Walking a list of URLs is For Each Link on Page.

A wait shorter than the page’s load time can click before the button is ready. The dashboard guide covers matching a wait to load time.

Hover, double-click, or right-click

Click Element can also Hover, Double-click, or Right-click. Hover sends enter events on the picked node and does not click. It does not move the real pointer. It does not put the page into the CSS :hover state, so a CSS-only dropdown stays closed.

Use hover, then a second Click Element, when a page script reveals the real button after enter events.

Limits to know before you start

• Chrome must stay open. Extension alarms do not fire after you quit Chrome. Running automations are rescheduled when Chrome starts again.
• A missing button fails the click. Click Element waits about six seconds, then records a failure in Activity. It does not treat a miss as a successful click.
• You pick one control. Tab Automation does not click every link in the window. One automation stays on one assigned tab.
• A click does not keep a login alive by itself. If the site ends the session, the next click can fail. Check Activity instead of assuming the button is still there.
• Some tabs cannot be automated. Chrome UI pages, extension pages, and the Chrome Web Store are excluded.
• Browser support is limited. Desktop Chrome, Edge, Brave, and Opera can install the Chrome Web Store listing. Firefox, Safari, and mobile are not supported.

Automations stay in chrome.storage.local on this computer. Read the privacy policy for permissions and data handling.