tessl install github:jeremylongshore/claude-code-plugins-plus-skills --skill fireflies-deploy-integrationDeploy Fireflies.ai integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Fireflies.ai-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy fireflies", "fireflies Vercel", "fireflies production deploy", "fireflies Cloud Run", "fireflies Fly.io".
Review Score
84%
Validation Score
12/16
Implementation Score
73%
Activation Score
100%
Deploy Fireflies.ai-powered applications to popular platforms with proper secrets management.
# Add Fireflies.ai secrets to Vercel
vercel secrets add fireflies_api_key sk_live_***
vercel secrets add fireflies_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod{
"env": {
"FIREFLIES_API_KEY": "@fireflies_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}app = "my-fireflies-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 Fireflies.ai secrets
fly secrets set FIREFLIES_API_KEY=sk_live_***
fly secrets set FIREFLIES_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="fireflies-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=FIREFLIES_API_KEY=fireflies-api-key:latest// config/fireflies.ts
interface Fireflies.aiConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getFireflies.aiConfig(): Fireflies.aiConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.FIREFLIES_API_KEY!,
environment: env as Fireflies.aiConfig['environment'],
webhookSecret: process.env.FIREFLIES_WEBHOOK_SECRET,
};
}// api/health.ts
export async function GET() {
const firefliesStatus = await checkFireflies.aiConnection();
return Response.json({
status: firefliesStatus ? 'healthy' : 'degraded',
services: {
fireflies: firefliesStatus,
},
timestamp: new Date().toISOString(),
});
}Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Store Fireflies.ai API keys securely using the platform's secrets management.
Use the platform CLI to deploy your application with Fireflies.ai integration.
Test the health check endpoint to confirm Fireflies.ai 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 fireflies_api_key "$FIREFLIES_API_KEY"
vercel --prod
;;
fly)
fly secrets set FIREFLIES_API_KEY="$FIREFLIES_API_KEY"
fly deploy
;;
esacFor webhook handling, see fireflies-webhooks-events.