Back/Sales/Zapier/Claude
IntermediateSales

Automate CRM Updates with Claude Projects and Zapier MCPs

Turn meeting notes into reliable CRM records by giving Claude a tightly scoped Zapier MCP toolset and project instructions that define lookup order, field meanings, and when to create or update a record.

Automate CRM Updates with Claude Projects and Zapier MCPs

Reid creates a restricted Zapier MCP tool collection, teaches a Claude Project the exact CRM lookup and write sequence, and processes meeting notes into Coda or HubSpot.

Before you start

What you need

  • A CRM or research database in Coda or HubSpot
  • A Zapier MCP server
  • A Claude Project
  • A meeting transcript from Granola or another source

What you’ll make

An updated CRM record with the correct contact, meeting, next steps, opportunity details, and source transcript.

Tools used

Step by step

The workflow

Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.

3 steps

Step01

Build a Custom Toolset with Zapier MCP

Create a dedicated Zapier MCP server for CRM logging. Add only the required Coda, HubSpot, calendar, internal lookup, and note actions, and restrict each tool to the records or documents this flow may touch.

Step02

Provide Instructions via a Claude Project

Create a Claude Project that specifies the lookup sequence, record identity rules, field definitions, allowed values, and the exact conditions for create versus update.

Example prompt
For every meeting transcript: 1. identify the attendee and meeting date; 2. search the authorized CRM by email; 3. search the meeting table for the same contact and date; 4. use the internal lookup only when required; 5. update the matching record or create one only when no match exists; 6. populate Next Steps, Opportunity Details, Product Feedback, Owner, and Source using the attached field definitions; 7. report every write and any unresolved ambiguity.
Step03

Execute the Workflow with Meeting Notes

After the meeting, select the CRM Logging project and attach the transcript plus any meeting identifier. Let Claude run the authorized lookup and write tools, then review its change summary against the source notes.

Example prompt
Process this meeting transcript using the CRM Logging project. Search before creating records, preserve the source link, update the correct contact and meeting, and report the exact fields changed. Ask before writing if identity or field mapping is ambiguous.

[transcript]

What good looks like

  • The agent searches before creating a new contact or meeting record.
  • Writes are restricted to the intended CRM documents and fields.
  • Custom field values follow documented definitions.
  • The final response lists exactly what was created or changed.

Build your next product with ChatPRD

Turn an idea into a PRD, user stories, and a plan.

Try ChatPRD free

After the steps

Runbook notes

How to recover when the loop fails and where human judgment helps.

Recover

If it goes sideways

The agent creates a duplicate contact or meeting
Search by stable identifiers such as email and meeting date first, then update the matching record or ask when several matches exist.
The model guesses how to populate custom fields
Document each field, allowed values, and examples in the Claude Project instructions.
The MCP exposes broader write access than the workflow needs
Create a dedicated server with only the required actions and restrict Coda documents, notebooks, or CRM objects.
A multi-step lookup exceeds the interactive tool window
Move slow research into a deterministic Zap and give Claude the finished result or job status before the CRM write.

Start shipping
better products.

Join 100,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.

Free to start
No credit card
SOC 2 certified
Enterprise ready