Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Granola

AI-powered meeting notes, automatically captures and summarizes your meetings.

CategoryProductivity
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Granola with Flows360

AI-powered meeting notes, automatically captures and summarizes your meetings.

Use the Granola connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 3 actions and 2 triggers.

Available actions

  • List Notes
  • Get Note
  • Custom API Call

Available triggers

  • New Note
  • Updated Note

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Granola
  • Package: @activepieces/piece-granola@0.1.0
  • Exact artifact digest: sha256:0d1e43ec48d82e004dc7c38a97e163c5398500e7a88e7f9ba68eaebf2931870c
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • List Notes (list_notes), List your meeting notes with optional date filters. Classification: read.
  • Get Note (get_note), Retrieve a single meeting note by its ID, with optional transcript. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Note, polling.
  • Updated Note, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects5
Supported actions3
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
List Notes Yes No List your meeting notes with optional date filters.
Get Note Yes No Retrieve a single meeting note by its ID, with optional transcript.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Note Yes No polling trigger declared by the pinned package.
Updated Note Yes No polling trigger declared by the pinned package.

Supported actions

List Notes · Read

List your meeting notes with optional date filters.

list_notes · Risk: low · Retry: safe

Inputs

  • created_after · string · Optional, Only return notes created after this date. Leave empty to return all notes.
  • created_before · string · Optional, Only return notes created before this date. Leave empty for no upper limit.
  • updated_after · string · Optional, Only return notes updated after this date. Useful to find recently modified notes.
  • page_size · number · Optional, Number of notes to return per page (1u201330).
Get Note · Read

Retrieve a single meeting note by its ID, with optional transcript.

get_note · Risk: low · Retry: safe

Inputs

  • note_id · string · Required, The ID of the note to retrieve. Starts with `not_` followed by 14 characters (e.g. `not_1d3tmYTlCICgjy`). You can get this from the **List Notes** action.
  • include_transcript · boolean · Optional, Include the full meeting transcript in the response. The transcript shows who said what and when.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Note · Poll

Triggers when a new meeting note is created in Granola.

Updated Note · Poll

Triggers when an existing meeting note is updated in Granola (e.g. summary edited, attendees changed).

Setup

Setup

  1. Add the Granola connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-granola@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 3 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Granola connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-granola@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com