Granola

• Import every Granola note you can see as an Atlas meeting, with its title, times, attendees, and folders.
• Bring the AI summary across as the meeting notes, and the transcript as a searchable transcript with speaker labels.
• Match an imported note to a meeting you already have, by calendar identifier first and then by time and title, instead of creating a duplicate.
• Offer the action items Granola found for approval. Nothing is turned into a task until you approve it.
• Keep working after you edit. A field you correct in Atlas stays corrected, and a later sync writes around it.

• You can sign in to Granola and open Settings, Connectors, API keys.
• You know which kind of key you want. A personal key reads notes you own or that were shared with you directly. A workspace key reads workspace-visible and Team space notes and can only be created by a Granola admin.
• You have decided whether to import transcripts. They are the most sensitive material this connector brings in, and the setting is offered at connect time.

1. Create the access key in Granola under Settings, Connectors, API keys.
2. Copy the key before closing the dialog, because Granola shows it once.
3. Choose the matching access level in Atlas.
4. Decide whether to import transcripts.
5. Paste the key and save.
6. Watch the first sync report a count on the connector card.

• The key stopped working

  A key revoked in Granola fails on the next call. Atlas moves the connection to an error state, stops syncing it, and tells the owner once rather than on every fifteen-minute tick. Already imported meetings are untouched. Paste a new key to resume.

• A recent call has not arrived

  Granola only serves a note once it has generated the summary and the transcript. Atlas records it as pending and retries, rather than reporting it as an error.

• Someone edited a meeting and the edit came back

  That should not happen, and it is worth reporting. An edit to a title, time, location, attendee list, or the notes is recorded and sync writes around it. Use Restore on the meeting to hand the field back to Granola deliberately.

• A workspace key sees fewer notes than a personal one

  That is expected. A workspace key cannot see other people private notes, so it is not a superset of a personal key. Removing a personal key genuinely loses coverage.

• The transcript names Other participants

  Granola labels each transcript line as microphone or speaker. When it supplies no speaker name, Atlas maps microphone to the connection owner and speaker to Other participants rather than inventing a name. The raw label is kept, so a better resolver can improve it later without re-fetching.

Atlas sets up one event notification address at Granola for each connection and checks the signature on every delivery. Each address carries its own private identifier, so a delivery is bound to exactly one connection and can never be applied to the wrong workspace.

Events Atlas listens for

• note.generated
• note.regenerated
• note.edited
• note.access_granted

Provider docs: https://www.granola.ai/

1. Click Disconnect on the Atlas Granola connector card. Atlas removes the event notification address at Granola, discards the stored key and signing secret, and clears the sync position.
2. Delete the key in Granola under Settings, Connectors, API keys if you want to revoke it there too.
3. Your imported meetings, transcripts, and the tasks made from them are kept, because they are your workspace data. Deleting Granola-sourced meetings is a separate action you have to confirm on its own.