Integrations
Connecting to Granola
Meeting notes, summaries and transcripts, so follow-ups start from what was actually said.
Connect Granola and Gini can read your meeting notes, summaries and transcripts, so the work that follows a call starts from what was actually said.
Read-only, by construction
This connection has no write operations at all. Gini can read your meetings and it cannot create, change or delete anything in Granola, whatever it is asked. That is the connection itself, not a setting.
What it can do
- List meetings. By date, folder, or search.
- Read a transcript in full. Not just the summary.
- Query across meetings. "When did we discuss the migration timeline?"
- Read folders. However your team organises calls.
How to connect
Open Integrations
app.ginicomputer.com → Integrations → Granola.
Sign in to Granola
Granola's own screen handles the authorisation.
Come back
Gini can now work from your meetings.
What changes anything
| Operation | What it does | Changes anything? |
|---|---|---|
| List meetings | Find calls by date or folder | No |
| Search meetings | Find calls by what was said | No |
| Get transcript | Read one call in full | No |
| List folders | See how meetings are organised | No |
| Get account info | Identify the connected account | No |
What it's great for
- Following up properly. "Draft the follow-up from the Northwind call, and reference what they pushed back on." The difference between this and a generic follow-up is the reason anyone reads it.
- Not losing the commitments. "What did we promise on the Acme call?" A meeting produces obligations, and the gap between the meeting and someone acting on them is where most of them die.
- Finding the thing you half-remember. "We talked about the migration timeline at some point. When, and what did we land on?" Transcripts are searchable in a way that memory is not.
- Prep from history. "Before this call, what did we discuss last time and what is still open?"
- Catching up on a call you missed. Without watching it.
Example routine
The post-meeting loop. This is the one to build first, because it runs several times a week and nobody enjoys any part of it:
- After each call, read the Granola transcript.
- Log the call on the HubSpot or Attio record.
- File the action items in Linear.
- Draft the follow-up email and hold it for approval.
Run it by hand twice and Gini will offer to take it over. See Routines.
Good to know
- It works within your Granola access. Meetings your account cannot see stay invisible to Gini.
- Transcripts are long, and reading costs credits. A question across a quarter of calls costs meaningfully more than one about yesterday. Scope the window when you can. See How credits work.
- The transcript is the source, not the summary. When accuracy matters, ask Gini to quote. A summary of a summary drifts.
- Everyone in the channel sees the answer. Meeting content can be sensitive, so think about the room before asking there rather than in a DM.
Troubleshooting
Gini can't find a meeting
Check that your Granola account has it. Calls recorded by a colleague on their own account are not visible to yours, and so not to Gini either.
The transcript looks incomplete
That is Granola's capture rather than Gini's reading. Check the meeting in Granola directly.
It is slow on "what did we say about X"
That question reads across many transcripts. Narrowing it to a period or a folder is both faster and cheaper.