Move your team from Lindy to Relay.app.

Lindy provides a dedicated Knowledge Base feature where you attach proprietary content (websites, Google Docs, Notion pages, Intercom articles, and more) and the agent retrieves from it with source citations when answering queries or taking actions. Relay.app achieves equivalent grounding through custom AI action steps: embed your proprietary content directly in the system prompt or user prompt of an AI step, or use a preceding App step to fetch the relevant document (from Google Drive, Notion, etc.) and pass it as context to the AI step. To migrate a Lindy Knowledge Base to Relay: export or link the source documents; in Relay, add an App step that fetches the target document and a custom AI step that receives the document text as context along with the query; set the output schema to match the fields you need. To migrate Relay AI steps back to Lindy: attach the same source documents to a Lindy Knowledge Base and instruct the agent to consult it before responding.

Both platforms provide large catalogs of pre-built app connectors that supply both triggers and actions for workflows. Lindy markets 'over 4,000 apps' accessible via native integrations and a generic Webhook connector; connectors include Gmail, Google Docs, Linear, Salesforce, HubSpot, Notion, GitHub, Airtable, YouTube, and Telegram. Relay.app ships 500+ deep native integrations covering AI/LLM providers, communication (Slack, Teams, Gmail, WhatsApp), project management (Notion, Jira, Asana, Linear), CRM (HubSpot, Salesforce, Pipedrive), and storage (Google Drive, Dropbox), plus native HTTP request steps and web scraping for apps without a connector. To migrate: audit your current workflow's integrations against the destination platform's connector list; for any connector present in Lindy but absent natively in Relay, use Relay's HTTP request step to call the API directly; for connectors in Relay not in Lindy, use Lindy's generic Webhook connector as a fallback. Re-authenticate OAuth connections on the destination platform — credentials do not transfer.

Both platforms address the problem of what happens mid-workflow when a task requires a decision or handoff that a single automated step cannot fully resolve. Lindy uses agent swarms and multi-agent coordination: one Lindy qualifies a lead, another sends follow-ups, a third updates the CRM, each with a defined role and allowed actions, handing work off between them automatically. Relay.app addresses this with explicit human-in-the-loop steps: Approval steps pause the run until an assignee approves via Slack or email, Data Input steps collect information only a human can provide, and AI review steps route AI-generated output to a person before proceeding. To migrate from Lindy multi-agent flows to Relay: identify each agent handoff point; in Relay, insert a human Approval or Data Input step at the same point if human judgment is appropriate, or use branching with AI steps if fully automated routing is acceptable. To migrate Relay human-in-the-loop steps to Lindy: replace approval checkpoints with a separate Lindy agent that has restricted permissions and a defined escalation action (e.g. send a Slack message and wait for reply webhook before continuing).

Both tools let non-technical users build AI-powered automations without writing code. In Lindy, open the agent builder, pick a template or start blank, select a trigger, chain actions, and write natural-language instructions for what the agent should do. In Relay.app, open the workflow builder and describe what you want to automate in the chat-first interface — Relay generates the workflow including steps, sequences, and tables, which you then refine in the visual drag-and-drop editor. To migrate from Lindy to Relay: export or document your Lindy agent's trigger, action chain, and natural-language instructions; recreate the trigger in Relay (app event, schedule, or webhook) and use the chat builder to generate a matching flow; port the instructions as custom AI action prompts. Migrating from Relay to Lindy: save your Relay workflow steps as a reference, then in Lindy pick the closest pre-built template and layer your logic as Rails conditions and natural-language instructions.

Both platforms model automations as a trigger followed by a series of steps. Lindy calls this system 'Rails': choose a trigger event (email received, calendar event, schedule), then chain Actions across connected apps, with conditional branching available for advanced flows. Relay.app uses a visual workflow editor with the same pattern: pick a trigger (app event, schedule, webhook, form, RSS, or table update), then add App steps, AI steps, human steps, or utility steps in sequence. Branching, loops, and merging paths are native primitives. To migrate Lindy Rails to Relay: map each Lindy trigger to its Relay equivalent (e.g. email trigger → Gmail trigger step; scheduled trigger → schedule trigger); convert each Lindy Action to a Relay App step using the matching integration; translate conditional flows to Relay branch/path steps. To migrate Relay to Lindy: identify the trigger type, recreate it in a new Lindy agent, and chain each step as a Lindy Action, noting that some Relay utility steps (JavaScript, PDF manipulation) have no direct Lindy equivalent and will need workarounds.