LI

lindy-deploy-integration

A deployment guide for hosting the application layers and webhook receivers that interact with Lindy AI.

Install

mkdir -p .claude/skills/lindy-deploy-integration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8912" && unzip -o skill.zip -d .claude/skills/lindy-deploy-integration && rm skill.zip

Installs to .claude/skills/lindy-deploy-integration

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Deploy applications that integrate with Lindy AI agents.
56 charsno explicit “when” trigger
Intermediate

Key capabilities

  • Deploy webhook receivers
  • Configure production callback handlers
  • Set up environment variables
  • Implement webhook authentication
  • Verify production deployment health

How it works

This workflow guides the deployment of webhook receivers and callback handlers that interact with Lindy agents. It includes steps for securing endpoints with secrets and updating agent URLs to production environments.

Inputs & outputs

You give it
Application code and deployment configuration
You get back
Production-ready webhook receiver endpoint

When to use lindy-deploy-integration

  • Deploy webhook receivers for Lindy
  • Configure production callback handlers
  • Set up environment variables for Lindy API
  • Implement security for webhook endpoints

About this skill

Lindy Deploy Integration

Overview

Lindy agents run on Lindy's managed infrastructure. Deployment focuses on your integration layer: webhook receivers, callback handlers, and application code that Lindy agents interact with via HTTP Request actions and webhook triggers.

Prerequisites

  • Lindy agents configured and tested
  • Application with webhook receiver endpoints
  • Deployment platform (Vercel, Railway, Docker, AWS, GCP)
  • Lindy API key and webhook secrets

Instructions

Step 1: Prepare Application for Deployment

// src/server.ts — Production-ready Lindy webhook receiver
import express from 'express';
import helmet from 'helmet';

const app = express();
app.use(helmet());
app.use(express.json({ limit: '1mb' }));

// Health check for load balancer
app.get('/health', (req, res) => {
  res.json({
    status: 'ok',
    timestamp: new Date().toISOString(),
    version: process.env.APP_VERSION || 'unknown',
  });
});

// Lindy webhook receiver with auth verification
app.post('/lindy/callback', (req, res) => {
  const auth = req.headers.authorization;
  if (auth !== `Bearer ${process.env.LINDY_WEBHOOK_SECRET}`) {
    return res.status(401).json({ error: 'Unauthorized' });
  }

  // Respond immediately, process async
  res.json({ received: true });

  // Async processing
  processWebhook(req.body).catch(err => {
    console.error('Webhook processing error:', err);
  });
});

async function processWebhook(payload: any) {
  const { taskId, status, result } = payload;
  // Your business logic here
  console.log(`Task ${taskId}: ${status}`, result);
}

const PORT = process.env.PORT || 3000;
app.listen(PORT, () => console.log(`Listening on :${PORT}`));

Step 2: Docker Deployment

# Dockerfile
FROM node:20-alpine
WORKDIR /app
COPY package*.json ./
RUN npm ci --production
COPY dist/ ./dist/
EXPOSE 3000
ENV NODE_ENV=production
HEALTHCHECK --interval=30s --timeout=3s \
  CMD wget -qO- http://localhost:3000/health || exit 1
CMD ["node", "dist/server.js"]
# Build and run
docker build -t lindy-integration .
docker run -d \
  -p 3000:3000 \
  -e LINDY_API_KEY="$LINDY_API_KEY" \
  -e LINDY_WEBHOOK_SECRET="$LINDY_WEBHOOK_SECRET" \
  --name lindy-app \
  lindy-integration

Step 3: Vercel Deployment

# Install Vercel CLI
npm i -g vercel

# Set secrets
vercel secrets add lindy-api-key "$LINDY_API_KEY"
vercel secrets add lindy-webhook-secret "$LINDY_WEBHOOK_SECRET"

# Deploy
vercel --prod
// vercel.json
{
  "env": {
    "LINDY_API_KEY": "@lindy-api-key",
    "LINDY_WEBHOOK_SECRET": "@lindy-webhook-secret"
  }
}

Step 4: Update Lindy Agent Webhook URLs

After deployment, update all Lindy agents with production URLs:

  1. In Lindy dashboard, open each agent with a webhook trigger

  2. Navigate to the HTTP Request action (if agent calls your API)

  3. Update URL from dev/staging to production:

    OLD: https://abc123.ngrok.io/lindy/callback
    NEW: https://api.yourapp.com/lindy/callback
    
  4. For webhook triggers, callers need the Lindy-generated URL (unchanged)

  5. Test with a sample webhook to verify end-to-end

Step 5: Post-Deploy Verification

#!/bin/bash
echo "=== Post-Deploy Verification ==="

PROD_URL="https://api.yourapp.com"

# Health check
echo "[1/3] Health check..."
curl -sf "$PROD_URL/health" | jq .

# Webhook endpoint reachable
echo "[2/3] Webhook endpoint..."
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
  -X POST "$PROD_URL/lindy/callback" \
  -H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"test": true}')
echo "Webhook endpoint: HTTP $STATUS (expect 200)"

# Trigger a test agent run
echo "[3/3] Agent trigger test..."
curl -s -X POST "https://public.lindy.ai/api/v1/webhooks/YOUR_ID" \
  -H "Authorization: Bearer $LINDY_WEBHOOK_SECRET" \
  -H "Content-Type: application/json" \
  -d '{"event": "deploy.verify", "env": "production"}'
echo "Agent triggered — check Tasks tab in Lindy dashboard"

Step 6: Rollback Plan

# If deployment fails, rollback:
# Vercel
vercel rollback

# Docker
docker stop lindy-app
docker run -d --name lindy-app-rollback \
  -e LINDY_API_KEY="$LINDY_API_KEY" \
  -e LINDY_WEBHOOK_SECRET="$LINDY_WEBHOOK_SECRET" \
  lindy-integration:previous-tag

# Update Lindy agents back to previous URLs if needed

Deployment Checklist

StepVerification
Build passesnpm run build exits 0
Tests passnpm test all green
Secrets configuredAPI key + webhook secret in platform
Health check respondsGET /health returns 200
Webhook auth worksPOST with valid token returns 200
Webhook auth rejectsPOST without token returns 401
Lindy agent URLs updatedHTTP Request actions point to prod
End-to-end testTrigger agent, receive callback

Error Handling

IssueCauseSolution
Webhook 502App crashed/not runningCheck container logs, restart
Webhook timeoutSlow processingRespond 200 immediately, process async
Wrong URL in LindyNot updated post-deployUpdate HTTP Request action URLs
SSL errorCertificate issueVerify HTTPS cert is valid
Secret mismatchDev secret in prodVerify production secrets match Lindy config

Resources

Next Steps

See lindy-webhooks-events for advanced webhook patterns.

When not to use it

  • When deploying non-webhook-based applications
  • When the application does not require Lindy integration

Prerequisites

Lindy agents configuredApplication with webhook receiver endpointsDeployment platformLindy API key and webhook secrets

Limitations

  • Requires valid HTTPS certificate for production
  • Webhook processing must be asynchronous to avoid timeouts

How it compares

This process provides specific patterns for async webhook processing and health checks, rather than generic deployment instructions.

Compared to similar skills

lindy-deploy-integration side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
lindy-deploy-integration (this skill)027dCautionIntermediate
workflow42moReviewIntermediate
setup-build-tools26moReviewBeginner
agent-release-manager06moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

You might also like

workflow

vercel

Creates durable, resumable workflows using Vercel's Workflow DevKit. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow devkit", or step-based orchestration.

431

setup-build-tools

aaddrick

Install build and extraction tools needed for building Claude Desktop Debian packages

212

agent-release-manager

ruvnet

Agent skill for release-manager - invoke with $agent-release-manager

00

replit-deploy-integration

jeremylongshore

Deploy Replit integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Replit-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy replit", "replit Vercel", "replit production deploy", "replit Cloud Run", "replit Fly.io".

00

agentnote-release

wasabeef

Prepare and publish Agent Note releases with the repo-local Markdown workflow, including version bump validation, release note preview, tag creation, workflow monitoring, and npm/GitHub verification.

00

telegram-bot-builder

davila7

Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.

106130

Search skills

Search the agent skills registry