name: firecrawl-monitor\ndescription: |\nAlert by webhook/email on web changes — use for \"monitor/watch/track/alert me when\": recurring checks on known URLs (prefer over repeated one-off scrapes) or web-wide watches for new results (queries + goal).\nallowed-tools:
\nDetect when content on a website changes and get notified by webhook or email. Firecrawl handles fetching, diffing, judging, and notifying server-side. Each page in a check is labeled same, new, changed, removed, or error.
Pick a target mode by what you're watching:
\n| Mode | \nFlags | \nWatches | \n
|---|---|---|
| Single page | \n--page <url> | \none URL, for changes | \n
| URL batch | \n--scrape-urls <url,url,...> | \nseveral URLs, for changes | \n
| Whole site | \n--crawl-url <root-url> | \nevery page a crawl discovers, for changes | \n
| Web search | \n--queries <q,...> + --goal | \nthe whole web, for new results matching the goal | \n
The first three watch URLs you already have. Web search runs your queries each check and alerts on results it hasn't seen before (labeled new once, same on later checks); --goal is required with --queries.
# Single page, natural-language schedule, email alert\nfirecrawl monitor create --name \"Blog\" --schedule \"every 30 minutes\" \\\n --goal \"Alert when a new blog post is published.\" \\\n --page https://example.com/blog \\\n --email alerts@example.com\n\n# Web monitor — search the whole web for NEW results matching a goal\nfirecrawl monitor create --name \"Competitor launches\" --schedule \"daily at 9:00\" \\\n --queries \"competitor product launch,competitor funding round\" \\\n --goal \"Alert when a competitor announces a new product or raises funding.\" \\\n --search-window 7d --max-results 20 \\\n --email alerts@example.com\n\n# Webhook notifications\nfirecrawl monitor create --name \"Docs webhook\" --schedule \"every 30 minutes\" \\\n --goal \"Alert when docs content changes.\" \\\n --page https://example.com/docs \\\n --webhook-url https://example.com/hook \\\n --webhook-events monitor.page,monitor.check.completed\n\n# Manage and inspect\nfirecrawl monitor list --limit 20\nfirecrawl monitor get <monitorId>\nfirecrawl monitor run <monitorId> # trigger a check now\nfirecrawl monitor checks <monitorId> # list all checks\nfirecrawl monitor check <monitorId> <checkId> --page-status changed\nfirecrawl monitor update <monitorId> --state paused\nfirecrawl monitor delete <monitorId>\nSubcommands: create | list | get | update | delete | run | checks | check. Run firecrawl monitor <subcommand> --help for the full option list.
Done when: create returns a monitor ID and a smoke-test run + check confirms the expected target, state, and notification configuration.
Read goals.md when writing or refining --goal (and --queries for web monitors). Read json-tracking.md when the user cares about specific structured fields (price, headline, stock flag) and wants per-field diffs.
update --state paused; reserve delete for monitors that are permanently done. (--state is an update flag; --status is the global CLI status flag.)--page-status changed (or new, removed, error) to skip the noise from same pages.firecrawl monitor run <id> triggers a check immediately — useful for smoke-testing a monitor right after creating it.--retention-days controls how long snapshots are kept for diffing. Lower it for high-frequency monitors to save storage.maxAge to 0 — every check performs a fresh scrape unless scrapeOptions.maxAge is set explicitly in a JSON payload.monitor when checks become recurring--crawl-url here for recurring crawl diffs