Zapier MCP in 20 Minutes: Let Claude Update Your CRM Safely

In about 20 minutes (plus CRM OAuth), you will have:

• Claude connected to Zapier MCP (browser and/or Desktop — one Zapier connection covers Claude chat, Desktop, and Cowork)
• CRM actions enabled the safe way: find/search first, updates only with explicit confirmation
• A first working business outcome: Claude finds a contact/deal in HubSpot (or Salesforce / Pipedrive via Zapier) and — only after you approve — updates a field or adds a note
• A short harden pass: least-privilege actions, task budget awareness, and no silent writes

1. Zapier account — Free works to start; each successful MCP tool call uses two Zapier tasks (failed calls do not count — confirm on Zapier’s current usage docs).
2. Claude account — Zapier MCP is available on Claude plans including Free (Cowork needs a paid Claude plan if you use that surface).
3. Claude in the browser and/or Claude Desktop installed.
4. CRM already in Zapier or ready to OAuth — HubSpot, Salesforce, Pipedrive, Close, etc. via Zapier’s app catalog.
5. A non-production contact/deal you can safely edit (sandbox portal or a test record named MCP TEST).
6. If you are on Claude Team / Enterprise: an Owner or Primary Owner must enable Zapier under organization connector settings before members can connect. Enabling the org connector does not skip individual sign-in.

1. Open Claude (browser is fine).
2. Paste this prompt:

Connect to Zapier MCP for me. If I haven't already connected to Zapier, prompt me to install the connector. After the connector is installed, use the Zapier MCP list skills tool to find the onboarding skill then run it to set me up in a flash!

1. Claude shows a Zapier connector card → click Connect.
2. On Zapier’s authorization screen:

1. 1

   Authorize Zapier

   Click Copy prompt (Continue stays disabled until you do) → then Continue
   Review access → pick the right Zapier account if you have several → Allow

2. 2

   Force a sync

   If Zapier tools do not appear in Claude Desktop, fully quit and reopen the app once to force a sync.

1. Return to Claude. In Desktop, the browser may ask to Open Claude — allow it.
2. Paste the prompt you copied and let onboarding run.
3. Approve the first Zapier tool run for the session when asked (saves repeated prompts).

Paste (if onboarding did not already):

I just connected to Zapier. Use the list-skills tool to find the onboarding skill and follow it: tell me what Zapier MCP can do, then show me by putting a few of my apps to work together, live.

What good looks like:

• Claude lists enabled actions / apps
• If nothing is enabled, it helps you enable apps and batches sign-in links
• It may run a read-only digest (email/calendar/tasks) — that is expected

If your CRM is not yet connected to Zapier, complete OAuth when prompted. Prefer a dedicated integration user in the CRM when your plan allows (not the CEO’s personal login).

Ask Claude explicitly:

Discover Zapier actions for HubSpot (or Salesforce). Enable ONLY:
1) Find/search contact
2) Find/search deal or company
3) Create note / log activity
Do NOT enable delete, merge, or bulk update actions.

Replace HubSpot with your CRM name.

Rules for a safe starter pack:

Use a real record:

Find the HubSpot contact for MCP TEST (or email test+mcp@yourdomain.com).
Return: record id, email, lifecycle stage, owner. If multiple matches, list them and stop — do not guess.

Pass criteria:

• Ids and fields match what you see in the CRM UI
• No invented stages or owners
• Tool call visible / approved in Claude’s tool UI

1. Tell Claude the policy before the write:

Policy: never update CRM fields unless I type APPROVE in my next message.
Propose an update to MCP TEST: set a test property (or add a note) "Verified via Zapier MCP on <today's date>".
Show the exact record id and fields you will change, then wait.

1. Verify the proposal against the CRM UI.
2. Reply APPROVE only if correct — or DENY with corrections.
3. After the tool runs, refresh the CRM record and confirm the note/field.

• Least privilege: only the actions your team truly needs; no delete/merge.
• Test records first: name them MCP TEST so mistakes are obvious.
• Human confirmation language in your custom Claude project instructions: “CRM writes require the user to reply APPROVE.”
• Task budget: MCP calls consume Zapier tasks (two per successful call per current Zapier docs). Watch usage before rolling out to the whole sales floor.
• Secrets: OAuth tokens live in Zapier — do not paste CRM API keys into Claude chat.
• Org rollout: Owners can roll Zapier MCP out org-wide; still require each user to authenticate. See Zapier’s “Roll out Zapier MCP to your Claude organization” guide.
• Audit: for regulated teams, log who connected and which write actions are enabled; review monthly.
• Desktop vs browser: one Zapier connection covers both; if tools go missing after a Claude update, reconnect once rather than creating duplicate servers.

• [ ] Zapier connector shows connected in Claude
• [ ] Onboarding skill completed once
• [ ] CRM OAuth succeeds; find/search returns real ids
• [ ] Write actions limited; delete/merge not enabled
• [ ] One APPROVE’d note or test-field update verified in CRM UI
• [ ] DENY path practiced (Claude does not write)
• [ ] Zapier task usage checked; team knows the budget
• [ ] Project instructions include the APPROVE policy
• [ ] Owner documented for who may enable new write actions

• Starting at mcp.zapier.com for Claude — wrong path for the connector flow; connect inside Claude so Zapier can auto-provision.
• Enabling every CRM action “just in case” — models will find the sharp tools. Allow-list reads; add writes deliberately.
• No APPROVE policy — conversational assent (“sure”) is too weak; require an explicit token.
• Using production deals for the first write — always burn in on MCP TEST.
• Ignoring Team Owner gates — members cannot fix a disabled org connector themselves.
• Burning the task quota in demos — successful calls cost tasks; rehearse reads, minimize speculative writes.
• Sharing connection tokens — if you later use token-based MCP clients, never paste those URLs into Slack; they are long-lived credentials.

For governed CRM/ERP design beyond DIY, see Solutions, Architecture, or contact Octacer.