Auto-start rules
PRO An auto-start rule watches the pages you open. The moment a page's address matches the rule's pattern, refreshing starts by itself â no popup, no Start button. Open your queue page, and it's already refreshing.
it finishes loading â đ¯ URL matches a rule
e.g.
*queue*
â
đ Refreshing startswith that rule's settings
No clicks needed â a matching address is enough to start the job.
Where to set them up
Auto-start rules are edited only in the web dashboard, on its Autostart Rules page â the popup has no editor for them. If you haven't opened the dashboard yet, see The web dashboard â it's one click from the popup, no account needed.
How patterns work
A pattern is just a piece of text compared against the page's full address. Two flavours:
- No
*in the pattern â "contains" match. The rule fires if the pattern appears anywhere in the address.example.commatches every page on that site. - With
*â wildcard match. Each*means "anything here", and the pattern is checked against the whole address.
Either way, capital letters don't matter â matching is case-insensitive.
| Pattern | Matches |
|---|---|
example.com/queue* | Any address containing example.com/queue followed by anything â the queue page and everything under it. |
*dashboard* | Any address with the word "dashboard" anywhere in it, on any site. |
Each rule carries its own settings
A rule isn't just a pattern â it holds a complete refresh setup of its own, edited right inside the rule using the same Refresh and (optional) Monitor sections you know from the rest of the dashboard: interval, refresh options, keywords, match actions, everything. So your queue rule can refresh every 30 seconds and watch for "new ticket", while your status-page rule refreshes every 5 minutes with no monitoring at all. Rules don't touch your normal defaults.
Each rule also has its own Enabled switch, so you can pause a rule without deleting it.
Exactly when a rule fires
A rule starts refreshing when all of these are true:
- a normal web page (
http/https) finishes loading, - its address matches the rule's pattern,
- no refresh job is already running on that tab (a rule never interrupts or replaces one), and
- the rule is enabled and your install has PRO.
The address matched example.com/queue* â so the page started refreshing on its own the moment it loaded.
A real example
- Open the dashboard's Autostart Rules page and add a rule.
- Pattern:
work.example.com/queue*. - In the rule's settings, set a fixed 30-second interval and a monitor keyword like
new ticketwith a notification. - Save. From now on, whenever you open the queue â first thing in the morning, after lunch, on any computer synced to this install â it's already refreshing and watching.