Agent skill · software engineering · jeremylongshore
intercom-deploy-integration
Deploy Intercom integrations to Vercel, Fly.io, and Cloud Run with proper secrets. Use when deploying Intercom-powered applications to production, configuring platform-specific secrets, or setting up signed webhook endpoints and health checks. Trigger with phrases like "deploy intercom", "intercom Vercel", "intercom production deploy", "intercom Cloud Run", "intercom Fly.io".
Why this skill is useful
Adds specific deployment commands and secret management patterns for Intercom integrations on multiple platforms that the AI wouldn't reliably generate on its own.
What it needs
Requires flyctl, gcloud, vercel installed locally. Requires intercom account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Intercom Deploy Integration Overview Deploy Intercom-powered applications to Vercel, Fly.io, or Google Cloud Run with proper secret management, signed webhook endpoints, and health checks. The workflow is the same across platforms — provision two secrets, deploy, wire a /health probe, then register the webhook URL — and each platform's copy-ready code lives in references/implementation.md. Prerequisites Intercom production access token Platform CLI installed (vercel, flyctl, or gcloud) Application with Intercom integration ready for deployment Authentication Two secrets drive every deployment. INTERCOMACCESSTOKEN authenticates API calls (passed to the SDK as new IntercomClient({ token })); INTERCOMWEBHOOKSECRET is the Developer Hub signing secret used to verify inbound webhook payloads (HMAC-SHA1 over the raw body, compared against the X-Hub-Signature header). Store both in the platform's secret store — never hardcode them: vercel env add, fly secrets set, or Cloud Run Secret Manager. A mismatched webhook secret returns 401 Invalid signature; an invalid token surfaces as a degraded health check rather than a hard failure. Instructions Pick the platform that matches your stack. Each step below shows the essential skeleton; open references/implementation.md for the complete webhook handler, vercel.json, fly.toml, Cloud Run deploy script, and shared health-check code. Step 1: Choose a platform and provision secrets Vercel (serverless): vercel env add INTERCOMACCESSTOKEN production then vercel env add INTERCOMWEBHOOKSECRET production. Fly.io (long-running): fly secrets set INTERCOMACCESSTOKEN=... INTERCOMWEBHOOKSECRET=.... Cloud Run (container): store both in Secret Manager and mount with --set-secrets. Step 2: Write the signed webhook handler Read the raw request body (disable body parsing), recompute the HMAC-SHA1 signature, and compare with crypto.timingSafeEqual. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/intercom-deploy-integration--bd44d4