Skip to content

Deal record updates from calls and email with a source per field

Reads the calls, emails and notes on a deal and proposes updates to its CRM fields using your sales method. Every value names where it came from, and nothing is written until the rep approves.

SalesWorks with Claude Desktop with MCP · Claude CodeCommunity example

What it does

  • Pulls recent calls, emails and notes for the account
  • Maps what was said to your pipeline fields and sales method
  • Proposes field updates, each with the call or email it came from
  • Suggests a stage move only when exit criteria are met
  • Skips anything the rep declined on an earlier run

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Writing any field to the CRM
  • Replacing an existing value
  • Moving the deal to another stage

You decide what happens next.

More about this workflow

This setup is for founders and small sales teams who want more time for real conversations. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it pulls recent calls, emails and notes for the account. Next, it maps what was said to your pipeline fields and sales method. Then it proposes field updates, each with the call or email it came from. After that, it suggests a stage move only when exit criteria are met. Finally, it skips anything the rep declined on an earlier run. It works with your CRM, call recorder and email, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before writing any field to the CRM, replacing an existing value and moving the deal to another stage, and says plainly if a step cannot be undone.

“Nothing is written to the CRM until the rep approves it.”
dhand-personal dhand-personal on GitHub · Sep 29, 2026
Before you startCRM · Call recorder accessScoped permissionsClaude Desktop with MCP or Claude Code
Explore required tools and model recommendations

Tools and access

  • HubSpot CRM

    Handles the crm part of this job. Grant read scopes, plus notes write.

    API required: Yes. Needs a HubSpot private app or OAuth app with the CRM scopes you choose.

  • Call recorder

    Handles the call recorder part of this job. Grant read access to transcripts you choose.

    API required: Optional. Most meeting tools can export transcripts. An API is only needed to pull them automatically.

    No sign-up needed
  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Good balance of speed and quality for briefs and drafts.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost per token for simple research summaries.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

for example MEDDPICC or BANT

2Your prompt

3 of 3 still empty
Fill these in before you run it: [DEAL OR ACCOUNT NAME] [SALES METHOD: for example MEDDPICC or BANT] [PIPELINE STAGES AND EXIT CRITERIA] You are the Deal record updates from calls and email with a source per field agent. Reads the calls, emails and notes on a deal and proposes updates to its CRM fields using your sales method. Every value names where it came from, and nothing is written until the rep approves. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Pulls recent calls, emails and notes for the account - Maps what was said to your pipeline fields and sales method - Proposes field updates, each with the call or email it came from - Suggests a stage move only when exit criteria are met - Skips anything the rep declined on an earlier run What you must never do without a yes from a person: - Writing any field to the CRM - Replacing an existing value - Moving the deal to another stage Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Desktop with MCP, Claude Code

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect HubSpot CRM with its own login, not yours. Grant read scopes, plus notes write.
  2. 2Set up Call recorder. Keep it to read access to transcripts you choose.
  3. 3Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: writing any field to the crm, replacing an existing value, moving the deal to another stage.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 84.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Deal record updates from calls and email with a source per field](https://trustcase.dev/badge/deal-record-updates-from-calls-and-email-with-sources.svg)](https://trustcase.dev/use-cases/deal-record-updates-from-calls-and-email-with-sources)
HTML
<a href="https://trustcase.dev/use-cases/deal-record-updates-from-calls-and-email-with-sources"><img src="https://trustcase.dev/badge/deal-record-updates-from-calls-and-email-with-sources.svg" alt="Trustcase trust score for Deal record updates from calls and email with a source per field" height="20"></a>
  • Tomorrow's meetings with the real lead source

    The afternoon before, it checks every lead source for each of tomorrow's outside meetings and works out where the meeting really came from and who owns the account. You get one brief for the whole day.

  • Lead research brief

    Turns a new inbound lead into a one page brief before your first call.

  • Follow up drafter

    Writes the follow up email after a sales call so nothing goes cold.

  • Pipeline cleanup

    Finds stale deals and tells you which ones to close or chase.

Other workflows that use the same tools

  • Daily request intake and client progress page

    Operations. Each morning it reads the latest meeting transcript, recent client emails and a drop folder, files every document and turns every request into a task on one list. Before the next meeting it builds a short what's new page from the progress since the last one.

  • Review request texts after a sale

    Marketing. When a sale or service is marked done, it waits two days and texts the customer a link to leave a review, then one reminder. It checks opt outs first and tells the owner if a text fails.

  • Invoice inbox

    Operations. Reads bills that land in email and gets them ready to pay.