Skip to main content
Get one digest each weekday morning of what a competitor published on its own sites: pricing changes, new plans and launches. A Keenable monitor keeps only new pages from the competitor’s domains. A cron schedule runs it at 9:00, and each run returns the new pages plus a summary in the shape of a JSON Schema you choose.

Recipe prompt

Paste this into your coding agent to have it build the recipe in your project:
Recipe prompt

What you build

To watch the coverage of a competitor on other sites, such as news or review sites, leave include_domains out and use exclude_domains to drop the competitor’s own hosts.

When it runs

At each cron time. A run returns the pages found since the previous run that no earlier run returned, most important first. A run with no new pages still sends monitor.run.completed, with results: []. A monitor matches only pages crawled after you create it, so the first digest covers the time since creation, not the past week.

Code

This sample creates the monitor and prints its ID, its status, the webhook signing secret and the next three run times:
You see the monitor’s ID and active, the whsec_ secret and three timestamps in UTC. Store the secret before anything else: only the create response carries it. To receive the digests, verify each delivery as in Verify a webhook, then read data.run.results and data.run.output from monitor.run.completed events.

Example output

Example output · created on Thursday 19 November 2026 after 9:00 Paris time, IDs vary
9:00 in Paris is 08:00 UTC in winter, and Saturday and Sunday are skipped. upcoming_runs always lists the next three run times in UTC.

Production notes

Monitors needs an API key and is free for now. output.structured is a summary written by an LLM from the run’s pages, and output.grounding names the pages behind each field. Check a field against its pages before you act on it.

Next steps