Workflows & Automations

Connect a Meeting Notetaker to Your CRM and To-Dos

2:49 · August 25, 2026

A CRM nobody updates is a CRM nobody trusts, and the reason it goes stale is never laziness. It is that the update happens after the call, when the next call has already started. This walkthrough closes that gap end to end. Carly has native connectors for Fathom, Fireflies, Gong, Recall.ai and tl;dv under Integrations, so most notetakers are one click. If yours is not on that list, the video shows the other path: Granola gets added through Connect an API, and the same route works for anything with an API or an MCP server, so the directory is a starting point rather than a limit. Once the notes are reachable and Carly can see your calendar, the first thing to do is a backfill, asking Carly to go through yesterday's calls so you can read what it wrote before you commit to anything. What lands is people, companies and deals, not a blob of text pasted into a notes field. Then you turn the same instruction into a workflow that runs after every meeting from that point on. The demo uses Carly's built-in CRM because it is quickest to show, but the same process runs against HubSpot, Salesforce, Pipedrive, Attio, Close and the rest, so a CRM you already like stays where it is. One thing worth saying out loud in the prompt: the CRM update and your own action items are two different requests, so ask for both or you will only get half of it.

Step by step

1. 01

   Name the actual problem

   The pipeline is out of date because updating it happens after the call, when the next one has already started. Nothing about the record is hard to write, it just never gets written.

2. 02

   Connect your notetaker in one click

   Open Integrations, then Third-party integrations, then Meetings and transcription. Fathom, Fireflies, Gong, Recall.ai and tl;dv are already wired up and connect with a single approval.

3. 03

   Not listed? Add it as a custom API

   Granola is not in the native list, so the video uses Connect an API instead. Any tool with a public API or an MCP server goes in the same way, and you can ask Carly in chat to walk you through the steps for your specific one.

4. 04

   Make sure Carly can see your meetings

   The notes are only half of it. Carly needs the calendar too, so the notes it pulls can be matched to the right call, the right attendees and the right company.

5. 05

   Backfill yesterday's calls first

   Before automating anything, ask Carly to go through the meetings you already had and write them up. It is a one-off catch-up, and it lets you read real output on your own data instead of trusting a demo.

6. 06

   Check what actually got written

   Open the records and look. You should see people, companies and deals updated as structured fields, not a transcript dumped into a notes box. This is the step that tells you whether to trust the workflow.

7. 07

   Turn it into a workflow that runs after every meeting

   The backfill was manual. Saving it as a workflow is what makes it ongoing, so the CRM updates itself once the meeting ends and you never open it to type.

8. 08

   Ask for the to-dos explicitly

   Updating the CRM and capturing your own commitments are two separate instructions. Say that you also want action items and promises added to your tasks, or the workflow will only do the CRM half.

9. 09

   Keep the CRM you already have

   The demo runs on Carly's built-in CRM because it is the fastest thing to show, but HubSpot, Salesforce, Pipedrive, Attio, Close, Folk, Zoho and the rest connect the same way. Carly connects to thousands of apps, so the missing piece is usually one bridge, not a migration.