lindy-migration-deep-dive

# Lindy Migration Deep Dive ## Overview Migrate existing automation workflows from Zapier, Make (Integromat), n8n, LangChain, or custom code to Lindy AI. Key insight: Lindy replaces rigid rule-based automations with AI agents that can reason, adapt, and handle ambiguity — so migration is a redesign opportunity, not a 1:1 translation. ## Prerequisites - Inventory of existing automations (source platform) - Lindy workspace ready with required integrations authorized - Migration timeline approved - Rollback plan defined for customer-facing workflows ## Migration Source Comparison | Source Platform | Lindy Equivalent | Key Difference | |----------------|-----------------|----------------| | **Zapier Zap** | Lindy Agent | AI reasoning replaces rigid if/then | | **Make Scenario** | Lindy Agent | No-code builder instead of module chains | | **n8n Workflow** | Lindy Agent | Managed infra, no self-hosting | | **LangChain Agent** | Lindy Agent Step | No-code, managed, no Python needed | | **Custom code** | HTTP Request + Run Code | Less code, AI fills gaps | ## Instructions ### Step 1: Inventory Source Automations For each existing automation, document: | Field | Example | |-------|---------| | **Name** | Support Email Triage | | **Trigger** | New email in support@co.com | | **Steps** | 1. Parse email 2. Classify 3. Route to channel | | **Integrations** | Gmail, Slack, Sheets | | **Frequency** | ~50 runs/day | | **Complexity** | Medium (3 steps, 1 condition) | ### Step 2: Class...