Agent skill · product strategy · jeremylongshore
lindy-reference-architecture
Reference architectures for Lindy AI agent integrations.
Why this skill is useful
Provides specific integration patterns and architecture designs for Lindy AI agents that the AI wouldn't reliably generate on its own.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Lindy Reference Architecture Overview Choose an integration shape for Lindy workflows without inventing a public SDK or control-plane API. The supported application boundary in these patterns is a dashboard-created Lindy webhook trigger, optionally paired with Lindy's HTTP Request or callback action for outbound delivery. Prerequisites Understanding of Lindy agent model (triggers, actions, skills) Familiarity with webhook-based architectures Production requirements defined (throughput, latency, reliability) Current workspace evidence for the triggers, actions, integrations, and plan entitlements you intend to use A separate secret for each Lindy trigger and a different secret for each callback receiver; neither belongs in source control or architecture diagrams Instructions 1. Write the workload's trust boundaries before selecting a pattern: event producers, Lindy trigger, callback receiver, stores, operators, and third parties. 2. Record data classification, maximum payload size, expected event rate, recovery objective, and whether duplicate delivery is safe. 3. Select the smallest pattern below that meets those requirements. Treat product features as available only after verifying them in the current Lindy workspace. 4. For every webhook edge, require HTTPS, an exact approved hostname, a per-edge secret, schema validation, payload bounds, idempotency, bounded retry, and a dead-letter or manual recovery path. 5. Test authorized and unauthorized requests with synthetic data. A 2xx response is insufficient evidence unless the expected task or durable queue record exists. 6. Produce the architecture decision record and dataflow inventory described in Output, then have a security reviewer approve the exact deployment revision. Trust-Boundary Contract A Lindy trigger URL is created in the dashboard and uses the documented https://public.lindy.ai/api/v1/webhooks/... shape. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/lindy-reference-architecture