LI

lindy-local-dev-loop

A guide to using ngrok or tunneling to test Lindy AI callbacks and webhooks in a local development environment.

Install

mkdir -p .claude/skills/lindy-local-dev-loop && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8769" && unzip -o skill.zip -d .claude/skills/lindy-local-dev-loop && rm skill.zip

Installs to .claude/skills/lindy-local-dev-loop

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.

Set up local development workflow for testing Lindy AI agent integrations.
74 charsno explicit “when” trigger
Beginner

Key capabilities

  • Create local webhook receivers
  • Expose local endpoints via tunneling
  • Configure Lindy agents for local testing
  • Implement local test harnesses
  • Verify webhook authenticity locally

How it works

The workflow uses tunneling software like ngrok to expose local webhook receivers to Lindy's infrastructure. It enables developers to iterate on callback logic by pointing Lindy agents to a temporary tunnel URL.

Inputs & outputs

You give it
Local development code
You get back
Tunnel URL for Lindy agent callbacks

When to use lindy-local-dev-loop

  • Test Lindy callbacks locally
  • Build webhook receivers with hot reload
  • Expose local endpoints for Lindy triggers
  • Verify webhook authenticity locally

About this skill

Lindy Local Dev Loop

Overview

Lindy agents run on Lindy's managed infrastructure — you do not run agents locally. Local development focuses on building and testing the webhook receivers, callback handlers, and application code that Lindy agents interact with. Use ngrok or similar tunnels to expose local endpoints for Lindy webhook triggers.

Prerequisites

  • Node.js 18+ or Python 3.10+
  • ngrok or Cloudflare Tunnel for HTTPS tunneling
  • Lindy account with at least one agent configured
  • Completed lindy-install-auth setup

Instructions

Step 1: Create Webhook Receiver

// server.ts — Express webhook receiver for Lindy callbacks
import express from 'express';
import dotenv from 'dotenv';
dotenv.config();

const app = express();
app.use(express.json());

const WEBHOOK_SECRET = process.env.LINDY_WEBHOOK_SECRET;

// Verify Lindy webhook authenticity
function verifyWebhook(req: express.Request): boolean {
  const auth = req.headers.authorization;
  return auth === `Bearer ${WEBHOOK_SECRET}`;
}

// Receive Lindy agent callbacks
app.post('/lindy/callback', (req, res) => {
  if (!verifyWebhook(req)) {
    console.error('Unauthorized webhook attempt');
    return res.status(401).json({ error: 'Unauthorized' });
  }

  console.log('Lindy callback received:', JSON.stringify(req.body, null, 2));

  // Process the agent's output
  const { taskId, result, status } = req.body;
  console.log(`Task ${taskId}: ${status}`);

  res.json({ received: true });
});

// Health check for Lindy to verify endpoint
app.get('/health', (req, res) => res.json({ status: 'ok' }));

app.listen(3000, () => console.log('Webhook receiver running on :3000'));

Step 2: Expose Local Server via Tunnel

# Install and start ngrok
npm install -g ngrok
ngrok http 3000

# Output: https://abc123.ngrok.io -> http://localhost:3000
# Use this URL in Lindy webhook configuration

Step 3: Configure Lindy Agent to Call Your Endpoint

In the Lindy dashboard, add an HTTP Request action to your agent:

  • Method: POST

  • URL: https://abc123.ngrok.io/lindy/callback

  • Headers: Content-Type: application/json

  • Body (AI Prompt mode):

    Send the task result as JSON with fields: taskId, result, status
    

Or configure a webhook trigger pointing to your tunnel URL:

https://abc123.ngrok.io/lindy/webhook

Step 4: Create Test Harness

// test-trigger.ts — Fire a test webhook to your Lindy agent
import fetch from 'node-fetch';

async function triggerAgent() {
  const WEBHOOK_URL = process.env.LINDY_WEBHOOK_URL!;
  const SECRET = process.env.LINDY_WEBHOOK_SECRET!;

  const response = await fetch(WEBHOOK_URL, {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${SECRET}`,
      'Content-Type': 'application/json',
    },
    body: JSON.stringify({
      action: 'test',
      data: { message: 'Hello from local dev', timestamp: new Date().toISOString() },
    }),
  });

  console.log(`Status: ${response.status}`);
  console.log(`Response: ${await response.text()}`);
}

triggerAgent();

Step 5: Watch Mode Development

// package.json scripts
{
  "scripts": {
    "dev": "tsx watch server.ts",
    "test:trigger": "tsx test-trigger.ts",
    "tunnel": "ngrok http 3000"
  }
}
# Terminal 1: Start server with auto-reload
npm run dev

# Terminal 2: Start tunnel
npm run tunnel

# Terminal 3: Fire test triggers
npm run test:trigger

Step 6: Environment Configuration

# .env
LINDY_API_KEY=lnd_live_xxxxxxxxxxxx
LINDY_WEBHOOK_SECRET=whsec_xxxxxxxxxxxx
LINDY_WEBHOOK_URL=https://public.lindy.ai/api/v1/webhooks/YOUR_ID
NODE_ENV=development

Development Workflow

[Edit local code] → [Auto-reload via tsx watch]
                          ↓
[Fire test webhook] → [Lindy agent processes]
                          ↓
[Agent calls back] → [ngrok tunnel → localhost:3000]
                          ↓
[Review logs] → [Iterate]

Error Handling

IssueCauseSolution
ngrok tunnel expiresFree tier limit (2hr)Restart ngrok or use paid plan
Lindy can't reach endpointTunnel URL changedUpdate webhook URL in Lindy dashboard
Callback not receivedAgent HTTP Request misconfiguredCheck URL and headers in action config
ECONNREFUSEDLocal server not runningStart server before testing
SSL errorngrok not using HTTPSAlways use the https:// ngrok URL

Resources

Next Steps

Proceed to lindy-sdk-patterns for integration patterns and best practices.

When not to use it

  • When testing agents directly on production infrastructure
  • When the application has no webhook components

Prerequisites

Node.js 18+ or Python 3.10+ngrok or Cloudflare TunnelLindy account with agentlindy-install-auth setup

Limitations

  • Tunnel URLs may expire on free tiers
  • Requires local server to be running for callbacks

How it compares

It focuses on the specific requirement of tunneling for Lindy's managed infrastructure, which does not allow direct local agent execution.

Compared to similar skills

lindy-local-dev-loop side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
lindy-local-dev-loop (this skill)027dCautionBeginner
playwright-browser-automation297moReviewIntermediate
documenso-local-dev-loop227dReviewBeginner
customerio-local-dev-loop127dReviewIntermediate

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

playwright-browser-automation

lackeyjb

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

29146

documenso-local-dev-loop

jeremylongshore

Set up local development environment and testing workflow for Documenso. Use when configuring dev environment, setting up test workflows, or establishing rapid iteration patterns with Documenso. Trigger with phrases like "documenso local dev", "documenso development", "test documenso locally", "documenso dev environment".

26

customerio-local-dev-loop

jeremylongshore

Configure Customer.io local development workflow. Use when setting up local testing, development environment, or offline development for Customer.io integrations. Trigger with phrases like "customer.io local dev", "test customer.io locally", "customer.io development environment", "customer.io sandbox".

12

firecrawl-local-dev-loop

jeremylongshore

Configure FireCrawl local development with hot reload and testing. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with FireCrawl. Trigger with phrases like "firecrawl dev setup", "firecrawl local development", "firecrawl dev environment", "develop with firecrawl".

12

deepgram-local-dev-loop

jeremylongshore

Configure Deepgram local development workflow with testing and iteration. Use when setting up development environment, configuring test fixtures, or establishing rapid iteration patterns for Deepgram integration. Trigger with phrases like "deepgram local dev", "deepgram development setup", "deepgram test environment", "deepgram dev workflow".

11

maintainx-local-dev-loop

jeremylongshore

Set up a local development loop for MaintainX integration development. Use when configuring dev environment, testing API calls locally, or setting up a sandbox workflow for MaintainX. Trigger with phrases like "maintainx dev setup", "maintainx local", "maintainx development environment", "maintainx testing setup".

11

Search skills

Search the agent skills registry