Actions108
- AI Visibility Actions
- List Sources
- Search
- Agentic Search
- AI Visibility Search
- AI Visibility Sources
- Browser Task
- Control Monitor
- Crawl
- Create Monitor
- Delete Session
- Get Monitor Changes
- List Monitors
- List Sessions
- Map
- Scrape URL
- Wire: Browse Catalog
- Wire: Discover Actions
- Wire: List Identities
- Wire: Request New Action
- Wire: Run Read Action
- Wire: Run Write Action
- Wire: Sign In
- Browser Actions
- Delete Session
- List Sessions
- Run Task
- Agentic Search
- AI Visibility Search
- AI Visibility Sources
- Browser Task
- Control Monitor
- Crawl
- Create Monitor
- Get Monitor Changes
- List Monitors
- Map
- Scrape URL
- Search
- Wire: Browse Catalog
- Wire: Discover Actions
- Wire: List Identities
- Wire: Request New Action
- Wire: Run Read Action
- Wire: Run Write Action
- Wire: Sign In
- Monitor Actions
- Control
- Create
- Get Changes
- List
- Agentic Search
- AI Visibility Search
- AI Visibility Sources
- Browser Task
- Control Monitor
- Crawl
- Create Monitor
- Delete Session
- Get Monitor Changes
- List Monitors
- List Sessions
- Map
- Scrape URL
- Search
- Wire: Browse Catalog
- Wire: Discover Actions
- Wire: List Identities
- Wire: Request New Action
- Wire: Run Read Action
- Wire: Run Write Action
- Wire: Sign In
- Web Actions
- Agentic Search
- Crawl
- Map
- Scrape URL
- Search
- AI Visibility Search
- AI Visibility Sources
- Browser Task
- Control Monitor
- Create Monitor
- Delete Session
- Get Monitor Changes
- List Monitors
- List Sessions
- Wire: Browse Catalog
- Wire: Discover Actions
- Wire: List Identities
- Wire: Request New Action
- Wire: Run Read Action
- Wire: Run Write Action
- Wire: Sign In
- Wire Actions
Browser → Get Monitor Changes
AI-generatedSummary
Retrieve the detected changes recorded for a specific monitor identified by its Monitor ID.
Inputs
- Monitor ID (required) — The unique identifier of the monitor for which to fetch recorded changes (obtained from List Monitors or Create Monitor operations).
Output shape
a single record containing the monitor's change history and related metadata
The response JSON includes success status, the operation name, the provided monitor ID, and detailed information on the changes detected by the monitor.
Examples
Example 1: Fetch change history of a website monitor
Provide the 'Monitor ID' of an existing monitor to retrieve its recorded changes, useful for auditing updates or triggers downstream workflow logic based on detected content changes.