Agent skill
posthog-deploy-integration
Deploy PostHog integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying PostHog-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy posthog", "posthog Vercel", "posthog production deploy", "posthog Cloud Run", "posthog Fly.io".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/posthog-deploy-integration
SKILL.md
PostHog Deploy Integration
Overview
Deploy PostHog-powered applications to popular platforms with proper secrets management.
Prerequisites
- PostHog API keys for production environment
- Platform CLI installed (vercel, fly, or gcloud)
- Application code ready for deployment
- Environment variables documented
Vercel Deployment
Environment Setup
# Add PostHog secrets to Vercel
vercel secrets add posthog_api_key sk_live_***
vercel secrets add posthog_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
vercel.json Configuration
{
"env": {
"POSTHOG_API_KEY": "@posthog_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
Fly.io Deployment
fly.toml
app = "my-posthog-app"
primary_region = "iad"
[env]
NODE_ENV = "production"
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = true
auto_start_machines = true
Secrets
# Set PostHog secrets
fly secrets set POSTHOG_API_KEY=sk_live_***
fly secrets set POSTHOG_WEBHOOK_SECRET=whsec_***
# Deploy
fly deploy
Google Cloud Run
Dockerfile
FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]
Deploy Script
#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="posthog-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=POSTHOG_API_KEY=posthog-api-key:latest
Environment Configuration Pattern
// config/posthog.ts
interface PostHogConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getPostHogConfig(): PostHogConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.POSTHOG_API_KEY!,
environment: env as PostHogConfig['environment'],
webhookSecret: process.env.POSTHOG_WEBHOOK_SECRET,
};
}
Health Check Endpoint
// api/health.ts
export async function GET() {
const posthogStatus = await checkPostHogConnection();
return Response.json({
status: posthogStatus ? 'healthy' : 'degraded',
services: {
posthog: posthogStatus,
},
timestamp: new Date().toISOString(),
});
}
Instructions
Step 1: Choose Deployment Platform
Select the platform that best fits your infrastructure needs and follow the platform-specific guide below.
Step 2: Configure Secrets
Store PostHog API keys securely using the platform's secrets management.
Step 3: Deploy Application
Use the platform CLI to deploy your application with PostHog integration.
Step 4: Verify Health
Test the health check endpoint to confirm PostHog connectivity.
Output
- Application deployed to production
- PostHog secrets securely configured
- Health check endpoint functional
- Environment-specific configuration in place
Error Handling
| 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 |
Examples
Quick Deploy Script
#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
vercel)
vercel secrets add posthog_api_key "$POSTHOG_API_KEY"
vercel --prod
;;
fly)
fly secrets set POSTHOG_API_KEY="$POSTHOG_API_KEY"
fly deploy
;;
esac
Resources
Next Steps
For webhook handling, see posthog-webhooks-events.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?