tessl install github:jeremylongshore/claude-code-plugins-plus-skills --skill firecrawl-deploy-integrationDeploy FireCrawl integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying FireCrawl-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy firecrawl", "firecrawl Vercel", "firecrawl production deploy", "firecrawl Cloud Run", "firecrawl Fly.io".
Review Score
81%
Validation Score
12/16
Implementation Score
65%
Activation Score
100%
Deploy FireCrawl-powered applications to popular platforms with proper secrets management.
# Add FireCrawl secrets to Vercel
vercel secrets add firecrawl_api_key sk_live_***
vercel secrets add firecrawl_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod{
"env": {
"FIRECRAWL_API_KEY": "@firecrawl_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}app = "my-firecrawl-app"
primary_region = "iad"
[env]
NODE_ENV = "production"
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = true
auto_start_machines = true# Set FireCrawl secrets
fly secrets set FIRECRAWL_API_KEY=sk_live_***
fly secrets set FIRECRAWL_WEBHOOK_SECRET=whsec_***
# Deploy
fly deployFROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="firecrawl-service"
REGION="us-central1"
# Build and push image
gcloud builds submit --tag gcr.io/$PROJECT_ID/$SERVICE_NAME
# Deploy to Cloud Run
gcloud run deploy $SERVICE_NAME \
--image gcr.io/$PROJECT_ID/$SERVICE_NAME \
--region $REGION \
--platform managed \
--allow-unauthenticated \
--set-secrets=FIRECRAWL_API_KEY=firecrawl-api-key:latest// config/firecrawl.ts
interface FireCrawlConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getFireCrawlConfig(): FireCrawlConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.FIRECRAWL_API_KEY!,
environment: env as FireCrawlConfig['environment'],
webhookSecret: process.env.FIRECRAWL_WEBHOOK_SECRET,
};
}// api/health.ts
export async function GET() {
const firecrawlStatus = await checkFireCrawlConnection();
return Response.json({
status: firecrawlStatus ? 'healthy' : 'degraded',
services: {
firecrawl: firecrawlStatus,
},
timestamp: new Date().toISOString(),
});
}Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Store FireCrawl API keys securely using the platform's secrets management.
Use the platform CLI to deploy your application with FireCrawl integration.
Test the health check endpoint to confirm FireCrawl connectivity.
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via platform CLI |
| Deploy timeout | Large build | Increase build timeout |
| Health check fails | Wrong API key | Verify environment variable |
| Cold start issues | No warm-up | Configure minimum instances |
#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
vercel)
vercel secrets add firecrawl_api_key "$FIRECRAWL_API_KEY"
vercel --prod
;;
fly)
fly secrets set FIRECRAWL_API_KEY="$FIRECRAWL_API_KEY"
fly deploy
;;
esacFor webhook handling, see firecrawl-webhooks-events.