Lindy gets the inbox right and the listener almost right

The email core is genuinely push

Lindy's strongest primitive is its Gmail integration. The email trigger (onGmailMessageReceived) uses Google's Pub/Sub push notifications, which means Gmail sends Lindy a notification the moment a message arrives. No polling interval, no 15-minute delay. The agent fires immediately.

For a product whose core use case is email triage, this is the right call. Email is the one integration where latency actually matters to users. When your VP replies at 2pm, you want the draft response generated now, not in 15 minutes. Lindy nails this. The triage, prioritization, and draft-reply workflow is fast enough that several users report their colleagues assuming they type faster than they actually do.

The scheduling integration works the same way. Calendar availability checks, meeting coordination, reschedule handling. These tap into Google Calendar APIs that support real-time access, and the experience is smooth. Lindy can negotiate meeting times over text message in a way that feels like having an actual assistant.

Beyond email, the picture changes

When I set up a Confluence watcher, the trigger configuration was straightforward. Connect your account, pick the pages to monitor, and Lindy starts watching. What caught my eye was a field at the bottom of the setup: "Polling schedule (In Seconds)" with a default of 900. That's 15 minutes.

The Notion integration is similar. Lindy's own documentation confirms that all seven Notion trigger types (new database item, updated page, new comment, and four others) check every 10 minutes for changes. The docs are transparent about this. It's polling.

This isn't a Lindy-specific problem. Confluence doesn't offer webhooks in all deployment configurations. Notion's API has rate limits that make aggressive polling impractical. Many of the 2,500+ integrations Lindy gained through its Pipedream partnership inherit Pipedream's trigger model, which uses polling for providers that don't support webhooks natively.

The result is a product where the user experience feels uniform, but the underlying architecture isn't. The email agent reacts in seconds while the Confluence watcher takes minutes, and a Notion monitor might miss a rapid sequence of changes between polling intervals entirely. None of this is surfaced to the user in a way that sets expectations. The agent builder doesn't distinguish between "this trigger fires in real time" and "this trigger checks every N seconds."

For a morning briefing workflow, the distinction barely matters. For an agent that's supposed to catch a production incident summary the moment it's posted to a Confluence page, 15 minutes is a long time.

Running the scorecard

We've been using a three-question framework to evaluate products that claim to be proactive. Here's how Lindy lands.

Clock: Yes. Lindy can wake itself up on schedules, intervals, and in response to time-based conditions. The overnight email digest, the morning meeting prep, the weekly CRM update. The clock is solid, and the scheduling agent that negotiates meeting times is one of the most polished schedule-aware features in any AI assistant.

Listener: Partial. This is where it gets nuanced. For email, the listener is real. Push-based, low-latency, properly event-driven. For everything else, the listener is a polling loop with a configurable interval. Confluence at 900 seconds. Notion at 600 seconds. The architecture does the right thing for the core use case and compromises everywhere else, which is a defensible product decision but not the same as having a real listener across the board.

Inbox: Yes, and then some. Lindy delivers through iMessage, SMS, Slack, email, and its own web interface. The delivery channel is contextual. Urgent items get pushed to your phone. Summaries land in Slack. Draft emails sit in your inbox waiting for approval. Multi-channel delivery is one of Lindy's genuine differentiators, and the iMessage integration is the best version of "meet the user where they are" that I've seen in this space.

What Lindy chose and what it traded

Lindy made a product bet that's worth naming: optimize the consumer experience first, build the infrastructure as needed. This is the opposite of the approach Notion took when it shipped composable building blocks and let developers wire their own proactive behavior. Lindy gives you a polished agent that works today for the use cases most people care about.

That bet has real strengths. Onboarding is fast, the iMessage integration means adoption doesn't require changing your workflow, and the agent builder lets non-technical users create sophisticated automations without ever thinking about webhooks or polling intervals. For that audience, Lindy is one of the best options available. The Zapier review captures this well: "you'll probably like Lindy if your life is mostly email, calendar, and meetings, and you'd rather delegate via text than learn another dashboard."

The trade is in the infrastructure layer. Lindy's state management between agent runs is opaque to users. You can't inspect what an agent remembers from its last execution, and the persistence model isn't documented in a way that lets you reason about it. When agents fail mid-execution, the recovery behavior varies by integration. The credit-based pricing means an agent that polls aggressively or triggers frequently can run up costs in ways that are hard to predict. G2 reviewers cite cost unpredictability as the top concern, with 42 mentions of "expensive" and 35 of "high subscription cost."

The security model is another area where consumer polish and infrastructure depth pull in different directions. Lindy needs broad permissions to read your email, calendar, and connected apps. The OAuth scopes are wide because the product needs them to be useful. But the per-agent permission model isn't granular enough for teams that want their email triage agent to have different access than their CRM update agent. The three-primitives framework calls out scoped auth per agent as a requirement for proactive systems, and Lindy doesn't quite get there yet.