Get AI summaries of any video or article — Sign up free
Introducing Lindy 2.0 - The FIRST True AI-First Automation Platform thumbnail

Introducing Lindy 2.0 - The FIRST True AI-First Automation Platform

MattVidPro·
5 min read

Based on MattVidPro's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Lindy 2.0 is positioned as an automation platform where AI agents can execute actions in external tools, not just generate text.

Briefing

Lindy 2.0 positions itself as a true automation platform rather than an “AI assistant” that only responds to prompts. The core shift: Lindy can run multi-step workflows that connect to real services—like Google Calendar and Google Docs—so tasks can execute automatically once a trigger fires. That matters because it moves AI from drafting text to performing actions, with built-in control points that decide when an agent should continue, stop, or hand off to the next step.

The walkthrough starts by contrasting ChatGPT-style usage with what Lindy enables. ChatGPT-like tools require the user to initiate every action and provide the right inputs; they don’t autonomously manage external systems. Lindy’s approach centers on “Lindies” built through a flow editor. Users begin with a message node that kicks off a bot, then route execution into one or more “AI agents.” Each agent runs under a defined prompt and model choice, and it can be configured with “skills” that grant access to specific actions—such as creating, listing, updating, and deleting Google Calendar events.

A calendar example makes the difference concrete. A custom “calendar management bot” greets the user, checks Google Calendar for conflicts, proposes the best available times, and then creates a new event with details and a link. The workflow also demonstrates recurring automation: a trigger set for every day at 8:00 a.m. launches a separate agent that summarizes the day’s schedule and upcoming events. After the calendar check completes, “jump conditions” determine when the flow should exit the agent and move to the next task—such as sending an email summary—so the system doesn’t stumble between steps.

Lindy 2.0 then expands beyond calendar management into information gathering and document automation. Using a “web monitoring” template, the creator builds a news gatherer that extracts text from web pages and PDFs, updates a Google Doc with the latest AI news, and can optionally record changes to Slack. The example evolves into a multi-source pipeline: it searches the web (including Bing), extracts from an AI news site, and even searches YouTube for AI news results, then writes the aggregated findings into the same Google Doc with correct dates and formatting. The flow editor also supports conditional logic—only continuing when new content is detected since the last check.

Under the hood, Lindy offers model selection (including OpenAI and Claude options such as GPT-4 Turbo, GPT-4o mini, Claude 3 Haiku, Claude 3 Sonnet, and Claude 3 Opus) and a large menu of integrations and actions. The transcript highlights connections to Google Workspace (Calendar, Docs, Sheets, Tasks), Gmail, Slack, HubSpot, AWS-related tools, HTTP/custom API calls, webhooks, and more—plus “premium actions” gated behind higher tiers.

Finally, Lindy 2.0 is framed as credit-based automation: running AI tasks costs credits, with a free intro month (up to 400 credits) and paid plans that replenish monthly. The creator emphasizes that Lindy is early access, with new flow-chart features and ongoing improvements, and notes cross-device access via iOS and desktop apps for Mac and Windows. The overall message is that Lindy 2.0 aims to make AI-driven apps that can do real work—without constant oversight—by combining triggers, agent logic, and direct service permissions in one workflow builder.

Cornell Notes

Lindy 2.0 reframes AI from a chat-only tool into an automation platform that can execute multi-step workflows. Instead of relying on user-by-user prompting, Lindy uses a flow editor with triggers, AI agents, and “jump conditions” to decide when to move between steps. Agents can be configured with skills that grant direct access to services like Google Calendar and Google Docs, enabling actions such as checking schedules, creating events, and updating documents automatically. The transcript demonstrates both recurring automation (daily calendar summaries and emails) and on-demand automation (scraping AI news from multiple sources and writing it into a Google Doc). This matters because it turns AI outputs into real operational changes in external systems.

Why does Lindy 2.0 claim to be different from ChatGPT-style “AI assistants”?

ChatGPT-like tools generate responses based on prompts, but they don’t autonomously take actions in external systems. Lindy 2.0 is built around automation: a user-defined flow triggers an AI agent, and that agent can perform actions through configured “skills.” In the calendar example, the agent doesn’t just describe a schedule—it connects to Google Calendar, checks for conflicts, proposes best times, and creates events. That kind of direct read/write access is presented as the key gap versus typical chatbots.

How does the flow editor structure an automation?

A Lindy starts with a message or trigger node, which activates an AI agent. The agent runs until a “jump condition” is met, then the flow continues to the next node. In the daily calendar workflow, the trigger fires at 8:00 a.m., the agent checks the calendar and summarizes events, and only after that completion does the flow move to sending an email. The transcript emphasizes jump conditions as the mechanism that prevents workflows from getting stuck or skipping steps.

What can the calendar bot actually do with Google Calendar?

Configured skills let the bot create and manage events: create events, delete events, format events for display, get event details, list events, find best times to schedule, update events, and view calendars/events. In the demo, it answers “what’s my schedule for the rest of the week,” then handles “add a new event” by finding available times, asking which option to use, and creating the event with a link to details.

How does Lindy 2.0 handle recurring versus on-demand tasks?

Recurring tasks use a scheduling trigger (e.g., every day at 8:00 a.m.) that automatically launches an agent. On-demand tasks start when a user sends a message to the Lindy. The transcript shows both: a recurring morning summary that can email results, and a manual “news gatherer” that runs when the user asks it to find the latest AI news and update a Google Doc.

What does the “web monitoring” news example demonstrate about multi-step automation?

It demonstrates conditional extraction, multi-source searching, and document updates. The workflow extracts web page text, checks whether new content exists since the last run, and only then updates a Google Doc. The example expands to additional sources: it searches via Bing, extracts from an AI news site, and searches YouTube for AI news results, then writes a consolidated, date-stamped update into the same document.

How do credits and tiers affect what users can build?

Lindy uses a credit system because running large language models for automation is described as expensive. The transcript mentions a free intro month (up to 400 credits) and a $30/month plan with 3,000 credits/actions per month, with monthly replenishment. It also notes that knowledge-base indexing scales with paid tiers and that “premium actions” (like Lindy messenger, meeting recording, webhooks, and prospecting) require higher access.

Review Questions

  1. In Lindy’s flow editor, what role do “jump conditions” play in moving from one step to another?
  2. How does the calendar bot’s Google Calendar access differ from what a typical chat-only AI can do?
  3. What sequence of steps enables the news gatherer to detect new content and update a Google Doc automatically?

Key Points

  1. 1

    Lindy 2.0 is positioned as an automation platform where AI agents can execute actions in external tools, not just generate text.

  2. 2

    A flow editor combines triggers, AI agents, and “jump conditions” to control multi-step workflows reliably.

  3. 3

    Google Calendar “skills” enable full event management—checking schedules, proposing times, and creating/updating/deleting events.

  4. 4

    Recurring triggers (like daily at 8:00 a.m.) support autonomous routines such as daily summaries and email delivery.

  5. 5

    The web monitoring example shows conditional scraping and document updating, including multi-source aggregation (web + YouTube).

  6. 6

    Lindy’s integrations span major services (Google Workspace, Gmail, Slack, HubSpot) plus webhooks and custom API calls.

  7. 7

    Automation runs on a credit-based pricing model, with free trials and paid tiers that unlock additional capabilities and premium actions.

Highlights

Lindy’s calendar bot doesn’t merely answer scheduling questions—it checks Google Calendar, finds conflicts, proposes times, and creates events with links.
“Jump conditions” are presented as the mechanism that lets agents hand off to the next workflow step only after prerequisites are met.
The news gatherer pipeline can search multiple sources (Bing, an AI news site, and YouTube), then update a Google Doc with formatted, date-stamped results.
Lindy 2.0’s value proposition centers on direct service permissions (Calendar/Docs) plus workflow control, turning AI output into real system changes.

Topics

Mentioned

  • Matthew
  • GPT
  • GPT-4
  • GPT-4 Turbo
  • GPT-4o mini
  • Claude
  • HTTP
  • AWS
  • iOS
  • Mac
  • Windows