Connect Slack to Fathom
When something happens in Slack, Notis takes the next step in Fathom. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Slack to Fathom
Pull a meeting recap from a channel request
When someone asks for a meeting recap in a Slack channel, retrieve the matching Fathom summary and deliver it where the team can use it.
Find exact meeting quotes from a DM
When a direct message asks for what someone said in a meeting, retrieve the Fathom transcript with speakers and timestamps for a precise answer.
Check meeting history from a channel question
Respond to channel questions about recent calls by listing matching Fathom meetings with useful date or attendee clues.
Retrieve a recap when a message gets a recap reaction
Use a chosen reaction on a meeting-related Slack message as a lightweight signal to retrieve its Fathom summary.
Verify a meeting decision in the transcript
When a Slack message asks whether a decision was actually made, retrieve the related Fathom transcript for verification.
Pull a customer call recap from a DM
When a DM asks what happened on a customer call, retrieve the matching Fathom summary for a quick, grounded catch-up.
List calls for a weekly review request
When a Slack channel asks for calls from a review period, list matching Fathom meetings to make weekly review easier to start.
Retrieve a transcript when a review reaction is added
Use a chosen reaction on a meeting-related Slack message to retrieve the matching Fathom transcript for a closer review.
Retrieve context for a team handoff
When a channel message requests handoff context from a meeting, fetch the Fathom summary to help the next owner pick up the thread.
Supported Triggers and Actions
Notis builds workflows that link Slack to Fathom. A trigger fires from one place; an action lands in another.
Slack triggers
Fathom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Webhook
Tool to delete an existing webhook by its ID. Use when you need to remove a webhook that is no longer needed.
New Channel Created Trigger
Triggered when a new channel is created in Slack.
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).
Channel Message Received
Triggered when a message is posted in a Slack channel (public, private, or multi-party IM). Does NOT match direct messages.
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.
Direct Message Received
Triggered when a new direct message (DM) is sent to a user in Slack. Catches all DMs across all DM channels.
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.
Message Reaction Added
Triggered when a reaction is added to a message in Slack. Supports optional filtering by channel and emoji name.
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.
Message Reaction Removed
Triggered when a reaction is removed from a message in Slack. Supports optional filtering by channel and emoji name.
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.
Reaction Added Trigger
DEPRECATED: use `SLACK_MESSAGE_REACTION_ADDED` instead. Triggered when a reaction is added to a message in Slack.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Slack and Fathom
Connect any two apps with Notis in the middle.
Slack 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.