home / skills / jeremylongshore / claude-code-plugins-plus-skills / perplexity-deploy-integration
/plugins/saas-packs/perplexity-pack/skills/perplexity-deploy-integration
This skill deploys Perplexity-powered apps to Vercel, Fly.io, and Cloud Run, handling secrets, config, and production-ready deployment pipelines.
npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill perplexity-deploy-integrationReview the files below or copy the command above to add this skill to your agents.
---
name: perplexity-deploy-integration
description: |
Deploy Perplexity integrations to Vercel, Fly.io, and Cloud Run platforms.
Use when deploying Perplexity-powered applications to production,
configuring platform-specific secrets, or setting up deployment pipelines.
Trigger with phrases like "deploy perplexity", "perplexity Vercel",
"perplexity production deploy", "perplexity Cloud Run", "perplexity Fly.io".
allowed-tools: Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---
# Perplexity Deploy Integration
## Overview
Deploy Perplexity-powered applications to popular platforms with proper secrets management.
## Prerequisites
- Perplexity API keys for production environment
- Platform CLI installed (vercel, fly, or gcloud)
- Application code ready for deployment
- Environment variables documented
## Vercel Deployment
### Environment Setup
```bash
# Add Perplexity secrets to Vercel
vercel secrets add perplexity_api_key sk_live_***
vercel secrets add perplexity_webhook_secret whsec_***
# Link to project
vercel link
# Deploy preview
vercel
# Deploy production
vercel --prod
```
### vercel.json Configuration
```json
{
"env": {
"PERPLEXITY_API_KEY": "@perplexity_api_key"
},
"functions": {
"api/**/*.ts": {
"maxDuration": 30
}
}
}
```
## Fly.io Deployment
### fly.toml
```toml
app = "my-perplexity-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
```bash
# Set Perplexity secrets
fly secrets set PERPLEXITY_API_KEY=sk_live_***
fly secrets set PERPLEXITY_WEBHOOK_SECRET=whsec_***
# Deploy
fly deploy
```
## Google Cloud Run
### Dockerfile
```dockerfile
FROM node:20-slim
WORKDIR /app
COPY package*.json ./
RUN npm ci --only=production
COPY . .
CMD ["npm", "start"]
```
### Deploy Script
```bash
#!/bin/bash
# deploy-cloud-run.sh
PROJECT_ID="${GOOGLE_CLOUD_PROJECT}"
SERVICE_NAME="perplexity-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=PERPLEXITY_API_KEY=perplexity-api-key:latest
```
## Environment Configuration Pattern
```typescript
// config/perplexity.ts
interface PerplexityConfig {
apiKey: string;
environment: 'development' | 'staging' | 'production';
webhookSecret?: string;
}
export function getPerplexityConfig(): PerplexityConfig {
const env = process.env.NODE_ENV || 'development';
return {
apiKey: process.env.PERPLEXITY_API_KEY!,
environment: env as PerplexityConfig['environment'],
webhookSecret: process.env.PERPLEXITY_WEBHOOK_SECRET,
};
}
```
## Health Check Endpoint
```typescript
// api/health.ts
export async function GET() {
const perplexityStatus = await checkPerplexityConnection();
return Response.json({
status: perplexityStatus ? 'healthy' : 'degraded',
services: {
perplexity: perplexityStatus,
},
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 Perplexity API keys securely using the platform's secrets management.
### Step 3: Deploy Application
Use the platform CLI to deploy your application with Perplexity integration.
### Step 4: Verify Health
Test the health check endpoint to confirm Perplexity connectivity.
## Output
- Application deployed to production
- Perplexity 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
```bash
#!/bin/bash
# Platform-agnostic deploy helper
case "$1" in
vercel)
vercel secrets add perplexity_api_key "$PERPLEXITY_API_KEY"
vercel --prod
;;
fly)
fly secrets set PERPLEXITY_API_KEY="$PERPLEXITY_API_KEY"
fly deploy
;;
esac
```
## Resources
- [Vercel Documentation](https://vercel.com/docs)
- [Fly.io Documentation](https://fly.io/docs)
- [Cloud Run Documentation](https://cloud.google.com/run/docs)
- [Perplexity Deploy Guide](https://docs.perplexity.com/deploy)
## Next Steps
For webhook handling, see `perplexity-webhooks-events`.This skill helps deploy Perplexity-powered applications to Vercel, Fly.io, and Google Cloud Run with secure secrets management and simple deployment scripts. It provides platform-specific commands, example configuration files, and a health-check pattern to verify runtime connectivity to Perplexity. Use it to move a Perplexity integration from development into production reliably.
The skill supplies step-by-step CLI commands and config snippets for each target platform: vercel.json and secret workflows for Vercel, fly.toml and fly secrets for Fly.io, and a Dockerfile plus gcloud deploy script for Cloud Run. It outlines an environment configuration pattern and a health-check endpoint to validate the Perplexity API connection after deployment. Quick helper scripts automate secret injection and deployment across platforms.
What secrets do I need to configure for production?
You need a production Perplexity API key and optionally a webhook secret. Add them via vercel secrets, fly secrets, or Cloud Run secret versions.
How do I verify the integration after deployment?
Call the health-check endpoint provided by the sample and confirm it reports 'healthy' for Perplexity, and check logs for successful API calls.