| name | attio-deploy-integration |
| description | Deploy Attio integrations to Vercel, Fly.io, Railway, and Cloud Run
with proper secrets, health checks, and webhook endpoint configuration.
Trigger: "deploy attio", "attio Vercel", "attio production deploy",
"attio Cloud Run", "attio Fly.io", "attio Railway".
|
| allowed-tools | Read, Write, Edit, Bash(vercel:*), Bash(fly:*), Bash(gcloud:*), Bash(railway:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","crm","attio"] |
| compatibility | Designed for Claude Code |
Attio Deploy Integration
Overview
Deploy Attio-powered applications to production platforms. Covers secrets injection, health check endpoints, webhook URL configuration, and platform-specific configurations for the Attio REST API (https://api.attio.com/v2).
Prerequisites
- Application code tested locally and in CI
- Production Attio token with minimal scopes
- Platform CLI installed
Instructions
Step 1: Vercel Deployment
vercel env add ATTIO_API_KEY production
vercel env add ATTIO_WEBHOOK_SECRET production
vercel --prod
{
"env": {
"ATTIO_API_KEY": "@attio_api_key",
"ATTIO_WEBHOOK_SECRET": "@attio_webhook_secret"
},
"functions": {
"api/webhooks/attio.ts": {
"maxDuration": 30
}
}
}
Vercel webhook endpoint:
import type { VercelRequest, VercelResponse } from "@vercel/node";
import crypto ;
config = { : { : } };
() {
(req. !== ) res.().();
: [] = [];
( chunk req) chunks.(chunk );
rawBody = .(chunks);
signature = req.[] ;
timestamp = req.[] ;
(!(rawBody, signature, timestamp)) {
res.().({ : });
}
event = .(rawBody.());
res.().({ : });
(event);
}