[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Rewrite Fathom call summaries for the client

> Regenerate Fathom summaries with your own instructions, tone and a Next steps section, call by call or kept for future calls. Weekly run.

Source: https://cotlet.dev/integrations/fathom-video-api-mcp-server/rewrite-call-summaries

The summary Fathom writes after a call is built for you, and the client reads the same text. Changing its tone or adding a section means opening the call and regenerating it by hand.

Cotlet does it in your own Fathom account with list\_calls, get\_call and regenerate\_summary, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=fathom-video) [All Fathom tools](https://cotlet.dev/integrations/fathom-video-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Fathom do this on its own?

Fathom lets you customize a summary only in its web app (checked 22 Oct 2026). The API returns the default summary template of the account, and its FAQ says changing a call's template in the app does not change what the API returns. Webhooks send the same Markdown summary.

## How you do it in Fathom today

1. You open the call page, select a summary type from the list and click the gear icon next to it.
2. You add instructions, for example "Write in a formal tone suitable for client updates", then click Regenerate Summary.
3. To keep the instructions for later calls, you wait for the new summary and click Apply to Future Summaries; the pencil icon edits them and the arrow button reverts to the default.
4. Customization is a Premium and Team feature, and for bot-free users it works in the web app only, not the desktop app.
5. Deals have their own summary tab with four sales templates, so the same steps repeat for a deal.

## How to rewrite Fathom call summaries for the client

Prompt

```
For my external Fathom calls this week, rewrite each summary in a formal tone for the client, with a Next steps section at the end. Show me the text before anything is shared.
```

1. 01  
### Pick the calls  
The agent runs list\_calls for the week and keeps calls whose meeting\_type is External. Internal standups are skipped, because the client never reads them.
2. 02  
### Read the current summary  
get\_call returns the summary\_template and the text now on the page. A call whose summary\_status is generating is skipped and retried on the next run, so a half-written summary is not replaced.
3. 03  
### Regenerate with your rule  
regenerate\_summary runs with your instructions, such as a formal tone and a closing Next steps section. It replaces the summary people see on the call, so it waits for your OK, and you read the new text in the chat first.
4. 04  
### Decide what carries forward  
apply\_to\_future stays false unless you said to keep the rule. Set to true, it applies the instructions to that template for future summaries, so the agent sets it only once and says so.
5. 05  
### Stop at the draft  
The agent returns the new text per call and leaves sharing to you, so nothing is sent to the client without a decision.

### What you get back

Example data

```
External calls this week: 6
Rewritten 5, e.g. "Q4 pricing review": formal tone, Next steps added
Skipped 1 (summary still generating): "Vendor onboarding sync"
Instructions kept for future summaries: no
```

### Other ways to ask

- Add a Risks section to every summary of calls with the meeting type Sales Intro Call.
- Rewrite only the call I name in plain, short sentences for an internal wiki.
- Keep the rule "formal tone, Next steps at the end" for all future General summaries.

## What Fathom allows, and what to know first

- Summary customization is available to Premium and Team plan users.
- Each template has a base prompt, and your text adds to it rather than replacing it.
- The API returns your account default summary template, and one summary per recording.
- Deal summaries use four templates: Sales, Sales SPICED, Sales MEDDPICC and Sales BANT.

regenerate\_summary asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: [Fathom Help: Customizing AI Summaries](https://help.fathom.video/en/articles/3239809) · [Fathom API: FAQ](https://developers.fathom.ai/faq) · [Fathom Help: Meeting Types](https://help.fathom.video/en/articles/7905409)

## Call regenerate\_summary from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/fathom-video/calls/610313346/summary/regenerate \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"instructions":"Write in a formal tone suitable for client updates. End with a Next steps section.","apply_to_future":false}'
```

Example response

```
{
"call_id": "610313346",
"summary_template": "General",
"applied_to_future": false,
"summary": "## Summary\nThe client agreed to annual billing on the Team plan. Dana sends the revised quote by Friday."
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is fathom\_video\_write → regenerate\_summary. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/fathom-video-api-mcp-server.md#automations)

## Fathom tools this automation uses

__Cotlet Fathom tools used to rewrite Fathom call summaries for the client__
| Tool | Parameters |
| ------------------- | ------------------------------------------------------------- |
| list\_calls | scope, created\_after, created\_before, meeting\_type, cursor |
| get\_call | call\_id |
| regenerate\_summary | call\_id, template, instructions, apply\_to\_future |

[All 14 Fathom tools with descriptions](https://cotlet.dev/integrations/fathom-video-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Fathom to Cotlet?

Yes. You sign in to Fathom yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Fathom once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Fathom automations

- [Mark Fathom action items done and keep them current](https://cotlet.dev/integrations/fathom-video-api-mcp-server/update-action-items.md)
- [Restrict Fathom call share links to people you added](https://cotlet.dev/integrations/fathom-video-api-mcp-server/restrict-share-links.md)
- [Fathom API and MCP server: every tool](https://cotlet.dev/integrations/fathom-video-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Fathom.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Fathom.

[Sign up free](https://cotlet.dev/app/signup?app=fathom-video)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.