lindy-reference-architecture

name	lindy-reference-architecture
description	Reference architectures for Lindy AI agent integrations. Use when designing systems, planning multi-agent architectures, or implementing production integration patterns. Trigger with phrases like "lindy architecture", "lindy design", "lindy system design", "lindy patterns", "lindy multi-agent".
allowed-tools	Read, Write, Edit
version	1.15.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","lindy","lindy-reference"]
compatibility	Designed for Claude Code

Lindy Reference Architecture

Overview

Production-ready architecture patterns for integrating Lindy AI agents into applications. Covers webhook integration, multi-agent societies, event-driven pipelines, and high-availability patterns.

Prerequisites

• Understanding of Lindy agent model (triggers, actions, skills)
• Familiarity with webhook-based architectures
• Production requirements defined (throughput, latency, reliability)

Architecture 1: Simple Webhook Integration

Single agent triggered by your application, results sent via callback.

┌─────────────┐       POST (webhook)       ┌──────────────┐
│  Your App   │ ─────────────────────────→  │ Lindy Agent  │
│             │                             │              │
│  /callback  │ ←─────────────────────────  │ HTTP Request │
│             │       POST (callback)       │   Action     │
└─────────────┘                             └──────────────┘

Implementation:

• Your app sends webhook with callbackUrl field
• Lindy agent processes and responds via Send POST Request to Callback
• Your app receives results asynchronously

Best for: Simple automations (email triage, lead scoring, content generation)

Architecture 2: Event-Driven Pipeline

Multiple event sources feed agents through a central webhook router.

┌──────────┐
│ Stripe   │──webhook──┐
└──────────┘           │
                       ▼
┌──────────┐     ┌───────────┐     ┌──────────────┐
│ Shopify  │──→  │  Router   │──→  │ Lindy Agents │
└──────────┘     │  Service  │     │              │
                 └───────────┘     │ • Order Bot  │
┌──────────┐           ▲          │ • Support Bot│
│ Your App │──webhook──┘          │ • Analytics  │
└──────────┘                      └──────────────┘

Implementation:

// Event router — maps events to specific Lindy agents
const agentWebhooks: Record<string, string> = {
  'order.created': process.env.LINDY_ORDER_AGENT_WEBHOOK!,
  'customer.support_request': process.env.LINDY_SUPPORT_AGENT_WEBHOOK!,
  : process..!,
};

app.(,  (req, res) => {
   { event, data } = req.;
   webhookUrl = agentWebhooks[event];

   (!webhookUrl) {
     res.().({ :  });
  }

   (webhookUrl, {
    : ,
    : {
      : ,
      : ,
    },
    : .({ event, data, :  }),
  });

  res.({ : , : event });
});