Skip to main content

How to save notes from Granola to folk?

Updated today

You can use this template: 👉🏼 https://zapier.com/shared/7ce85feb2046901af58228b11e249781b2b8f7a8

Overview of Tools

  • Granola – Records and provides call transcripts.

  • Folk – Your CRM where the notes will be stored.

  • Zapier – Automates the process between apps.

  • OpenAI – Transforms transcripts into a Markdown format acceptable by Folk.

  • OpenAI API Key – Required to connect Zapier to OpenAI.


Step-by-Step Setup

1. Trigger: Granola Call

  1. In Zapier, set Granola as the app.

  2. Select the trigger event (call data shared to Zapier).

  3. Connect your Granola account.

  4. Configure it at the workspace level so any team member’s calls can trigger the Zap.

  5. Output: You’ll get a transcript as a plain text field.


2. Transform Transcript to Markdown

  1. Add an OpenAI action in Zapier.

  2. Use a prompt to convert the note into a Markdown format.

    Convert the following plain text into clean, semantic Markdown using headings and lists. Remove all links and bare URLs. Return only the Markdown as a single line with literal \n characters for line breaks (no extra text, no code fences, no explanations, no actual newlines). ----------- Example input: ### Current Folk Implementation & Data Management - Julien cleaned up LP list after Affinity import issues - Many irrelevant contacts were imported initially - Some portfolio founders unexpectedly appeared in LP lists - No clear audit trail for how contacts get added (only shows “created by”) - Team finding Folk much more intuitive than Affinity - Less clicking required, can edit data directly - Browser extension significantly better than Affinity’s - WhatsApp integration working well for founder communications - Email notifications helping with follow-up reminders - Performance improvements noticed since last check-in - Fewer crashes reported by team members - Graham experiencing better stability ### Outreach Strategy & Process - Three main outreach triggers: - Geographic campaigns when traveling (NYC, London, etc.) - Material events (portfolio company funding rounds, new investments) - Regular newsletter via Mailchimp (though many LPs opt out) - Current list segmentation: Phase 1-2 (warmest pipeline), broader LP database - Primarily email-based outreach, some LinkedIn scraping via Chrome extension - Andrew handles most LinkedIn messaging on team - Slack integration highly desired - Team heavily dependent on Slack for daily operations - Sharing LinkedIn profiles, personal websites, contact info via Slack - Currently using Slack bot to extract URLs manually - Would benefit from automated data flow from Slack to Folk CRM ### Technical Integrations & Next Steps - Note-taking app integration needed - Currently using CircleBack but flexible on tool choice - Will coordinate with team on standardizing one enterprise plan - María will connect with Julián for API/Zapier setup - Upcoming Folk features of interest: - Sensitive contacts marking - Option to hide internal conversations - Native automations (beyond current Zapier/Make integrations) - All contacts/companies workspace view - Potential multichannel outreach via Lemlist for future consideration --- Chat with meeting transcript: [https://notes.granola.ai/d/911](https://notes.granola.ai/d/911) ----------- Example output: ### Current Folk Implementation & Data Management\n- Melissa cleaned up LP list after Affinity import issues\n- Many irrelevant contacts were imported initially\n- Some portfolio founders unexpectedly appeared in LP lists\n- No clear audit trail for how contacts get added (only shows “created by”)\n- Team finding Folk much more intuitive than Affinity\n - Less clicking required, can edit data directly\n - Browser extension significantly better than Affinity’s\n - WhatsApp integration working well for founder communications\n - Email notifications helping with follow-up reminders\n - Performance improvements noticed since last check-in\n - Fewer crashes reported by team members\n - Graham experiencing better stability\n### Outreach Strategy & Process\n- Three main outreach triggers:\n - Geographic campaigns when traveling (NYC, London, etc.)\n - Material events (portfolio company funding rounds, new investments)\n - Regular newsletter via Mailchimp (though many LPs opt out)\n- Current list segmentation: Phase 1–2 (warmest pipeline), broader LP database\n- Primarily email-based outreach, some LinkedIn scraping via Chrome extension\n- Andrew handles most LinkedIn messaging on team\n- Slack integration highly desired\n - Team heavily dependent on Slack for daily operations\n - Sharing LinkedIn profiles, personal websites, contact info via Slack\n - Currently using Slack bot to extract URLs manually\n - Would benefit from automated data flow from Slack to Folk CRM\n### Technical Integrations & Next Steps\n- Note-taking app integration needed\n - Currently using CircleBack but flexible on tool choice\n - Will coordinate with team on standardizing one enterprise plan\n- María will connect with Julián for API/Zapier setup\n- Upcoming Folk features of interest:\n - Sensitive contacts marking\n - Option to hide internal conversations\n - Native automations (beyond current Zapier/Make integrations)\n - All contacts/companies workspace view\n - Potential multichannel outreach via Lemlist for future consideration ------ Here is the text you need to convert:
  3. Output: A Markdown-formatted note ready for Folk.


3. Loop Through Attendees

  1. Add a Looping by Zapier step.

  2. Loop through the attendees’ email addresses (comma-separated list from Granola).

  3. Exclude the host from the list.

  4. This ensures each attendee gets the note in Folk.


4. Find Contacts in Folk

  1. Add a Find Person in Folk step.

  2. Search by attendee email.

  3. Filter so that the step only continues if contact exists.


5. Add the Note in Folk

  1. Use a Custom Request action in Zapier (Webhooks by Zapier).

  2. Method: POST

  3. Endpoint: Folk API endpoint for notes (see Folk API Docs).

  4. Data: JSON body containing the note text in Markdown.

  5. Headers:

    • Authorization: Bearer

    • Content-Type: application/json

    • Accept: application/json


6. Result

Once set up:

  • Every time a call is recorded in Granola, the transcript is transformed into a Markdown note.

  • That note is added to every attendee’s profile in Folk automatically.

Did this answer your question?