Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Fathom

Fathom is an AI meeting assistant that automatically records, transcribes, highlights, and generates AI summaries and action items from your meetings. Integrate with workflows to react to meeting events and retrieve meeting data.

CategoryProductivity
AuthenticationOAuth 2.0, custom
Version0.2.4
Published scopes1 published scope
Last updatedSeptember 30, 2026

Overview

Connect Fathom with Flows360

Fathom is an AI meeting assistant that automatically records, transcribes, highlights, and generates AI summaries and action items from your meetings. Integrate with workflows to react to meeting events and retrieve meeting data.

Use the Fathom 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 5 actions and 1 trigger.

Available actions

  • Get Recording Summary
  • Get Recording Transcript
  • List Meetings
  • Find Team
  • Find Team Member

Available triggers

  • New Recording

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: Fathom
  • Package: @activepieces/piece-fathom@0.2.4
  • Exact artifact digest: sha256:b779f10b7ac95dcd278002c6fb84d58049b20e0295535417917c37951ab6191b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2, 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

  • Get Recording Summary (getRecordingSummary), Get the AI-generated summary of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2. Classification: read.
  • Get Recording Transcript (getRecordingTranscript), Get the AI-generated transcript of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2. Classification: read.
  • List Meetings (listMeetings), List meetings with optional filtering and pagination Classification: read.
  • Find Team (findTeam), Find team based on name Classification: read.
  • Find Team Member (findTeamMember), Find team member based on email Classification: read.

Trigger contracts

  • New Recording, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

AuthenticationOAuth 2.0, custom
Supported objects6
Supported actions5
Triggers1

Authentication

Authentication method: OAuth 2.0, custom

Required scopes

public_api

Authentication profiles

connection · oauth2

OAuth scopes: public_api

connection_2 · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Recording Summary Yes No Get the AI-generated summary of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2.
Get Recording Transcript Yes No Get the AI-generated transcript of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2.
List Meetings Yes No List meetings with optional filtering and pagination
Find Team Yes No Find team based on name
Find Team Member Yes No Find team member based on email
New Recording Yes No webhook trigger declared by the pinned package.

Supported actions

Get Recording Summary · Read

Get the AI-generated summary of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2.

get_recording_summary · Risk: low · Retry: safe

Inputs

  • recording_id · string · Required, Select the meeting recording to get the summary for
  • destination_url · string · Optional, Optional: URL where Fathom will POST the summary. Leave empty to get data directly in response.
Get Recording Transcript · Read

Get the AI-generated transcript of a meeting recording. Note: This action requires API Key authentication and is not available when using OAuth2.

get_recording_transcript · Risk: low · Retry: safe

Inputs

  • recording_id · string · Required, Select the meeting recording to get the transcript for
  • destination_url · string · Optional, Optional: URL where Fathom will POST the transcript. Leave empty to get data directly in response.
List Meetings · Read

List meetings with optional filtering and pagination

list_meetings · Risk: low · Retry: safe

Inputs

  • calendar_invitees · array · Optional, Email addresses of calendar invitees to filter by
  • calendar_invitees_domains · array · Optional, Domains of the companies to filter by (e.g., acme.com)
  • calendar_invitees_domains_type · string · Optional, Filter by whether calendar invitee list includes external email domains
  • recorded_by · array · Optional, Email addresses of users who recorded meetings
  • teams · array · Optional, Team names to filter by (e.g., Sales, Engineering)
  • created_after · string · Optional, Filter to meetings created after this timestamp (e.g., 2025-01-01T00:00:00Z)
  • created_before · string · Optional, Filter to meetings created before this timestamp (e.g., 2025-01-01T00:00:00Z)
  • include_transcript · boolean · Optional, Include the transcript for each meeting
  • include_summary · boolean · Optional, Include the summary for each meeting
  • include_action_items · boolean · Optional, Include the action items for each meeting
  • include_crm_matches · boolean · Optional, Include CRM matches for each meeting
  • cursor · string · Optional, Cursor for pagination (from previous response)
Find Team · Read

Find team based on name

find_team · Risk: low · Retry: safe

Inputs

  • cursor · string · Optional, Cursor for pagination (from previous response)
Find Team Member · Read

Find team member based on email

find_team_member · Risk: low · Retry: safe

Inputs

  • team · string · Optional, Team name to filter by
  • cursor · string · Optional, Cursor for pagination (from previous response)

Triggers

New Recording · Webhook

Fires when a meeting is recorded (i.e. a new meeting recording is produced)

Inputs

  • triggered_for · array
  • include_transcript · boolean
  • include_summary · boolean
  • include_action_items · boolean
  • include_crm_matches · boolean

Setup

Setup

  1. Add the Fathom 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.

OAuth scopes

  • public_api
  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-fathom@0.2.4; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 1 trigger 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.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Fathom 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-fathom@0.2.4 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