Every Wednesday, one essay on what's actually working in Marketing with AI - tools, workflows, and mindset shifts you can apply immediately.
3 Ways I Can Help You With Claude + Marketing
Whether you’re just getting started or ready to go deeper with Claude as your AI marketing tool, here’s how we can work together:
A. Follow along for free — Every Wednesday I break down what’s actually working in Marketing with AI. Subscribe to this newsletter and get practical frameworks, walkthroughs, and real examples straight to your inbox. No fluff.
B. Book a Claude Marketing Power Hour — 60 minutes, 1:1, focused entirely on your situation. Tell me where you’re stuck with Claude and marketing and we’ll work through it together - whether that’s setting up your first Project, building a Skill for your workflow, or figuring out which mode to use for what. One session, one clear next step. Book a session →
C. Embed Claude into your marketing team — For marketing leaders and teams who want to go beyond individual use and build Claude into how the whole function operates. From capability assessments and team training through to building custom Skills and workflows — this is where the real competitive advantage gets built. Let’s talk →
I’ve been using Zapier for years.
And for years, every Zap I’ve built has done the same thing: move data from one place to another.
Two simple examples:
1/ A new form submission triggers an email.
2/ A new CRM entry pings Slack.
Both reliable and predictable.
But completely unable to make a single decision on its own.
A lead comes in at 9pm. Zapier can send them a template email. But it can’t read their message, figure out what they actually need, and write something personalised.
A blog post goes live. Zapier can notify your team. It cannot draft three social versions tailored to different platforms.
A customer replies to a survey. Zapier can log the response. It cannot tell you whether they are happy, frustrated, or about to churn.
That middle step, the thinking step, has always been missing.
Zapier’s CEO Wade Foster put it well: “You probably don’t want an agent. You want a workflow that thinks.”
That is exactly what connecting Claude to Zapier gives you.
Not a smarter Zap. A workflow that can read, interpret, write, classify, score, and decide, then hand the result to whatever app needs it next.
Why This Connection Changes Things for Marketers
The reason most marketing automation feels underwhelming is not the tools.
It is the gap between trigger and action.
Today, you can set up a Zap that fires every time a new lead fills in a form. But as I have already said, the follow-up email is the same for everyone, because Zapier cannot write a personalised response.
You can set up a Zap that fires when a blog post is published. But the social content still needs a human, because Zapier cannot adapt your 1,500-word article into a 200-word LinkedIn post with the right tone.
When Claude sits inside that workflow, the gap closes. The automation stops being just a pipe that moves data and becomes a system that processes it.
Here’s how things change in practice when Claude sits inside your workflows:
• A new lead arrives → Claude reads their role, company, and message, scores their intent, writes a personalised follow-up, and routes them to the right sequence. Not after you wake up. Immediately. And because Claude is working inside a Cowork Project, it has access to your messaging playbook and ICP criteria. The follow-up is not generic AI copy. It follows your positioning, uses your language, and scores against the criteria you actually care about.
• A blog post is published → Claude drafts platform-specific versions for LinkedIn, Twitter, and email. But here is what makes this different from asking any AI to “summarise my article.” If you have built a brand voice Skill (which we covered earlier in this series), Claude reads your tone rules, your banned words, your formatting preferences. The LinkedIn post sounds like you wrote it, because Claude is working from the same style guide you would use yourself.
• A customer submits feedback → Claude categorises the sentiment, identifies the core issue, writes a one-line summary, and flags anything urgent in Slack. If the feedback mentions a specific product or feature, Claude can cross-reference against your product docs or FAQs inside the Project to give the summary real context, not just a vague “customer is unhappy.”
None of this requires you to be in the conversation.
It runs automatically, every time the trigger fires. But the quality of the output is shaped by the context you have already built: your Skills, your Projects, your reference files. That is the difference between automation that sounds like AI and automation that sounds like your team.
One Reddit user I read about built a full social media automation system using Claude, Google Sheets, Zapier, and Buffer for $0.15 per week. Another documented saving 20+ hours per week on content repurposing.
And if this doesn’t convince you of the power of combining Claude + Zapier, then I am not sure what will - but Zapier themselves deployed 800+ Claude-driven workflows internally, with task completion growing 10x year-on-year.
How Claude Connects to Zapier
There are actually three different methods to connect Claude to Zapier.
But for anyone already working in Claude Cowork, the method that matters is Zapier MCP.
MCP stands for Model Context Protocol if you don’t already know. In plain English, MCP is the connection that lets Claude connect and talk to other tools.
So with Zapier MCP, Claude communicates with Zapier from inside your Claude Cowork conversation.
You connect Zapier as a single connector, choose which apps and actions Claude can access, and then from inside your chat you give instructions in natural language. Claude figures out which tools to call, asks for your confirmation, and executes.
This video will show you how to connect Claude to Zapier in 3 simple steps:
That one Zapier MCP connects you to: 9,000+ apps. 30,000+ actions. And no Zap builder needed.
One other benefit: Zapier gives Claude access to more ‘functions’ per app than the native Cowork connectors. Google Calendar through the Claude Cowork connector gives you a handful of actions. Google Calendar through Zapier gives you significantly more. It is not just the breadth of apps. It is the depth within each one.
Five Marketing Workflows You Can Build This Week with Claude and Zapier
1. Personalised Lead Follow-Up on Autopilot
Connectors needed: Gmail (Send Email, Create Draft), Google Sheets or your CRM (Find Row)
The flow: New form submission → Claude reads the lead’s name, company, role, and message → scores their intent (0-100) based on job seniority and urgency language → writes a personalised 150-word follow-up → routes the email based on score.
Ask Claude: “A new lead just submitted a form. Here is their data: [Name], [Company], [Job Title], [Message]. Score their intent 0-100 based on seniority and urgency language. Write a warm, direct 150-word follow-up email that references their specific situation and invites a 20-minute discovery call. No jargon. If the score is above 70, send the email immediately via Gmail. If below 70, save it as a draft for my review.”
Why this matters: The difference between a five-minute response and a 24-hour response is not marginal. Research consistently shows that responding within the first hour increases conversion rates dramatically. This workflow means your best leads never wait, and you are not the bottleneck.
Taking it further: Add your CRM as a connector and have Claude update the lead record with the intent score and a two-line qualification summary. Over time, you build a scored database without ever manually entering data.
2. Blog Post to Multi-Channel Content Pipeline
Connectors needed: Google Docs (Find Document), Buffer or Hootsuite (Create Post), Mailchimp (Create Draft Campaign)
The flow: Blog post marked as published → Claude retrieves the full text → drafts platform-specific versions → schedules social posts → creates email digest draft.
Ask Claude: “Find the blog post titled [Title] in Google Docs. Draft three social versions: a LinkedIn post of 200 words in thought-leadership tone, a Twitter post of 280 characters maximum, and an Instagram caption in a casual tone with 5 relevant hashtags. Schedule them in Buffer across Tuesday, Wednesday, and Thursday. Then create an email intro paragraph in Mailchimp. Match my brand voice throughout.”
Why this matters: Most content teams know they should be repurposing. Most do not, because the manual work of adapting tone, length, and format for each platform takes longer than writing the original piece. This compresses that entire process into a single conversation.
The scheduling angle: Set this to trigger automatically every time a new post lands in your published folder. You write once. Claude handles distribution.
3. Post-Call CRM Update and Follow-Up
Connectors needed: Salesforce or HubSpot (Update Record, Create Task), Gmail (Create Draft)
The flow: Meeting transcript arrives (from Otter.ai, Fireflies, or any transcription tool) → Claude reads the full transcript → writes a structured call summary → updates the CRM record → creates follow-up tasks → drafts a follow-up email for your review.
Ask Claude: “I just finished a call with [Name] at [Company]. Here is the transcript. Write a 3-paragraph call summary covering: what was discussed, what was agreed, and what the next steps are. Update their Salesforce record with the summary. Create tasks for any agreed follow-up actions with due dates. Draft a follow-up email to [Name] confirming the next steps and save it as a Gmail draft for my review before sending.”
Why this matters: Manual data entry after every sales call is one of the most consistent time sinks in B2B marketing. And it is the kind of task that gets skipped when things are busy, which means your CRM slowly becomes unreliable. This makes the update automatic, so it happens every time regardless of how hectic the week is.
4. Customer Feedback Analysis and Routing
Connectors needed: Google Forms or Typeform (New Response), Google Sheets (Create Row), Slack (Send Message)
The flow: New survey response → Claude reads the full response → assigns sentiment (positive, neutral, negative) → categorises the issue → writes a one-line summary → routes based on severity.
Ask Claude: “Analyse this survey response. Assign a sentiment: positive, neutral, or negative. Identify the core issue and categorise it under one of: Product, Pricing, Support, Onboarding, or Other. Write a one-line summary. If the sentiment is negative and the category is Support or Product, post an alert to #urgent-feedback in Slack with the summary, the customer’s name, and their original response. Log everything to a Google Sheet with columns for date, name, sentiment, category, and summary.”
Taking it further: Set this to run on every new response. After a month, ask Claude to analyse the full spreadsheet and write a trends report: “Read the feedback log in Google Sheets. What are the top three issues by frequency? How has sentiment shifted over the past 4 weeks? Write a 200-word summary I can share with the product team.”
That second layer is where this compounds. Individual feedback is useful. Patterns across hundreds of responses are strategic.
5. Weekly Marketing Performance Briefing
Connectors needed: Google Sheets (Find Row), Google Docs (Create Document), Slack (Send Message)
The flow: Scheduled every Monday at 8am → Claude pulls the latest data from your reporting spreadsheet → identifies anomalies → writes a narrative summary → drops it into a Google Doc → posts a short version to Slack.
Ask Claude: “Pull this week’s data from the Marketing Dashboard spreadsheet in Google Sheets. Compare every metric against last week. Flag anything up or down more than 15% week-on-week. Write a 200-word narrative summary in the style of a weekly report, not bullet points. Highlight the single most important trend and one recommended action. Save it to the Weekly Reports folder in Google Drive and post a 3-line summary to #marketing-updates in Slack.”
The real power here is scheduling. Use /schedule to run this every Monday morning. By the time you sit down, the briefing is already in Slack. After a month, you can ask Claude to read all four weekly reports and identify the trend across the period. The briefing starts as a snapshot and becomes a strategic tool.
What It Costs to Connect Claude and Zapier
The honest picture: The free tier is fine for testing but not enough for real use. Each MCP tool call costs 2 Zapier tasks. So 100 tasks means 50 actions a month.
If you receive 50 leads and each triggers a follow-up, your entire allowance is gone before you have logged a single thing to your CRM. The Professional plan at $19.99/month is the realistic starting point. It also unlocks multi-step Zaps if you decide to go the traditional route later.
One important distinction: if you use the MCP route through Cowork, you do not need a separate Anthropic API key. Your Claude Pro subscription covers it. The API key is only needed for traditional Zaps where Zapier calls Claude as a step. If you are starting from Cowork, start with MCP. It is simpler and cheaper.
The Honest Caveats
1/ Claude has no memory between Zap runs. Every trigger starts fresh. Claude cannot know that the same lead emailed you last week, or that a customer escalated the same issue three times. To work around this, you pass the relevant history into the prompt as context, pulling it from your CRM or database. It works, but it requires planning.
2/ MCP connections can be temperamental. Some users report the connection dropping and needing re-establishment. It is improving, but worth knowing before you build mission-critical workflows around it.
3/ The desktop app is required for MCP. Claude on the web does not support Zapier MCP. You need the desktop app.
4/ Quality degrades without human checkpoints. Content pipelines that run fully automatically, with no review step, tend to produce generic output over time. The more brand-specific or strategically sensitive the task, the more important it is to keep a human review step. My recommendation: let Claude draft, but review before anything public-facing gets sent. The 10/80/10 principle applies perfectly here.
Some Closing Thoughts
Here is how I think about the split.
Cowork is where you do the strategic, iterative, judgment-heavy work. Writing a campaign brief. Developing a message framework. Analysing competitor positioning. Building the lead scoring criteria. Work that needs your judgment in the loop.
Zapier is where that work gets executed at scale. You develop the lead scoring framework inside a Cowork Project. Zapier applies it to every lead that ever comes in, at any hour, without you. You create the content repurposing template in Cowork. Zapier runs it every time a new blog post is published.
The strongest workflow is: Cowork to develop the strategy and templates. Zapier to execute them at scale.
Here is how the Claude ecosystem looks now if you’ve followed some of my recent ‘Claude for Marketing’ series:
I strongly believe the marketers who will get the most from this are the ones who stop treating these as separate features and start connecting them into a single system.
Want hands-on help with Claude?
I work with marketers 1:1 in Claude Marketing Power Hours and help teams embed Claude into their workflows from first steps to full-scale systems. Book a call using the link below.
Thanks for reading Marketing with AI! If you enjoyed this read, the best compliment I could receive would be if you shared it