This template starts when Fathom reports a new meeting, fetches the recording file in JavaScript, and uploads it to Google Drive.
Put the Fathom API key on the Fathom connection, and put it in the JavaScript node that downloads the file. Connect Fathom and Google Drive, then pick the Drive folder that should hold the recordings.
Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.
Full pricing — how CPU seconds work →Workflow preview
The scenario starts when Fathom reports a new meeting on the account you connect.
JavaScript fetches the recording file from the Fathom API. Put the Fathom API key in that JavaScript node.
Google Drive saves the file in the folder you choose.
Add a Fathom connection and watch new meetings. Paste your Fathom API key on that connection.
Add a Google Drive connection with write access to the folder that will hold recordings.
Add JavaScript to fetch the recording from the Fathom API, with the Fathom API key in that node. Upload the file with Google Drive. Choose the destination folder and a filename such as the meeting title. Test with one meeting.
FAQ
More templates
This template runs on a schedule, opens each URL in a headless browser, and compares visible text to the last snapshot in Latenode Database. When the change crosses your threshold, JavaScript builds RSS XML and Google Drive saves the feed file. Connect Google Drive. Keep snapshots in Latenode Database keyed by URL.
This template receives Cognito Forms submissions on a Latenode webhook, maps the payload, then creates or updates the contact in ActiveCampaign and applies a tag. Paste the webhook URL into Cognito Forms. Connect ActiveCampaign and put the API URL and key on that connection. Map email so matches update the same person.
This template watches a Discord channel for new messages, translates the text with Google Cloud Translate, and posts the translation back to Discord. Connect a Discord bot and Google Cloud Translate. Put the Translate API key on the Google Cloud Translate connection. Point the trigger at the channel you want to translate and pick the target language.
