apify-deploy-integration
Deploy Apify integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Apify-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy apify", "apify Vercel", "apify production deploy", "apify Cloud Run", "apify Fly.io".
Allowed Tools
Provided by Plugin
apify-pack
Claude Code skill pack for Apify (18 skills)
Installation
This skill is included in the apify-pack plugin:
/plugin install apify-pack@claude-code-plugins-plus
Click to copy
Instructions
Apify Deploy Integration
Overview
Deploy Apify-powered applications to popular platforms with proper secrets management.
Prerequisites
- Apify 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 Apify secrets to Vercel
vercel secrets add apify_api_key sk_live_***
vercel secrets add apify_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
vercel.json Configuration
{
"env": {
"APIFY_API_KEY": "@apify_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
Fly.io Deployment
fly.toml
app = "my-apify-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 Apify secrets
fly secrets set APIFY_API_KEY=sk_live_***
fly secrets set APIFY_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="apify-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=APIFY_API_KEY=apify-api-key:latest
Environment Configuration Pattern
// config/apify.ts
interface ApifyConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getApifyConfig(): ApifyConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.APIFY_API_KEY!,
environment: env as ApifyConfig['environment'],
webhookSecret: process.env.APIFY_WEBHOOK_SECRET,
};
}
Health Check Endpoint
// api/health.ts
export async function GET() {
const apifyStatus = await checkApifyConnection();
return Response.json({
status: apifyStatus ? 'healthy' : 'degraded',
services: {
apify: apifyStatus,
},
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 Apify API keys securely using the platform's secrets management.
Step 3: Deploy Application
Use the platform CLI to deploy your application with Apify integration.
Step 4: Verify Health
Test the health check endpoint to confirm Apify connectivity.
Output
- Application deployed to production
- Apify 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 apify_api_key "$APIFY_API_KEY"
vercel --prod
;;
fly)
fly secrets set APIFY_API_KEY="$APIFY_API_KEY"
fly deploy
;;
esac
Resources
Next Steps
For webhook handling, see apify-webhooks-events.