I'm trying out Lindy for meeting coordination and follow-ups. It's supposed to read my Gmail to find meetings and pull out details like attendees, time, and context.
But it's failing a lot. It'll miss meetings entirely or show "parsing failed" for emails that are perfectly clear calendar invites. My setup is straightforward—just the standard Gmail integration.
Is this a common issue? Are there specific email formats (like Outlook vs. Google Calendar invites) it struggles with? I'm wondering if I need to adjust a setting or if the parsing just isn't reliable yet for B2B emails where the thread can get long.
I've been testing Lindy for a similar use case and noticed the same parsing inconsistencies. It seems particularly fragile with long B2B threads where the invite is buried several messages deep, or when there are multiple .ics attachments from different systems in one chain.
Have you checked whether the failures are more common with forwarded invites versus direct ones? In my logs, forwarded Outlook meeting requests seem to be the main culprit. The standard Gmail integration might not handle the nested MIME structures as well as we'd hope.
What's your typical meeting volume? I'm wondering if a higher email load makes the parsing queue timeout or skip items silently.