Georgiadis S.

Hey Talia, I've run into this before. Usually when sites and apps built through Lindy break or show up as broken, it comes down to one of a few things: the deployment step not completing cleanly, a skill configuration that's referencing something stale, or a prompt loop that's eating credits without actually fixing the issue. Happy to take a look with you and figure out what's going on so you're not burning credits troubleshooting blind. Here's my Calendly if you want to hop on a quick call: https://calendly.com/shilisia00

Sounds good Tim F.

Good news, Jeff B.. Granola's Zapier trigger sends the full transcript as part of the webhook payload. The data you get includes: the meeting title, creator, attendees, calendar event details, your personal notes, the full raw transcript, and a share link to the note. So for Option 1, you'd set up a Zap with either the "Note Added to Folder" trigger (auto-fires when a note hits a specific folder) or "Note Shared to Zapier" (manual trigger from the note sidebar). Either way, the raw transcript comes through and you can push it straight into Lindy via a webhook action in the Zap. If you want help wiring that up, happy to walk through it with you. https://calendly.com/shilisia00

Aaron W. Sounds good, happy to chat whenever you’re ready.

Hey Jeff B., I've looked into this. Granola doesn't have a native Lindy integration, but there are a couple of ways to connect them without Zapier. Option 1 (simplest): Use Lindy's webhook trigger. Create a Lindy agent with a Receive Webhook trigger. Then in Granola, use their Slack integration to post meeting notes to a Slack channel. Set up a second Lindy agent that triggers on new Slack messages in that channel and passes the content to your main workflow. It's Slack as the bridge instead of Zapier. Option 2 (more direct): Granola has an MCP (Model Context Protocol) server that exposes your meeting notes. Lindy doesn't natively consume MCP yet, but you could use Lindy's HTTP Request action to hit Granola's API endpoints directly. The credentials are stored locally in your Granola app at Library/Application Support/Granola/supabase.json. You'd set up a scheduled Lindy agent that polls for new transcripts using those credentials and processes them. Option 3: If you're on Granola Enterprise, they have a proper API for programmatic access to workspace notes. You could connect that directly to Lindy via HTTP Request actions on a schedule. Option 1 is the fastest to set up. Option 2 gives you the most direct pipeline. Happy to help you wire either one up if you want to dig in.

Hey Tim F., i've run into Google Drive connection issues in Lindy before. A few things to try: First, re-authorizing sometimes doesn't fully refresh the token. Try completely DISCONNECTING the Google Drive connection in Settings → Connections, then reconnecting from scratch. This forces a fresh OAuth handshake with new scopes. Second, check if Google changed anything on your end. Go to myaccount.google.com/permissions and look for Lindy in the list of third-party apps. Revoke access there first, then reconnect in Lindy. This clears the old token on Google's side too. Third, if you're on Google Workspace (not personal Gmail), your admin might have recently tightened third-party app access policies. Check with your IT admin or go to Admin Console → Security → API Controls → App Access Control to see if Lindy got restricted. If none of those work, it could be a Lindy platform issue with their Google Drive connector. I'd open a support ticket with the screenshot and mention it started a few weeks ago without any changes on your end. They can check their API logs server-side. Happy to take a closer look if you're still stuck after trying these.

Thanks, Aaron W.. Good questions. On CRMs, the current build runs on HubSpot, but Lindy also connects to Salesforce, Pipedrive, and a few others natively. The agent logic stays the same, you'd just swap the CRM actions. Regarding the no-CRM scenario, that's actually simpler to set up. The intel output (company research, decision-maker profiles, talking points) can go straight to a Google Sheet, Notion, Airtable, or even just a daily email/Slack digest. The research and enrichment engine doesn't care where the results land. If you've got an audience and want to know more about who they are or surface outreach opportunities from that list, this type of agent works well for that. Happy to chat through what that would look like for your setup if you're interested. https://calendly.com/shilisia00