Agent skill · software engineering · jeremylongshore
lindy-sdk-patterns
Lindy integration patterns for webhook handling, HTTP actions, and
Why this skill is useful
Provides specific integration patterns and code examples for Lindy SDK that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. 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 Integration Patterns Overview Use Lindy's documented integration primitives: Webhook Received for inbound calls, HTTP Request for outbound calls, Run Code for bounded transformations, and Send POST Request to Callback for the documented callback workflow. This is not an SDK guide: Lindy's current public documentation does not provide the package, client, agent CRUD, streaming, API key, or general API-host surface that older copies of this skill claimed. Prerequisites Lindy workspace with an editable custom agent An application-owned HTTPS endpoint when outbound calls or callbacks are required A secret manager for the Lindy-generated Webhook Received secret and any separate credential owned by the target application Sanitized test fixtures and access to Tasks/Test Panel Authentication and Trust Boundaries Inbound to Lindy: create the webhook in the Webhook Received trigger, select Generate Secret, store the one-time value, and send it as an Authorization bearer value. Use only the generated public.lindy.ai webhook URL. Outbound from Lindy: configure authentication required by the target service in the HTTP Request action. This is the target service's credential, not a Lindy API key. Callback: Lindy's webhook guide documents callbackUrl and Send POST Request to Callback, but does not document a Lindy callback signature. Treat callback content as untrusted unless the receiving application establishes its own authenticated boundary; never invent or claim a Lindy signing header. Keep inbound, outbound, and callback credentials distinct. Never put secrets in a prompt, body, query string, task title, log, or Run Code text output. Instructions 1. Configure an Inbound Webhook Received Trigger 1. Add Webhook Received and create a named webhook. 2. Generate its secret and store it immediately; Lindy documents that it is shown once. 3. Choose follow-up behavior deliberately: same task, new task, or ignore. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-sdk-patterns