Agent skill

firecrawl-webhooks-events

Implement Firecrawl webhook event handling for async crawl and batch scrape jobs. Use when setting up webhook endpoints, handling crawl.page/crawl.completed events, or processing async job results in real-time. Trigger with phrases like "firecrawl webhook", "firecrawl events", "firecrawl webhook signature", "handle firecrawl events", "firecrawl notifications". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-webhooks-events --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.11.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(curl:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: plugins/saas-packs/firecrawl-pack/skills/firecrawl-webhooks-events/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Firecrawl Webhooks & Events ## Overview Handle Firecrawl webhooks for real-time notifications on async crawl and batch scrape jobs. Instead of polling `checkCrawlStatus`, configure a webhook URL and Firecrawl will POST events as pages are scraped and jobs complete. Signed with HMAC-SHA256 via `X-Firecrawl-Signature`. ## Webhook Event Types | Event | Trigger | Payload | |-------|---------|---------| | `crawl.started` | Crawl job begins | Job ID, config | | `crawl.page` | Individual page scraped | Page markdown, metadata | | `crawl.completed` | Full crawl finishes | All pages array | | `crawl.failed` | Crawl job errors | Error message | | `batch_scrape.completed` | Batch scrape finishes | All scraped pages | ## Instructions ### Step 1: Start Crawl with Webhook ```typescript import FirecrawlApp from "@mendable/firecrawl-js"; const firecrawl = new FirecrawlApp({ apiKey: process.env.FIRECRAWL_API_KEY!, }); // Webhook as string (simple) const job = await firecrawl.asyncCrawlUrl("https://docs.example.com", { limit: 100, scrapeOptions: { formats: ["markdown"] }, webhook: "https://api.yourapp.com/webhooks/firecrawl", }); console.log(`Crawl started: ${job.id}`); // Webhook as object (with

What's inside
Steps it walks through
  1. Overview
  2. Webhook Event Types
  3. Instructions
  4. Step 1: Start Crawl with Webhook
  5. Step 2: Webhook Handler with Signature Verification
  6. Step 3: Process Page Events (Streaming)
  7. Step 4: Handle Crawl Completion
  8. Step 5: Polling as Webhook Fallback
  9. Error Handling
  10. Examples
  11. Local Development with ngrok
  12. Resources
  13. Next Steps
Commands it runs
set -euo pipefail
Start ngrok tunnel for local webhook testing
ngrok http 3000
Use the ngrok URL as your webhook endpoint
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the firecrawl-webhooks-events skill do?

Implement Firecrawl webhook event handling for async crawl and batch scrape jobs. Use when setting up webhook endpoints, handling crawl.page/crawl.completed events, or processing async job results in real-time. Trigger with phrases like "firecrawl webhook", "firecrawl events", "firecrawl webhook signature", "handle firecrawl events", "firecrawl notifications". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-webhooks-events --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going