Agent skill · software engineering · jeremylongshore
clay-deploy-integration
Deploy Clay-powered applications to Vercel, Cloud Run, or Docker with
Why this skill is useful
Provides specific deployment scripts and patterns for integrating Clay applications with Vercel, Cloud Run, and Docker that the AI wouldn't reliably generate on its own.
What it needs
Requires docker, gcloud, vercel installed locally. Requires clay account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Clay Deploy Integration Overview Deploy applications that integrate with Clay (webhook receivers, enrichment processors, CRM sync services) to production platforms. Clay itself is a hosted SaaS -- you deploy the code that interacts with Clay, not Clay itself. The critical requirement is a publicly accessible HTTPS endpoint for Clay's HTTP API columns to call back to. Prerequisites Application code that handles Clay webhooks or HTTP API callbacks Platform CLI installed (vercel, gcloud, or docker) Clay webhook URL and/or API key stored securely HTTPS endpoint accessible from the public internet Instructions Step 1: Vercel Deployment (Serverless) Best for: Webhook receivers, small-scale enrichment handlers. Step 2: Cloud Run Deployment (Container) Best for: High-volume enrichment pipelines, CRM sync services. Step 3: Docker Compose (Self-Hosted) Best for: On-premise deployments, development staging. Step 4: Configure Clay to Call Your Deployed Endpoint Once deployed, update your Clay table's HTTP API column: 1. Get your deployment URL (e.g., https://clay-handler.vercel.app or Cloud Run URL) 2. In Clay table, edit the HTTP API column 3. Set URL to: https://your-deployment.com/api/clay/callback 4. Test on a single row before enabling auto-run Step 5: Health Check Endpoint Step 6: Production Environment Variables Error Handling Issue Cause Solution ------- ------- ---------- Clay can't reach callback Endpoint not public HTTPS Verify URL is accessible, check firewall Cold start timeout Serverless function too slow Set min-instances=1 on Cloud Run Missing secrets in deploy Env vars not configured Add via platform CLI before deploying Health check fails Clay webhook URL invalid Re-copy webhook URL from Clay table Output Publish a deployment receipt containing environment, release/version, runtime identity, secret references, webhook verification, health checks, alert route, and rollback decision. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/clay-deploy-integration