Skip to content
Notis

Ground interview debriefs in the conversation

Start an interview debrief with the relevant Fathom summary and spend less energy reconstructing what stood out.

Trigger

New Page

Triggers when a new page is added to a Notion database.

Action

Get Recording Summary

Tool to retrieve the AI-generated summary for a specific recording. Use when you need to access the summary of a meeting recording. Supports both synchronous mode (returns summary directly) and asynchronous mode (delivers summary to webhook URL specified in destination_url parameter).

Why this helps

Interview impressions fade quickly, and writing a useful debrief can feel like another task after a full day.

  • Recall what was discussed while evaluating a candidate.
  • Reduce the effort of starting a debrief.
  • Keep review more consistent across interviews.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Fathom to Notis once in the portal.
  • 2Create an automation in the portal or ask Notis conversationally.
  • 3Ask Notis in one instruction to retrieve the Fathom summary for the interview referenced by each new debrief page.
  • 4Select the Notion New Page trigger and choose a channel for run reports.
  • 5Test using a debrief page for a recorded interview.

Questions about this workflow

Does this score or rank candidates?

No. It retrieves meeting context to support your own review.

What details help find the recording?

A candidate name, interview date, or clear meeting title can help identify the right Fathom call.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Fathom. A trigger fires from one place; an action lands in another.

Notion triggers

Fathom actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create webhook for meeting content

Tool to create a webhook to receive new meeting content from Fathom. Use when you need to set up notifications for meeting recordings. At least one of transcript, CRM matches, summary, or action items must be included in the webhook payload.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Webhook

Tool to delete an existing webhook by its ID. Use when you need to remove a webhook that is no longer needed.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Recording Summary

Tool to retrieve the AI-generated summary for a specific recording. Use when you need to access the summary of a meeting recording. Supports both synchronous mode (returns summary directly) and asynchronous mode (delivers summary to webhook URL specified in destination_url parameter).

ActionInstant

Comment Created

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

TriggerInstant

Get Recording Transcript

Tool to retrieve the full transcript for a specific recording. Use when you need to access the complete meeting transcript with speaker information and timestamps. Can operate synchronously (returns transcript directly) or asynchronously (posts transcript to a destination URL). In the response, speaker is an object — access speaker.display_name rather than treating speaker as a string. Prefer this tool over fetching transcripts via list-meetings calls with include_transcript=true, which produces extremely large responses when many meetings are returned.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

List Meetings

Tool to retrieve a paginated list of meeting recordings for the authenticated user or organization. Use when you need to fetch meetings with optional filtering by dates, domains, meeting type, or recorder. Supports data enrichment via include_* parameters.

ActionInstant

Database Created

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

TriggerInstant

List Team Members

Tool to retrieve a paginated list of all team members in the organization. Use when you need to view team members, optionally filtered by team name or paginated using a cursor.

ActionInstant

Data Source Created

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

TriggerInstant

List Teams

Tool to retrieve a paginated list of all teams in the organization. Use when you need to get information about teams accessible through the API.

ActionInstant

Data Source Schema Updated

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

TriggerInstant

Connect any two apps with Notis in the middle.

Notion and Fathom, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Fathom.