Monitor Website Changes Behind Login
To monitor a website behind login, capture the page through an authenticated browser session, store a meaningful baseline and compare later structured captures. Alert on changes that matter to the workflow rather than every visual difference.
For the category overview, see how structured browser state fits the category.
Use an authenticated browser session
Private dashboards and portals often depend on cookies, multi-factor authentication, device trust and interactive navigation. A separate crawler may stop at the login wall or create another session that behaves differently.
E2LLM works with connected browser tabs. The browser holds the established session, while the agent can discover the tab and capture its rendered state. The user remains responsible for access to the site and for keeping the session valid.
Define the monitored state
Choose the smallest page region that answers the operational question. Examples include:
- A ticket status and its last update.
- A supplier's inventory row.
- A deployment state in an internal dashboard.
- A policy or account setting.
- A balance, invoice state or renewal date.
Record the target, the expected page and the fields that constitute a meaningful change. This prevents navigation changes, timestamps and unrelated counters from producing noise.
Capture, normalize and compare
A monitoring run should:
- Find the expected authenticated tab or navigate to the target.
- Capture current structured state.
- Extract the monitored fields.
- Compare them with the stored baseline.
- Save the new state and notify only when the rule matches.
The scheduler, baseline storage, comparison policy and notification channel belong to the surrounding workflow or agent system. E2LLM supplies the current browser observation and actions needed to reach it.
Detect session and page failures
A login page is a state change, but usually not the business change being monitored. Detect expired sessions, access-denied pages, incomplete loads and unexpected navigation separately. Report them as collection failures so they do not overwrite a valid baseline.
Use a positive control during setup: change one known test value or monitor a page with a predictable update, then confirm the comparison produces an alert. A quiet monitor is trustworthy only after it has demonstrated that it can detect a real change.
Keep sensitive state bounded
Store only the fields needed for comparison. Review the data path and retention of the browser service and the monitoring system, especially for internal or regulated pages.
Example: watch a private order status
A workflow runs on a schedule and opens the order portal in an established browser session. It locates the order by its stable identifier, captures the status, expected delivery date and last update, then compares those fields with the prior baseline.
If the status changes, the workflow records both states and sends a notification with the order reference. If the session has expired, it sends a collection alert and preserves the previous baseline. The login page never becomes the new business state.
Common questions
Does E2LLM schedule the monitoring run?
The scheduler belongs to the agent or workflow system using E2LLM. E2LLM provides browser observation and actions when that system initiates the run.
Should I compare raw HTML?
Raw page comparisons often amplify timestamps, generated identifiers and unrelated layout changes. Extract and compare the fields that answer the monitoring question, while retaining enough context to investigate a real change.
What if no dedicated browser tab is open?
Define the operating procedure before launch. The workflow can use an established target tab or navigate an authorized connected tab, depending on the session and controls you choose. Treat absence of the required session as an explicit failure.
Copy this instruction into your monitoring agent
Use E2LLM to inspect this authenticated page.
1. Find the expected tab and confirm the page identity.
2. Capture current structured state.
3. Extract only these monitored fields: [list fields].
4. Compare them with this prior baseline: [provide baseline or reference].
5. Report each changed field with its old and new value.
6. Treat a login page, access denial, missing tab or incomplete load as a collection failure. Do not replace the baseline.
7. Return the new bounded baseline only after a valid capture.Build the underlying workflow with website automation that needs no API. For frequent checks, control recurring capture costs.