A week of changes.
A clearer conversation.

Start with the conversation you need.

1. Open Reports & exports in your workspace.
2. Choose inclusive dates and a timezone, then optionally filter by label, review status or monitor name/URL.
3. On Pro and Business, review totals, label groups and up to 100 recent changes. Open any change to see the retained evidence.
4. Download the selected range, or save a separate weekly schedule below.

Totals cover every retained event in the selected range, including recorded changes that did not match an alert rule. Each event counts once in the total. Events with several labels appear in several groups, so adding group counts can overstate the total. Unlabelled events have their own group. Labels, names and review state reflect generation time, not a historical label or reviewer audit log.

Reports reuse cached AI summaries where available and otherwise describe deterministic captured changes. No new AI request or summary credit is used. A report can be useful with AI completely disabled. It never marks a change reviewed or changes notification state.

Your retained changes, ready for a spreadsheet.

CSV downloads are available on every plan. Use the Reports page to choose dates, or export the filtered Changes inbox for the previous seven complete UTC days. Exports include IDs, monitor name, source URL, labels, capture time, matching-rule status, current review time/reviewer, a bounded description, cached-summary flags, authenticated-capture flag and coverage metadata.

Up to 5,000 rows and 10 MiB per download; up to 10 export attempts per workspace per hour. A larger request asks you to narrow the range or label. Nothing is silently truncated. Empty results produce a header-only CSV. Full text snapshots and screenshot binaries are not embedded.

Files use UTF-8 with a BOM, quoted cells and CRLF rows. Formula-like source values are prefixed as spreadsheet text. This can add a leading tab to machine imports; use the existing JSON API for programmatic data where available. Re-editing and resaving files in another application can change its handling of formulas.

Downloads can contain private captured values and URLs. Store and share them with care. Exports respect workspace membership and current retention; revoking a connection or deleting history cannot recall a file already downloaded.

One weekly schedule. The right people.

1. An owner or admin enables weekly delivery.
2. Choose a day, time and timezone, and all labels or one label.
3. On Pro, select the owner’s email. On Business, select up to five current workspace members and/or connected Slack and Microsoft Teams destinations.
4. Save and check the next scheduled time. The notification worker prepares and sends the report on its next run after that time.

The reporting period is the seven complete local dates before the scheduled day. All review states are included. Preview filters above do not silently change the weekly schedule. Daylight-saving gaps use the next valid local minute; repeated hours use the first occurrence. At most one report is generated per workspace per local Monday–Sunday week; moving the schedule after a report was generated takes effect on a future week.

This opt-in schedule is separate from change emails, quiet hours and hourly/daily digests. Weekly emails do not consume the change-email allowance. Native-channel attempts, including retries, share the existing outbound delivery allowance. No new OpenAI credits are used. Zero-change reports still send and explicitly describe retained evidence.

Email uses the existing retry and idempotency system with a 23-hour retry window. Slack and Teams can deliver duplicates after ambiguous network failures. A worker outage resumes with the most recent scheduled week, without replaying every missed week. Changing or disabling the schedule cancels waiting deliveries; an already-dispatched message cannot be recalled.

Email recipients are checked again before sending. Removed members, changed email addresses, changed/disconnected channels, stale report settings and lost plan access cancel affected deliveries. Downgrading a team schedule to Pro disables it rather than redirecting private material to another recipient. Re-enable an eligible schedule explicitly after upgrading.

A useful export for everyone. A routine for paid teams.

Existing text/image storage limits also apply. Members can view reports and export any workspace history they can already access. Owners and admins manage schedules and recipients. Connecting or receiving a report does not grant access to the underlying workspace.

A working review, not a certified archive.

Only captured, still-retained events can appear. Failed checks, storage cleanup, deleted monitors and time-based retention can leave gaps. No returned changes is not proof that a site never changed. Review history and monitor health before drawing that conclusion.

Weekly emails include up to 12 highlights and eight label groups; channel cards contain aggregate counts and a report link. Totals cover the full selected range. Links open a live view, so later reviews or expiry can change what appears. Authenticated captured values are not embedded in weekly messages: sign in to review them. Members and channel participants can still see report counts, labels and monitor names. Connected channels may include people outside your workspace.

PageFluxer generates CSV without a permanent export object or extra screenshot copies. Weekly delivery uses bounded frozen messages in the existing outbox; completed delivery records follow its seven-day cleanup. Report run dates and counts are kept for 30 days. Reports do not extend source history or image retention. Delivered messages and downloads are external copies, unaffected by later deletion.

If a report does not arrive

Check the next scheduled time, current plan, recipient membership and channel connection. Open Notifications for sent, pending, failed or cancelled report deliveries and their safe error categories. The worker can be delayed by service capacity. An expired or deleted highlight cancels a frozen message instead of sending stale captured content. Use the live report and CSV while investigating; there is no automatic replay after the retry window.

The existing MCP summarize_changes tool remains an on-demand, paginated digest grouped by monitor. It does not create a weekly schedule. CSV downloads and report settings are signed-in web features; API tokens cannot call these session endpoints.

Include filtered changes in your review

Reports and exports include relevance-filtered changes by default. Choose the AI relevance filter in the report view to focus on filtered alerts, uncertain decisions or fallbacks. CSV adds the saved verdict, explanation and delivery permission. Weekly reports include filtered changes and never run a new AI evaluation. Rule matched and relevance permits alert do not establish provider acceptance. Understand relevance decisions →