Get the page ready.
Then watch what matters.
Open a filter, enter a public search term, choose an option, then capture the result. The same sequence works with content monitoring and visual pixel comparisons.
Record once in Chrome.
- Open the public page where your sequence should begin. Click PageFluxer and choose Record steps.
- Use the page normally: open a menu, enter a public search term, change a filter. Recording performs these actions on the real site. Avoid account actions, purchases, and private information.
- Choose Stop recording in the page badge or side panel. Select the resulting content you want to watch, or choose visual monitoring.
- Continue in PageFluxer. Sign in there if needed, review the recorded values and test the cloud capture before saving.
Recording is explicit, limited to the clicked tab, and stops after five minutes or when it cannot continue safely. Same-origin navigation can continue; a different origin, another tab, frames and shadow DOM are unsupported. The original URL stays the starting point for every check.
Keep the simple path simple.
No steps are required for an ordinary monitor. For a page that needs preparation, open Page loading & steps. Edit recorded values, reorder or remove actions, or add steps manually using CSS selectors. Use Test loading & steps to capture the result.
PageFluxer runs your sequence first, then applies your existing extra wait, lazy-loading scrolls and readiness selector, then captures the selected content or image. Loading scrolls return to the top; an explicit recorded scroll can trigger lazy loading. Visual capture returns to the top for consistent screenshot coordinates. Each test uses one preview attempt, and each scheduled run uses one Browser check regardless of the number of steps.
The cloud uses a fresh browser session every time. Your extension selection is retained, but login sessions and cookies are not imported. A successful test becomes the baseline when you save. Editing a recipe requires another test and creates a quiet new baseline, preserving retained history.
A small, predictable action set.
| Action | What it does |
|---|---|
| Click | Click one visible element. Useful for menus, tabs and filters. |
| Enter text | Replace a public input’s value. Up to 500 characters; passwords, uploads and sensitive fields are blocked. |
| Choose option / set checkbox | Select one native option by its value, or explicitly check/uncheck a checkbox. |
| Press key | Enter, Escape, Tab, ArrowDown or ArrowUp. The recorder captures Enter in a text input; other keys can be added in the editor. |
| Wait for element | Wait for one visible element before the next action. Add this in the editor for delayed controls. |
| Scroll | Scroll the page 1–1,800 pixels up or down. Add explicit scrolls in the editor; ordinary scrolling is not automatically recorded. |
Selectors must identify exactly one visible element. Supported CSS is the same bounded subset as monitor selections, including nth-of-type. Arbitrary scripts and executable snippets are never accepted.
Included with Browser access.
| Plan | Steps per monitor | Availability |
|---|---|---|
| Free | 5 | Within the existing one-time Browser trial |
| Starter | 10 | Within your Browser check allowance |
| Pro | 20 | Within your Browser check allowance |
Steps do not add separate monthly charges or extend the Browser trial. On downgrade, monitors whose recipes exceed the new limit pause; shorten the sequence and test it before resuming. Normal monitor, image-storage and check limits still apply.
Public pages, with clear boundaries.
Replay supports public GET requests and same-origin navigation. A public search form that navigates with a GET request can work. A search or filter that requires POST requests cannot work in this release. Login flows, supplied cookies, payments, file uploads, downloads, CAPTCHA solving, other origins, frames and shadow DOM are unsupported.
Steps have a shared 12-second replay budget, with up to 2.5 seconds per action, or 5 seconds for an explicit wait-for-element step. They share the existing 25-second overall capture deadline, request and transfer limits with page loading and screenshots. More steps do not increase those limits. A POST request during a step—including a site’s tracking request—can stop replay; simplify the recipe if this happens.
RECORDED_STEP_FAILED identifies the step number and a safe reason. Review its selector or value, add a wait for a delayed element, and test again. PageFluxer never silently skips a failed step: the last successful baseline remains, and the failed capture does not create a change alert.
Entered values are configuration, not encrypted secrets. They are saved with the monitor and can appear in setup drafts, authenticated API responses and image metadata. Do not put credentials, personal data or tokens in a recipe.
One recipe across extension, app and API.
Pro API clients can send capture_controls.steps in a Browser preview and then save using that preview. The server enforces the same plan limits and tested-capture requirements. Visual creation remains in the web app; API clients can read visual monitors and their saved controls. AI suggestions are currently available in the web setup flow.
{
"load_mode": "browser",
"capture_controls": {
"steps": [
{
"action": "fill",
"selector": "#search",
"value": "senior engineer"
},
{
"action": "press",
"selector": "#search",
"value": "Enter"
},
{
"action": "wait",
"selector": "#results"
}
]
}
}