lindy-webhooks-events

name	lindy-webhooks-events
description	Configure Lindy AI webhook triggers, callback patterns, and event handling. Use when setting up webhook triggers, implementing callback receivers, or building event-driven Lindy integrations. Trigger with phrases like "lindy webhook", "lindy events", "lindy callback", "lindy webhook trigger".
allowed-tools	Read, Write, Edit, Bash(curl:*)
version	1.15.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","lindy","webhooks"]
compatibility	Designed for Claude Code

Lindy Webhooks & Events

Overview

Lindy supports webhooks in two directions: Inbound (Webhook Received trigger wakes an agent) and Outbound (HTTP Request action calls your API). This skill covers both patterns, plus the callback pattern for async two-way communication.

Prerequisites

• Lindy account with active agents
• HTTPS endpoint for receiving callbacks (if using outbound/callback patterns)
• Completed lindy-install-auth setup

Webhook Architecture

INBOUND (your system triggers Lindy):
[Your App] --POST--> https://public.lindy.ai/api/v1/webhooks/<id>
                         ↓
                    [Lindy Agent Wakes Up]
                         ↓
                    [Processes with LLM]
                         ↓
                    [Executes Actions]

OUTBOUND (Lindy calls your system):
[Lindy Agent] --HTTP Request action--> https://your-api.com/endpoint
                                            ↓
                                       [Your Handler]

CALLBACK (two-way async):
[Your App] --POST with callbackUrl--> [Lindy Agent]
                                          ↓
[Your App] <--POST to callbackUrl-- [Lindy: Send POST to Callback]

Instructions

Step 1: Create Webhook Received Trigger

1. In your agent, click the trigger node

2. Select Webhook Received

3. Lindy generates a unique URL:

   https://public.lindy.ai/api/v1/webhooks/<unique-id>
   

4. Click Generate Secret — copy immediately (shown only once)

5. Configure follow-up processing mode:

   • Process in workflow: Handle in current workflow
   • Spawn separate task: Each webhook creates a new task
   • Discard follow-ups: Ignore subsequent requests while processing

Step 2: Access Webhook Data in Workflow

Reference incoming webhook data in any subsequent action field:

Variable	Description	Example
{{webhook_received.request.body}}	Full JSON payload	{"event": "order.created", ...}
{{webhook_received.request.body.event}}	Specific field