Skip to content
agentusehub
OperationsBeginnerB2B SaaS

Meeting notes that update the CRM for you

After each sales call, Zapier sends the transcript to Claude, which writes the notes and updates next steps and deal fields in Salesforce.

Time saved
5h / week
Setup time
40 minutes
Running cost
$40/mo
Cost range
$25–100/mo

The problem it solves

Reps finish a call, jump straight into the next one, and the CRM update waits until Friday or never happens. Managers forecast from stale deal stages and missing next steps. The notes that do get written are a line or two, so nobody else can pick up the account.

How it flows
  1. Call ends
  2. Transcript to Claude
  3. Notes + field updates
  4. Salesforce updated

Step-by-step setup

  1. Pick the transcript trigger

    In Zapier, start with your meeting tool's transcript-ready trigger, such as Zoom's new recording transcript trigger. Add a Filter step that continues only when at least one attendee email is outside your company domain.

  2. Find the deal in Salesforce

    Add a Salesforce Find Record step that looks up the Contact by the external attendee's email, then a second Find Record for the open Opportunity on that Account. Use Paths so calls with no open Opportunity log the note on the Contact only.

  3. Send the transcript to Claude

    Add the Anthropic (Claude) Send Message action with the prompt below. Map in the transcript plus the Opportunity's current Stage and Next Step so Claude can tell what changed.

  4. Parse the response

    Claude replies in JSON only. A Code by Zapier step runs JSON.parse and outputs summary, next_step, next_step_date, stage_suggestion and risks as separate fields.

  5. Update Salesforce

    Log a completed Task with the summary as its description, update the Opportunity's Next Step field, and create a follow-up Task due on next_step_date. Put stage_suggestion in the note instead of changing Stage directly.

  6. Check the first 20 calls

    Ask reps to skim the logged notes for two weeks and correct anything wrong. Most fixes become one-line additions to the prompt, such as how your team names products and plans.

Example prompts

Call notes and CRM fields
You are updating Salesforce after a sales call between {{rep_name}} and {{account_name}}.

Current opportunity stage: {{current_stage}}
Current next step: {{current_next_step}}

Read the transcript and return JSON only, with these keys:
- summary: 4 to 6 bullet points covering pain, budget, timeline, decision makers and objections
- next_step: the specific agreed next action, under 15 words
- next_step_date: ISO date if one was agreed, otherwise null
- stage_suggestion: a stage name if the call clearly moved the deal, otherwise null
- risks: up to three short phrases, such as "no budget owner identified"
- competitors_mentioned: an array of names

Only include what was actually said. Do not invent dates or names.

Transcript:
{{transcript}}
Sales · Intermediate
  1. Meeting in 60 min
  2. Perplexity research
  3. Claude writes brief

Build a pre-call brief for every discovery meeting

An hour before each discovery call, get a one-page brief on the account, the attendee and recent news, saved to Salesforce.

Make · Perplexity · Claude · Salesforce
Sales · Beginner
  1. Form submit
  2. Fetch company site
  3. Claude scores fit

Auto-qualify inbound leads before a rep sees them

Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.

n8n · Claude · HubSpot · Slack
Customer Support · Intermediate
  1. New ticket webhook
  2. Claude classifies
  3. Draft from help docs

Triage support tickets and draft first replies

Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.

Zendesk · n8n · Claude