Start with the decision, then the page
A clear monitoring request says what page matters and what would make an update useful. “Watch this page” can mean a changed paragraph, a new listing, a lower price or a different image. Give Flux one concrete goal before adding another.
For a source you are authorized to monitor, try: “Help me monitor example.com/product for a price below 80 CAD using PageFluxer Cloud.” The address is illustrative; replace it with your permitted source. Flux can suggest a below-price rule, but only the fresh capture can establish which offer and amount the monitor will read.
Open Ask Flux, choose AI mode, sign in and review the sharing choice. If you prefer to choose settings directly, use Set up a monitor without sending an AI message.
Treat the suggestion as the beginning of setup
Check the address and method
Use PageFluxer Cloud for checks that continue when your computer is off. Choose PageFluxer Local when the supported workflow belongs in your approved Chrome profile. Visual comparisons use Cloud Browser.
Read the alert rule
A decrease and a crossing below a budget are different rules. Confirm the amount and currency. Leave an unknown field unfinished and resolve it in setup instead of guessing.
Open Review setup
PageFluxer Cloud saves a setup draft, then opens the normal wizard. No monitor is active yet. Owners and admins in the same workspace can resume the draft, which expires after 30 days without another save.
Confirm a fresh capture
Select the correct content or offer, inspect the preview, choose schedule and notifications, and confirm the monitor. A suggestion cannot establish that the source is accessible or that a price is correct.
For PageFluxer Local, the page and goal carry into the existing preparation form. Choose the detailed rule and browser there, then test and confirm in the extension. Keep Chrome running on an awake computer for later checks.
Separate setup, successful checks and delivery
After saving, use the first-monitor checklist and monitor details to confirm a later successful check. A baseline alone is not the complete workflow. Follow the practice alert guide if you want to verify a known change end to end.
| Question | What to share | What still needs verification |
|---|---|---|
| Is this monitor paused? | Select that monitor’s status | Check the snapshot timestamp and current details |
| Which monitors need setup? | Workspace totals | Open the dashboard to identify the individual monitors |
| Why did my alert not arrive? | Optional monitor status | Inspect matching history, delivery logs, schedules and allowances |
| What changed in this private page? | Keep the captured content out of chat | Read the retained evidence in monitor details |
Keep the next action small
When the status shows an error, ask Flux where to look next. It does not receive the raw error message, browser-contact records or the source page, so it should guide verification rather than invent a cause. Its sources link to capture, website-access and notification workflows.
Use New chat or change context before discussing another monitor. Navigation and refresh clear the chat; saved drafts stay available in Settings → Setup drafts. Read the full Flux documentation for data sharing, role permissions and allowances.
Common questions
Does asking Flux create a running monitor?
No. Asking can produce a suggestion. Review setup prepares a draft or opens PageFluxer Local setup; the normal fresh preview and final confirmation are still required.
Can I use Flux with extension 0.4.7?
Yes. Flux uses the website’s existing PageFluxer Local preparation flow. Published extension 0.4.7 remains compatible, with no new extension permissions or installation required.
What if the AI allowance is used up?
Find guidance, the manual setup card and ordinary dashboard remain available. Included AI Credits reset monthly; purchased credits carry forward. Daily/monthly spending limits also apply. Normal monitoring allowances remain separate.