| name | firecrawl-ci-integration |
| description | Configure Firecrawl CI/CD integration with GitHub Actions and automated scraping tests.
Use when setting up automated testing of Firecrawl integrations, configuring CI pipelines,
or validating scraping behavior in pull requests.
Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions",
"firecrawl automated tests", "CI firecrawl", "test firecrawl in CI".
|
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","firecrawl","testing","ci-cd"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Firecrawl CI Integration
Overview
Set up CI/CD pipelines to test Firecrawl integrations automatically. Covers GitHub Actions workflow, API key secrets management, integration tests that validate real scraping, and mock-based unit tests for PRs.
Prerequisites
- GitHub repository with Actions enabled
- Firecrawl API key for testing (separate from production)
@mendable/firecrawl-js installed
Instructions
Step 1: Configure Secrets
set -euo pipefail
gh secret set FIRECRAWL_API_KEY --body "fc-test-key-here"
Step 2: GitHub Actions Workflow
name: Firecrawl Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "20"
cache: "npm"
- run: npm ci
- run: npm test --