Agent skill · marketing growth · jeremylongshore
lindy-install-auth
Set up a Lindy account and authenticated webhook trigger.
Why this skill is useful
Provides specific API integration patterns and authentication procedures for the Lindy AI platform that the AI wouldn't reliably generate on its own.
What it needs
Requires node, python installed locally. Requires lindy account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Install & Auth Overview Lindy AI is a no-code/low-code AI agent platform. Agents ("Lindies") are built in its web dashboard. This setup uses Lindy's documented webhook trigger: Lindy provides the trigger URL, and the caller authenticates with a bearer secret. Prerequisites Lindy account with permission to create or edit an agent A secret manager for the trigger credential curl or another HTTP client for a synthetic connectivity check A non-production test payload that contains no customer data Instructions Step 1: Create the Webhook Trigger 1. Open the target agent in the Lindy dashboard. 2. Add a webhook trigger and copy its generated URL. 3. Store the complete URL as a secret because its unique path identifies the trigger. 4. Record only the host and a redacted path in setup receipts. Step 2: Configure Bearer Authentication In the webhook trigger's authentication controls, click Generate Secret and copy the Lindy-generated value into your secret manager. Store it separately from any credential used by an HTTP Request action to call your application. Callers must include that generated value as bearer authentication in every request. Step 3: Verify Authorized Connectivity Confirm that exactly one task is created and retain its task ID. Step 4: Verify Rejection Without Authentication Any non-2xx response proves only transport rejection. Also inspect task history; do not continue if the unauthenticated request created a task. Output Deliver a sanitized setup receipt naming the target workspace and environment, the secret-manager references used for the trigger and callback credentials, the webhook host with its unique path redacted, and the results of one authorized and one unauthorized connectivity check. Never place credential values or a complete private webhook URL in the receipt. Examples Store the webhook credential under a development-only secret reference, send a minimal test payload, and record the resulting task ID and HTTP status. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-install-auth