firecrawl-monitor

Detect website content changes and send webhook or email notifications on a schedule.

2|Updated Mar 29, 2015
One-click install
npx skills add https://github.com/ovisan/dotfiles --skill firecrawl-monitor-ovisan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: firecrawl-monitor
Source: https://github.com/ovisan/dotfiles/tree/main/.grok/skills/firecrawl-monitor
Command: npx skills add https://github.com/ovisan/dotfiles --skill firecrawl-monitor-ovisan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tracking changes on websites normally requires wiring together cron jobs, scrapers, diff libraries, and SMTP servers yourself. This Skill replaces that entire stack with a single Firecrawl CLI command that watches pages or the whole web and notifies you only when real content changes. ## Core Features & Use Cases - Page, batch, and site monitors: Watch a single URL, a list of URLs, or every page discovered by a recurring site crawl, with each page labeled same, new, changed, removed, or error. - Web monitors: Monitor the entire web via search queries plus a goal to get alerted on new results such as product launches, funding rounds, papers, or brand mentions. - AI noise filtering and structured diffs: A plain-language --goal makes the change judge ignore formatting and tracking-param noise, and JSON-mode change tracking returns per-field diffs like plans[0].price: "$19/mo" → "$24/mo". - Use Case: A product team wants to know when a competitor changes pricing. Create a monitor on the competitor's pricing page with a goal about price changes and an email recipient, and get notified only when prices, tiers, or features actually change. ## Quick Start Ask the AI to create a Firecrawl monitor on a specific URL with a schedule like "every 30 minutes", a goal describing what change matters, and your email or webhook URL for notifications.

Frequently Asked Questions about firecrawl-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor a webpage for changes and get notified?

Run firecrawl monitor create with --page for the URL, --schedule for frequency like "every 30 minutes", --goal describing what change matters, and --email or --webhook-url for delivery. Firecrawl handles fetching, diffing, and notifying server-side with no cron setup.

How do I monitor the web for new results instead of a specific URL?

Create a web monitor with --queries for comma-separated search queries plus a required --goal describing what counts as a match. Each check runs the searches and alerts only on new results not seen before, with --search-window controlling recency from 5m to 7d.

What is the difference between firecrawl scrape and firecrawl monitor?

Scrape reads a page once and returns its current content. Monitor checks a URL repeatedly on a schedule and notifies you when content changes, so use monitor whenever the same URL needs checking more than once.

Does Firecrawl monitoring support structured field-level diffs?

Yes, JSON-mode change tracking returns per-field diffs like plans[0].price with previous and current values, plus a snapshot of the full extraction. Pass a JSON body with a changeTracking format and schema via a file or piped stdin to monitor create.

What are the limitations of Firecrawl monitors?

The minimum schedule interval is 15 minutes, and monitoring is not available for zero-data-retention teams. External email recipients must confirm an opt-in email before receiving alerts, and monitor-triggered scrapes default maxAge to 0 for fresh fetches.

Why does my web monitor send too many irrelevant alerts?

Broad queries with a vague goal produce low-value alerts because queries control recall while the goal controls precision. Tighten queries to 2-6 keyword terms per distinct subject and add an intent-specific Ignore clause to the goal.