integrations

Connect Granola with an API key

Connect Granola using a customer-provided API key.

Every call creates an installation, also for a key already connected, e.g. the same notes feeding a second store. To replace an existing installation's key, e.g. after it expired, use POST /v1/integrations/granola/installations/{installation_id}/reconnect instead: connecting the new key would add an installation next to the old one.

post/v1/integrations/granola/connect

Request body

api_keystring required

Granola API key

store_namestring nullable

Ingestion store name. A store that already exists is shared: every data source connected to it ingests into it, except another installation of the same account, which would ingest every item again. Without it, the account's default store, numbered past a store another installation of the account feeds. Rejected with 422 when the connect refreshes an existing installation and names a store other than its own.

new_storeboolean

Ingest into a store created for this connection: the connect fails with 409 when store_name names a store that already exists, and without store_name the default name is numbered past existing stores. Rejected with 422 when the connect refreshes an existing installation, which keeps its store.

sync_schedule_interval'off' | 'ten_minutes' | 'hourly' | 'daily' | 'weekly'

Initial periodic sync interval

account_namestring nullable

Name of the person the API key belongs to

account_emailstring nullable

Email of the person the API key belongs to

Response

The connected Granola installation

Changes