firecrawl-ci-integration
Configure FireCrawl CI/CD integration with GitHub Actions and testing.Use when setting up automated testing, configuring CI pipelines,or integrating FireCrawl tests into your build process.Trigger with phrases like "firecrawl CI", "firecrawl GitHub Actions","firecrawl automated tests", "CI firecrawl".
When & Why to Use This Skill
This Claude skill automates the configuration of FireCrawl CI/CD pipelines using GitHub Actions. It enables developers to seamlessly integrate automated web scraping tests, manage API secrets securely via GitHub CLI, and establish robust testing workflows that ensure data extraction reliability throughout the software development lifecycle.
Use Cases
- Automating FireCrawl API health checks and integration tests within GitHub Actions to prevent breaking changes in web scraping logic.
- Configuring secure environment variables and GitHub Secrets for FireCrawl API keys using automated CLI commands.
- Setting up branch protection rules that require successful FireCrawl integration tests before merging pull requests to main branches.
- Creating production-ready release workflows that verify FireCrawl connectivity and script performance before deploying updates.
| name | firecrawl-ci-integration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
FireCrawl CI Integration
Overview
Set up CI/CD pipelines for FireCrawl integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- FireCrawl test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
Create .github/workflows/firecrawl-integration.yml:
name: FireCrawl Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
Step 2: Configure Secrets
gh secret set FIRECRAWL_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
describe('FireCrawl Integration', () => {
it.skipIf(!process.env.FIRECRAWL_API_KEY)('should connect', async () => {
const client = getFireCrawlClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
Output
- Automated test pipeline
- PR checks configured
- Coverage reports uploaded
- Release workflow ready
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
Examples
Release Workflow
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
FIRECRAWL_API_KEY: ${{ secrets.FIRECRAWL_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify FireCrawl production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
Branch Protection
required_status_checks:
- "test"
- "firecrawl-integration"
Resources
Next Steps
For deployment patterns, see firecrawl-deploy-integration.