Lead Generation · n8n

Meeting Notes to CRM: voice-note your call debrief, find it structured in the pipeline sheet

An n8n workflow where you send a voice note to Telegram right after a sales call — transcribed automatically, then Claude extracts the deal stage, budget signals, objections, and agreed next step, updates the prospect's row in your CRM sheet, and schedules the follow-up reminder.

difficulty Intermediatesetup 40 minresult CRM hygiene without the CRM data entry — debriefs captured while walking to the car
  1. 1

    Voice note in

    A Telegram Trigger on voice messages, then a Telegram node downloads the audio file. The habit that makes this work: debrief in the first three minutes after the call, while the details are still warm.

  2. 2

    Transcribe

    An HTTP Request posts the audio to your transcription endpoint and returns plain text. Accuracy on a quiet voice note is excellent; even a car-noise debrief comes through usable because Claude reads for meaning, not word-perfection.

  3. 3

    Extract and match

    Claude receives the transcript plus the current prospect list (names + companies from the sheet): identify the prospect, extract the deal fields as JSON, flag match_confidence. High confidence proceeds; low confidence triggers the clarifying Telegram question instead of a guess.

  4. 4

    Update the row, set the reminder

    A Google Sheets update writes the fields to the prospect's row (appending to notes history, never overwriting). The agreed next step's date feeds a Schedule-checked reminders tab, and the morning of, you get: 📞 Follow up with Jane @ Acme — promised the case study. Pipeline reviews stop starting with 'wait, where did that deal end up?'

Frequently asked questions

How does the transcription work?

The Telegram voice file goes to a speech-to-text API — the workflow ships wired for OpenAI-compatible Whisper endpoints (including self-hosted) since that's the most common setup, with a note for swapping in any transcription service. A 2-minute debrief costs about a cent to transcribe.

How does it know which prospect I'm talking about?

Say the name in the note — 'call with Acme, spoke to Jane…' — and Claude matches it against your prospects sheet with fuzzy matching. Ambiguous or unknown names don't guess: the workflow replies asking 'Acme Corp or Acme GmbH?' and a new name offers to create a row. Wrong-row updates are the failure mode this design refuses.

What exactly gets extracted into the sheet?

Stage (discovery/proposal/negotiation/closed), sentiment, budget signals if mentioned, objections raised, promises you made, agreed next step with date, and the raw transcript link. The next-step date also creates the reminder — the follow-up you promised at 4:55 on Friday no longer depends on Friday-you remembering.

Related recipes

Follow-Up Sequencer: polite persistence on autopilot — day 3 and day 7 nudges from a Google Sheet

An n8n workflow that reads your outreach sheet daily, finds contacts you emailed 3 or 7 days ago with no reply, has Claude write a short varied follow-up (never the same canned bump twice), and sends it from your Gmail — replies are auto-detected and pulled out of the sequence.

Intermediate · 40 min setup

Contact-Form Lead Enricher: every form submission arrives pre-researched in Slack

An n8n workflow that catches your website's contact-form submissions via webhook, has Claude research the sender's company from their email domain and website, scores the lead, and posts a briefing card to Slack — so you walk into every reply already knowing who they are.

Beginner · 30 min setup

Job-Post Lead Finder: companies hiring for a role are companies with that problem — catch them weekly

An n8n workflow that scrapes fresh job listings for roles that signal a need for your service (hiring a 'social media manager' = needs content help), has Claude extract the company, size hints, and pain signals, and delivers a scored lead list to Google Sheets every Monday.

Intermediate · 45 min setup
About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.