'Sync Fathom meeting data to CRM and build automated follow-up workflows.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add jeremylongshore/tons-of-skills-marketplace --skill fathom-core-workflow-b --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fathom Core Workflow B?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeremylongshore-fathom-core-workflow-b-tons-of-skills-marketplace)More formats (shields.io, HTML) on the badges page.
---
name: fathom-core-workflow-b
description: 'Sync Fathom meeting data to CRM and build automated follow-up workflows.
Use when integrating Fathom with Salesforce, HubSpot, or custom CRMs,
or creating automated post-meeting email summaries.
Trigger with phrases like "fathom crm sync", "fathom salesforce",
"fathom follow-up", "fathom post-meeting workflow".
'
allowed-tools: Read, Write, Edit, Bash(python3:*), Grep
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- meeting-intelligence
- ai-notes
- fathom
compatibility: Designed for Claude Code
---
# Fathom Core Workflow: CRM Sync & Follow-Up
## Prerequisites
- Approved CRM mapping, consent/recording policy, scoped credentials, owner, and synthetic test meeting data.
## Output
- A reviewed Fathom-to-CRM follow-up workflow with explicit field mapping, consent/data controls, idempotency, and rollback/disable action.
## Error Handling
| Condition | Safe response |
|---|---|
| CRM record maps incorrectly | Pause sync, correct the field mapping, and validate with a synthetic record before replay. |
| Duplicate follow-up is detected | Deduplicate by stable meeting/action ID and do not resend automatically. |
| Consent/recording state is unclear | Do not sync or distribute content until the owner verifies it. |
## Examples
Use a synthetic meeting summary and test CRM contact to verify field mapping, follow-up creation, and deduplication in development. Record only opaque IDs and outcomes; do not use customer recordings, transcripts, or contacts as a tutorial fixture.
## Overview
Automate post-meeting workflows: sync meeting notes to CRM opportunities, send follow-up emails with action items, and maintain a meeting history database.
## Instructions
### Meeting-to-CRM Sync
```python
def sync_meeting_to_crm(meeting: dict, crm_client):
summary = meeting.get("summary", "")
action_items = meeting.get("action_items", [])
participants = meeting.get("participants", [])
# Find matching CRM contact/opportunity by participant email
for email in participants:
contact = crm_client.find_contact(email=email)
if contact:
crm_client.log_activity(
contact_id=contact["id"],
type="meeting",
subject=meeting["title"],
body=f"Summary: {summary}\n\nAction Items:\n" +
"\n".join(f"- {a['text']}" for a in action_items),
date=meeting["created_at"],
)
```
### Automated Follow-Up Email
```python
def generate_followup_email(meeting: dict) -> str:
actions = meeting.get("action_items", [])
action_list = "\n".join(f"- {a['text']}" for a in actions)
return f"""Hi team,
Thanks for the meeting: {meeting['title']}
Summary:
{meeting.get('summary', 'No summary available')}
Action Items:
{action_list if action_list else '- None recorded'}
Best regards"""
```
### Meeting History Database
```sql
CREATE TABLE fathom_meetings (
id VARCHAR PRIMARY KEY,
title VARCHAR NOT NULL,
created_at TIMESTAMP NOT NULL,
duration_seconds INTEGER,
summary TEXT,
participant_count INTEGER,
action_item_count INTEGER,
synced_to_crm BOOLEAN DEFAULT FALSE,
synced_at TIMESTAMP
);
```
## Resources
- [Fathom API Reference](https://developers.fathom.ai/api-reference)
- Fathom Integrations
## Next Steps
For error troubleshooting, see `fathom-common-errors`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!