Agent skill · marketing growth · jeremylongshore
lindy-webhooks-events
Configure Lindy AI webhook triggers, callback patterns, and event handling.
Why this skill is useful
Provides specific patterns and code snippets for configuring Lindy AI webhooks that the AI wouldn't reliably generate on its own.
What it needs
Requires lindy account access. About 5k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Webhooks and Events Overview Build two documented boundaries: an application calls a Lindy Webhook Received trigger using its generated Bearer secret, and Lindy calls an application through an outbound callback action such as HTTP Request. Treat them as separate trust directions with separate secrets, schemas, retry policies, and evidence. Use Read to inspect the integration and Write or Edit to implement its closed contracts. Implement only the documented generated-Bearer trigger and configurable outbound-request surfaces; do not add unaudited control-plane, registration, event-feed, or signature mechanisms. Prerequisites A Webhook Received trigger with its generated URL and nonempty generated secret. An approved secret manager; never store secret values in code or skill output. A separate, nonempty application-owned callback secret. A fixed or strictly allowlisted HTTPS callback destination controlled by the application owner. Closed request and callback schemas with local field, length, enum, and byte limits. A shared atomic idempotency store and durable queue for scaled or retryable work. Access to Lindy's Tasks view and synthetic test data with unique request IDs. Instructions Step 1: Define minimal contracts Specify only fields the workflow needs. A safe application-owned trigger envelope might contain requestId, an enumerated eventType, a non-sensitive subjectId, and occurredAt. Reject unknown fields, invalid types, excessive lengths, and payloads above the documented local byte limit before enqueue or transmission. Define the callback separately—for example requestId, taskId, and an enumerated status. Do not return full prompts, model output, source records, or customer data unless an approved data contract requires those fields. Step 2: Configure the Lindy trigger In the workflow, add Webhook Received, create or select a webhook, generate its secret, and store that secret immediately. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-webhooks-events--fcc27e