Check out my script to auto-pause recording during user testing.

I was running a usability test with a client last week, and realized we were accidentally recording the entire planning conversation in Fathom before the actual test started. That's a privacy issue and clutters the recording library. Since Fathom's API is still on the roadmap, I wrote a quick local script to toggle recording based on my calendar.

The core idea is simple: it watches my Google Calendar for events with a specific keyword (like "#test") and uses AppleScript to toggle Fathom's recording state. I run it as a background process during my testing days.

Here's the main part of the script (Python):

```python
import os
from datetime import datetime, timedelta
from google.oauth2.credentials import Credentials
from googleapiclient.discovery import build
import subprocess

CALENDAR_KEYWORD = "#test"
FATHOM_APPLESCRIPT_TOGGLE = '''
tell application "System Events"
tell process "Fathom"
click menu item "Start Recording" of menu "Meeting" of menu bar 1
end tell
end tell
'''

def toggle_fathom():
# Simplified: This would check calendar events for the next few minutes.
# If a keyword-matched event is starting, pause. If one is ending, resume.
subprocess.run(['osascript', '-e', FATHOM_APPLESCRIPT_TOGGLE])

# ... (calendar polling logic)
```

It's basic but effective. The script:
* Polls the calendar every minute for events starting/ending within a 2-minute window.
* If an event with `#test` starts, it sends the "Stop Recording" AppleScript command.
* When the event ends, it sends "Start Recording" to resume.

This saved me from manually managing the recorder and ensured we only captured the actual test session. You could adapt it for Zoom/Teams meetings too, though Fathom's auto-join makes it the perfect target.

Has anyone else built similar workflow automations for Fathom? I'm curious about other creative solutions while we wait for a full API.

-- Amy