Paste a single URL into Claude and it can draft your Gmail replies, log deals in your CRM, and ping your Slack. No workflow builder. No code. Set up in about ten minutes.
Claude is smart, but out of the box it can't touch your inbox, your spreadsheets, or your CRM. The bridge that fixes that is called MCP, the Model Context Protocol. It's an open standard for how AI models talk to outside tools. Zapier runs an MCP server that exposes its entire catalog, roughly 8,000 apps and 30,000 actions, through one URL.
By the end of this playbook you'll have:
This is where your one link comes from.
Go to mcp.zapier.com and sign in with your Zapier account (create a free one if needed). Click New MCP Server. When it asks which client you're connecting, choose Claude. Give the server a name you'll recognize, something like claude-ops.
Zapier generates a unique server URL. That URL is a credential. Anyone who has it can fire your connected actions, so treat it like a password. Don't screenshot it, don't paste it in a group chat, and if it ever leaks, rotate it from the same dashboard.
An empty server does nothing. You have to explicitly grant tools. This is a feature, not a chore: Claude can only ever do what you've approved here.
Inside your new server, click Add tool (Zapier sometimes labels these "actions"). For the lead workflow in this playbook, add these three:
Each tool asks you to authenticate the underlying account the first time. That's normal OAuth, same as connecting any Zap. For fields, leave most of them set to "Have AI guess a value" so Claude can fill them from context, but hard-code anything that should never change, like the Slack channel name.
This is the sixty-second part from the video.
Open Claude in your browser at claude.ai. Then:
When the row shows as connected, that one link just handed Claude every action you granted in Step 2. Open a new chat, click the tools icon (the sliders) near the input box, and confirm your Zapier connector is toggled on with your three tools listed.
No workflow builder. No trigger diagrams. You just describe the outcome and Claude picks the tools itself.
Start a new chat and paste a real inbound lead (forwarded email text works fine), then a prompt like this:
# Prompt: the one-sentence ops run Here's a new lead that just emailed me: [paste the email] Do three things: 1. Draft a warm, short Gmail reply that answers their question and proposes a 15-minute call this week. 2. Add them to my Leads sheet with today's date and Status set to "New". 3. Post a one-line summary to the #leads Slack channel with their name and what they asked for.
Claude will ask permission the first time it calls each tool. Approve them, watch each one tick to done, then verify: the draft is sitting in Gmail, the row is in your sheet, the ping landed in Slack. In my runs the whole chain finishes in under a minute.
Nine times out of ten it's one of these. Check them in order:
Typing the same three-part prompt every time defeats the point. Save it once.
Create a Claude Project called "Lead Ops" and drop your workflow rules into the project instructions:
# Project instructions: Lead Ops
When I paste an inbound lead email, always:
- Draft a reply in Gmail. Never send, only draft.
- Log the lead in the "Leads" Google Sheet.
- Post a summary to #leads in Slack.
Tone for drafts: friendly, direct, two short paragraphs max.
Always confirm what you did in a bullet list at the end.
Now the entire workflow is: open the project, paste the email, hit enter. From here, expand sideways. Add a CRM tool for deal stages, a Calendar tool for booking the call, or a Notion tool for meeting notes. Same one link, more granted actions.
The apps were never the hard part. The bridge was. Now you have it.
Every playbook in the AI Automation Starter Stack is this practical: real steps, real prompts, things you can ship today.
Browse the free library