Granola creates AI-generated meeting notes, summaries, and transcripts. The Granola app connector lets your Lovable app read meeting context from your Granola workspace using a managed workspace-level connection, so the decisions, requirements, and follow-ups from a meeting flow straight into the product you’re building.Documentation Index
Fetch the complete documentation index at: https://docs.lovable.dev/llms.txt
Use this file to discover all available pages before exploring further.
This page covers Granola as an app connector, which provides meeting context both while you build and inside your deployed app. Granola is also available as a chat connector, which only provides meeting context to the Lovable agent while you build.
- Retrieve AI-generated meeting notes and summaries
- Access full meeting transcripts on demand
- Build workflows around meeting intelligence
- Sync action items and notes into your product
Common use cases and example apps
| Example app | Example prompt | Description |
|---|---|---|
| Customer call to product change | Use Granola and build the onboarding flow Lisa described in our call yesterday. Pull the notes from Granola. | Turn discovery-call decisions into working code the same day. The app pulls the relevant Granola note, extracts the requested changes, and applies them to the product. |
| Sprint planning to prototype | Use Granola and create the dashboard layout we agreed on in standup this morning. | Build from what was actually agreed in a meeting, not from memory. The app pulls the standup note from Granola and turns the agreed scope into a first-pass prototype. |
| Client feedback to build | Use Granola and implement the navigation changes from the design crit we just had with the client. | Move client feedback from a meeting straight into the build. The app reads the crit notes, identifies the requested changes, and applies them without a separate spec doc. |
| Action item tracker | Use Granola to pull action items from recent meeting notes and turn them into a task board. | Turn meeting follow-ups into trackable work. The app reads Granola summaries and organizes follow-up items so teams can assign, review, and complete them. |
| Customer call archive | Use Granola and build a customer meeting archive with search by account, date, and topic. | Make customer conversations easier to find. The app pulls transcripts and summaries from Granola so customer-facing teams can review prior calls without searching manually. |
| Product decision log | Use Granola to find product decisions from recent meeting notes and show them in a decision log with links to the source note. | Preserve meeting decisions in a structured format. The app extracts relevant summaries and lets teams browse past decisions with source context. |
| Weekly meeting digest | Use Granola and create a weekly digest that summarizes key topics, decisions, and next steps from recent meetings. | Summarize multiple meetings into one review flow. The app retrieves recent Granola notes and turns them into a concise recurring digest. |
| CRM note sync | Use Granola so that after a customer call, the Granola summary and transcript appear in the account timeline. | Keep customer records aligned with meeting context. The app uses Granola meeting data to enrich CRM-style records with notes, summaries, and next steps. |
How Granola connections work
Each Granola connection uses one Granola API key. The data available to your app depends on the API key type and the permissions of the Granola account or workspace behind that key. Granola supports two API key types:| API key type | Who can create it | Granola plan required | What it can access |
|---|---|---|---|
| Personal API key (Beta) | Any Granola workspace member | Granola Business or Enterprise | Notes you own, notes directly shared with you, and notes in private folders shared with you |
| Enterprise API key | Granola workspace admin | Granola Enterprise | All notes in the Team space |
How to connect Granola
Workspace admins and owners can connect Granola. You can create multiple Granola connections using different API keys. This makes it easy to create separate connections for API keys with different Granola access scopes, for example one connection for personal notes and another for the full Team space. When the connection is created, Granola can be linked to any project in the workspace. Multiple projects can use the same connection.Prerequisites
Before connecting Granola, make sure you have:- A Granola workspace on a plan that supports the API key type you want to use
- A Granola API key
- Lovable workspace admin or owner role
All API requests made through this connector use your Granola API key. API usage counts toward your Granola plan limits and billing is handled directly by Granola, not Lovable.
Step 1: Create a Granola API key
A Granola API key lets your Lovable app authenticate with Granola and read your meeting notes, summaries, and transcripts. Granola API keys are created in the Granola desktop app. To create a Granola API key:- Open the Granola desktop app and click on your workspace name.
- Go to Settings → Connectors → API.
- Click Create new key.
- Choose a key type if Granola prompts you.
- Click Generate API Key.
- Copy the generated key and store it securely.
Your Granola API key functions like a password. Keep it secure, do not share it publicly. You’ll need it in the next step.
Step 2: Connect Granola in Lovable
You can create multiple connections using different Granola API keys.- Open Connectors → App connectors and select Granola.
- Click Add connection.
- Display name: Name the connection, for example
Granola Team Notes. - API key: Enter your Granola API key (
grn_xxxxxxxx…). - Who can access this connection: Keep access limited to specific people or invite the entire workspace. See Connection-level access for more information
- Click Connect.
Available data
Through the Granola connector, your app can access meeting data that the connected API key is allowed to read.| Data | Description |
|---|---|
| Notes | Meeting notes available to the connected Granola API key |
| AI summaries | Granola-generated summaries for processed meetings |
| Transcripts | Full meeting transcripts when requested |
| Owners | The note owner name and email when provided by Granola |
| Meeting metadata | Fields returned by the Granola API, such as note IDs and titles |
Limitations
The Granola connector cannot:- Create, update, or delete Granola notes (read-only access)
- Return notes that have not finished processing. Granola only returns notes that have a generated AI summary and transcript. Unprocessed notes are excluded from the list.
- Support per-end-user Granola login (each end user connecting their own Granola account)
- Exceed Granola’s API rate limits. Granola API rate limits apply to requests made through the connector.
- Lovable gateway limits also apply. See Gateway-based connectors for details.
How to unlink projects from a connection
Editors and above can remove specific projects from a connection without deleting the connection entirely. The connection will remain available for other projects. To unlink projects:
When unlinked, those projects will no longer have access to through this connection. If a project needs again, you can link it to any available connection.