Sign inStart your trial

FathomFathom
01Integration field card

Fathom Meeting Automation & Approval Workflows

Run Fathom on autopilot. Keep the veto.

7 actions

Meeting summaries and transcripts sit in Fathom while decisions wait; Rills proposes what to do with them and you approve before anything goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential other action from Fathom arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

FATHOM · SUMMARY ROUTING
82

Route 3 call summaries to client threads in your CRM?

3 meetings closed in last 6 hours with no follow-up queued

Transcripts confirmed complete; no flagged misquotes

Same routing pattern approved for last Tuesday's calls

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Fathom automation

Meeting recordings pile up after every sales call, onboarding session, and team standup, and the notes inside them have real consequences if they get routed to the wrong person or trigger a follow-up you wish you'd reviewed first.

When Fathom runs unsupervised

Fathom captures everything, but acting on that content without a checkpoint is where things go wrong. A summary goes out to a client before you've confirmed the transcript is accurate, or a webhook fires against meeting content you haven't cleared.

  • Get Recording Summary routes a call summary to a client thread before you've confirmed the AI captured the right decisions.
  • Get Recording Transcript feeds a raw transcript into a follow-up sequence that sends before you spot the misquote.
  • Create webhook for meeting content fires against meeting data the moment a recording lands, with no pause for your review.
  • Delete Webhook removes a connection mid-workflow, breaking a downstream process you didn't know depended on it.
  • List Team Members exposes who has access to recordings in ways that can surprise you when permissions have drifted.

What Rills does inside Fathom

Rills sits between Fathom and whatever comes next. When a recording summary is ready or a transcript is pulled, Rills drafts the proposed action, whether that's routing the summary, adjusting team access via List Team Members, or queuing a follow-up, and waits for your call before anything ships.

The transcript still gets used; you just approve Fathom's next move before it reaches anyone.

Why Fathom has no triggers and how Rills fills the gap

Fathom does not emit events that can start a workflow on their own, so without a layer on top, you either act manually or nothing happens. Rills fills that gap by polling and scheduling checks that keep Fathom automation moving without running unsupervised.

  • List Meetings runs on a schedule to surface new recordings and propose next steps for any meeting that hasn't been actioned yet.
  • Get Recording Summary is polled after a set delay, giving you time to review before Rills proposes routing the summary anywhere.
  • List Teams checks periodically for membership changes that might affect who can see sensitive recordings, then queues an approval before access is updated.
  • Get Recording Transcript is triggered by an upstream event in another tool, so Fathom content flows into your other workflows only after you've reviewed the proposal.
04. Actions

What Rills can do in Fathom

2 of 7 actions across reads, writes, and updates.

  1. 01

    Get Recording Transcript

    Retrieve the complete transcript of a specific meeting recording with speaker identification and timing information. Use this to access detailed meeting notes without downloading large batches of data.

  2. 02

    List Meetings

    Retrieve all your meeting recordings with optional filtering by date, domain, or meeting type to organize and review your conversations.

05. FAQ

Common questions about Fathom automation

06. NEXT MOVE

Approve every Fathom change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.