firecrawl-monitor

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

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/CliffVale/opencode-free-setup --skill firecrawl-monitor-cliffvale
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: firecrawl-monitor
Source: https://github.com/CliffVale/opencode-free-setup/tree/main/skills/firecrawl-monitor
Command: npx skills add https://github.com/CliffVale/opencode-free-setup --skill firecrawl-monitor-cliffvale

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually re-checking websites for updates is tedious and error-prone, and building your own change-detection pipeline means wiring together cron jobs, scrapers, diff libraries, and email delivery. This Skill provides change-detection-as-a-service through the Firecrawl CLI, so you can watch pages, whole sites, or the entire web and get notified 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 whole web via search queries plus a plain-language goal to alert on new results such as product launches, funding rounds, papers, or brand mentions. - AI noise filtering and structured diffs: A goal-based judge ignores formatting, timestamps, and tracking-param churn, while JSON-mode change tracking returns per-field diffs like price changes ready for Slack or CI. - Use Case: A competitive intelligence analyst creates a daily web monitor with queries for competitor launches and a goal to alert on new product announcements, receiving webhook notifications only for genuinely new, on-topic results. ## Quick Start Ask the AI to create a Firecrawl monitor that checks a specific URL every 30 minutes and emails you when its content changes.

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 website for changes and get notified?▼

Create a Firecrawl monitor with a target URL, a schedule such as "every 30 minutes", a plain-language goal, and an email or webhook destination. Firecrawl handles fetching, diffing, and notifying server-side, so no cron jobs or diff scripts are needed.

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

Use a web monitor by passing comma-separated search queries with --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 recency controlled by --search-window.

What is the difference between a page monitor and a web monitor in Firecrawl?▼

Page monitors watch URLs you already have and label them same, new, changed, removed, or error. Web monitors run search queries against the whole web and alert only on new results matching your goal, never reporting changed or removed.

Can Firecrawl monitors track specific fields like prices instead of full pages?▼

Yes, JSON-mode change tracking extracts structured fields using a schema and prompt, returning per-field diffs such as plans[0].price changing from $19/mo to $24/mo. Pass the configuration as a JSON body via file or stdin since CLI flags do not cover it.

What are the limitations of Firecrawl monitors?▼

The minimum schedule interval is 15 minutes, and monitoring is unavailable for zero-data-retention teams. External email recipients must confirm an opt-in message before receiving alerts, and web-monitor results are capped at 50 per query.

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 and add an intent-specific Ignore clause to the goal to filter out off-topic results.