Skip to main content 홈 크리에이터 jeremylongshore tons-of-skills-marketplace attio-deploy-integration
attio-deploy-integration 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".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill attio-deploy-integration명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
jeremylongshore
jeremylongshore/tons-of-skills-marketplace
GitHub 저장소 열기 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.7.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);
}
from
"crypto"
export
const
api
bodyParser
false
export
default
async
function
handler
req : VercelRequest , res : VercelResponse
if
method
"POST"
return
status
405
end
const
chunks
Buffer
for
await
const
of
push
as
Buffer
const
Buffer
concat
const
headers
"x-attio-signature"
as
string
const
headers
"x-attio-timestamp"
as
string
if
verifySignature
return
status
401
json
error
"Invalid signature"
const
JSON
parse
toString
status
200
json
received
true
await
processAttioEvent
Step 2: Fly.io Deployment
app = "my-attio-app"
primary_region = "iad"
[env]
NODE_ENV = "production"
[http_service]
internal_port = 3000
force_https = true
auto_stop_machines = "suspend"
auto_start_machines = true
[[http_service.checks]]
interval = "30s"
timeout = "5s"
grace_period = "10s"
method = "GET"
path = "/api/health"
fly secrets set ATTIO_API_KEY=sk_prod_xyz
fly secrets set ATTIO_WEBHOOK_SECRET=whsec_prod_abc
fly deploy
fly status
curl -s https://my-attio-app.fly.dev/api/health | jq .
Step 3: Google Cloud Run
echo -n "sk_prod_xyz" | gcloud secrets create attio-api-key --data-file=-
echo -n "whsec_prod_abc" | gcloud secrets create attio-webhook-secret --data-file=-
gcloud builds submit --tag gcr.io/$PROJECT_ID /attio-service
gcloud run deploy attio-service \
--image gcr.io/$PROJECT_ID /attio-service \
--region us-central1 \
--platform managed \
--set-secrets="ATTIO_API_KEY=attio-api-key:latest,ATTIO_WEBHOOK_SECRET=attio-webhook-secret:latest" \
--min-instances=1 \
--max-instances=10 \
--allow-unauthenticated
Step 4: Health Check Endpoint Every deployment should include an Attio health check:
export async function GET ( ): Promise <Response > {
const checks : Record <string , { status : string ; latencyMs ?: number }> = {};
const start = Date .now ();
try {
const res = await fetch ("https://api.attio.com/v2/objects" , {
headers : { Authorization : `Bearer ${process.env.ATTIO_API_KEY} ` },
signal : AbortSignal .timeout (5000 ),
});
checks.attio = {
status : res.ok ? "healthy" : `error_${res.status} ` ,
latencyMs : Date .now () - start,
};
} catch {
checks.attio = { status : "unreachable" , latencyMs : Date .now () - start };
}
const overall = Object .values (checks).every ((c ) => c.status === "healthy" )
? "healthy"
: "degraded" ;
return Response .json ({ status : overall, checks, timestamp : new Date ().toISOString () });
}
Step 5: Register Webhook URL in Attio After deploying, register your webhook endpoint via the API:
const webhook = await fetch ("https://api.attio.com/v2/webhooks" , {
method : "POST" ,
headers : {
Authorization : `Bearer ${process.env.ATTIO_API_KEY} ` ,
"Content-Type" : "application/json" ,
},
body : JSON .stringify ({
target_url : "https://my-attio-app.fly.dev/api/webhooks/attio" ,
subscriptions : [
{ event_type : "record.created" },
{ event_type : "record.updated" },
{ event_type : "record.deleted" },
{
event_type : "list-entry.created" ,
filter : { list : { $eq : "sales_pipeline" } },
},
],
}),
});
const result = await webhook.json ();
console .log ("Webhook registered:" , result.data ?.id ?.webhook_id );
Step 6: Environment Configuration Pattern
interface AppConfig {
attio : {
apiKey : string ;
webhookSecret : string ;
baseUrl : string ;
};
port : number ;
environment : string ;
}
export function loadConfig ( ): AppConfig {
const env = process.env .NODE_ENV || "development" ;
return {
attio : {
apiKey : requireEnv ("ATTIO_API_KEY" ),
webhookSecret : requireEnv ("ATTIO_WEBHOOK_SECRET" ),
baseUrl : "https://api.attio.com/v2" ,
},
port : parseInt (process.env .PORT || "3000" , 10 ),
environment : env,
};
}
function requireEnv (key : string ): string {
const val = process.env [key];
if (!val) throw new Error (`Missing required env: ${key} ` );
return val;
}
Output Following this guide produces the Attio integration outcome for its topic—configuration, validation evidence, operational recovery, or a documented migration result. Record command output and relevant identifiers so a failed step is traceable.
Examples Start with the smallest applicable command or code example in the relevant section, using a dedicated test record or workspace and non-production credentials. Confirm the expected response or validation result before applying the pattern to production.
Error Handling Issue Cause Solution Webhook never fires Wrong URL or not registered Verify with GET /v2/webhooks 401 on health check Token not injected Check platform secrets config Cold start timeout Attio API slow on first call Set min-instances=1 Webhook signature fails Secret mismatch Verify secret matches dashboard value Deploy succeeds, API fails Wrong env variable name Check exact key name in platform UI
Resources
Next Steps For webhook event handling, see attio-webhooks-events.