Skip to main content

Granola API Data Source

The Granola API connector enables you to ingest meeting notes, transcripts, and AI-generated summaries from your Granola workspace into Nexla data flows. Follow the instructions below to create a new data flow that ingests data from a Granola API source in Nexla.
granola_api.png

Granola API

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Granola API connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Granola API, and click Next; or, create a new Granola API credential for use in this flow.

  3. In Nexla, Granola data sources can be created using pre-built endpoint templates, which expedite source setup for common Granola endpoints. Each template is designed specifically for the corresponding Granola endpoint, making data source setup easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Granola sources can also be configured manually, allowing you to ingest data from Granola endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Granola endpoints. Each template is designed specifically for the corresponding Granola endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    List notes

    Retrieves a paginated list of notes from the Granola API. Use this endpoint to ingest meeting notes in bulk, with optional filtering by creation or update time and cursor-based pagination for large note collections.

    • Sends a GET request to https://public-api.granola.ai/v1/notes with optional query parameters for date filtering (Created Before, Created After, Updated After) and pagination (Cursor, Page Size).
    • Response data is extracted from $.notes[*], returning each note as an individual record.
    • Configure the following parameters: Created Before — filter notes created before this date/time. Created After — filter notes created after this date/time. Updated After — filter notes updated after this date/time. Cursor — pagination cursor returned by a prior response. Page Size — number of notes to return per page.

    Use the Created After or Updated After parameters with date/time macros to perform incremental ingestion — fetching only notes created or updated since the last run.

    Get note

    Retrieves a single note by its unique ID, with an option to include related data such as transcript segments or AI summaries. Use this endpoint when you need the full details of a specific meeting note.

    • Sends a GET request to https://public-api.granola.ai/v1/notes/{id} with an optional include query parameter for embedding related data.
    • Response data is extracted from $, returning the full note object as a single record.
    • Configure the following parameters: Id — the unique identifier of the note to retrieve. Include — optional comma-separated list of related resources to embed in the response (e.g., transcript, summary).

    The note Id can be obtained from the List notes endpoint. Use a lookup macro to pass IDs dynamically when chaining API calls.

    List folders

    Returns a paginated list of all folders in the Granola workspace. Use this endpoint to discover folder structures and retrieve folder IDs for use in folder-scoped data pipelines.

    • Sends a GET request to https://public-api.granola.ai/v1/folders with optional Page Size and Cursor pagination parameters.
    • Response data is extracted from $.folders[*], returning each folder as an individual record.
    • Configure the following parameters: Page Size — number of folders to return per page. Cursor — pagination cursor returned by a prior response to retrieve the next page.

    Folder IDs returned by this endpoint can be used as input to the Get folder notes endpoint to retrieve all notes belonging to a specific folder.

    Get folder notes

    Retrieves the notes belonging to a specific folder, enabling folder-scoped data pipelines to access only the notes within a given folder.

    • Sends a GET request to https://public-api.granola.ai/v1/folders/{id}/notes where {id} is the folder identifier.
    • Response data is extracted from $.notes[*], returning each note in the folder as an individual record.
    • Configure the following parameters: Id — the unique identifier of the folder whose notes should be retrieved.

    Use the List folders endpoint to obtain folder IDs. You can use a lookup macro to pass the folder ID dynamically if iterating over multiple folders.

    Retrieve the full raw transcript segments for a specific note

    Retrieves the full raw transcript segments for a specific note, separate from the AI-generated summary. Use this endpoint for downstream NLP processing, transcript archiving, or custom analysis of meeting speech.

    • Sends a GET request to https://public-api.granola.ai/v1/notes/{id}/transcript where {id} is the note identifier.
    • Response data is extracted from $.transcript[*], returning each transcript segment as an individual record.
    • Configure the following parameters: Id — the unique identifier of the note whose transcript should be retrieved.

    The note Id can be obtained from the List notes endpoint. Transcript data is only available for notes that have a completed AI summary and transcript.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Granola API sources can be configured to ingest data from any valid Granola API endpoint. Configuration options available for Granola API sources allow them to be fully customized to suit any use case—including using chained API calls to fetch data from multiple endpoints or sources that require custom authentication headers or request parameters.

First, select the API method that will be used for calls to the Granola API from the Method pulldown menu. The Granola API uses POST for all of its data-retrieval endpoints, which is the correct method for most Granola sources:

  • POST: Required for all standard Granola API data-retrieval endpoints, including notes listing, transcript retrieval, and document metadata.
  • GET: Used only for specific utility endpoints. Consult the Granola API documentation to confirm the method required for a specific endpoint.

API Endpoint URL​

  1. Enter the URL of the Granola API endpoint from which this source will fetch data in the Set API URL field. The Granola API base URL is https://public-api.granola.ai. Below are the most commonly used Granola API endpoints for data ingestion:

    • https://public-api.granola.ai/v2/get-documents — Retrieves a paginated list of meeting notes from your workspace. This is the primary endpoint for ingesting meeting records and should be used as the starting point for most Granola data flows.

    • https://public-api.granola.ai/v1/get-document-transcript — Retrieves the full transcript for a specific meeting, including speaker labels and timestamped segments.

    • https://public-api.granola.ai/v1/get-document-metadata — Retrieves metadata for a specific meeting document, including participant information and meeting details.

    • https://public-api.granola.ai/v2/get-document-lists — Retrieves workspace folder and list structures, useful for understanding how notes are organized in your workspace.

    The Granola API returns only meeting notes that have a generated AI summary and transcript. Notes that are still being processed or were never summarized will not appear in responses.

Request Body​

  1. Many Granola API endpoints require a JSON request body to specify parameters such as pagination cursors or document IDs. Enter the required request body in the Request Body field using JSON format.

    For the POST /v2/get-documents endpoint, the request body supports the following parameters:

    • limit (optional): The maximum number of documents to return per page. Defaults to 20. Enter a value up to 100 for larger batches.

    • cursor (optional): A pagination cursor returned by a previous response. Use this value to retrieve the next page of results when iterating through large note collections.

    Example request body for listing documents:

    {"limit": 100}

    For the POST /v1/get-document-transcript endpoint, the request body requires:

    • documentId (required): The unique identifier of the meeting document for which to retrieve the transcript. This ID is returned in the id field of the get-documents response.

    Example request body for retrieving a transcript:

    {"documentId": "your-document-id-here"}

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Macros are particularly useful when constructing Granola API requests that filter notes by date range, or when pagination parameters need to reference dynamic values that change between data ingestion runs.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are particularly useful for Granola sources when you need to retrieve transcripts or metadata for specific document IDs sourced from a prior Granola get-documents ingestion step.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data returned by the Granola API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when API responses contain pagination metadata or wrapper objects that you don't need for your analysis.

For example, the POST /v2/get-documents endpoint returns a JSON response with a top-level docs array containing the meeting records, along with a nextCursor pagination token. By entering the path to the docs array, you can configure Nexla to treat each element of the array as a separate record.

Path to Data is essential for Granola API responses, which wrap the actual data within nested objects. Without specifying the correct path, Nexla may not be able to properly parse and organize your meeting records.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For the POST /v2/get-documents endpoint, enter $.docs[*] to extract the array of meeting documents.

    • For the POST /v1/get-document-transcript endpoint, enter $.transcript[*] to extract the array of transcript segments.

    • For responses in JSON format, enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.data.items[*] to access an array of items within a data object).

    Path to Data Example:

    For the Granola get-documents endpoint, the response includes a top-level docs array that contains the meeting records. Enter $.docs[*] as the path to data so that each meeting document is treated as an individual record in the Nexset.

Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

    PathSuggestions.png

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records but isn't part of the main data array.

For example, the Granola get-documents response includes a nextCursor pagination token at the top level of the response, alongside the docs array. If you have specified $.docs[*] as the path to relevant data, you can specify a path to nextCursor or other top-level fields to include them as metadata in each record.

Metadata paths are particularly useful for preserving Granola API response context like pagination cursors, total record counts, or request timestamps that apply to all records in the response.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). For the Granola API, the Content-Type: application/json header is typically required when sending a JSON request body.

    You do not need to include the Authorization header in the Request Headers field, as Nexla automatically applies the API key from your Granola API credential to all requests. Common headers like Authorization are handled automatically based on your credential configuration.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

The Granola API applies rate limits per user or workspace depending on the key's access scope. If a test returns a 429 Too Many Requests error, wait briefly before retrying. For additional information about Granola API rate limits, refer to the Granola API documentation.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Create button in the upper right corner of the screen to save and create the new Granola API data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.