How this PM uses MCPs to automate his meeting prep, CRM updates, and customer feedback synthesis

How this PM uses MCPs to automate his meeting prep, CRM updates, and customer feedback synthesis

How I AIFeb 2, 202640m

Claire Vo (host), Reid Robinson (guest)

MCPs reframed as AI app connectorsZapier MCP custom tool collectionsClaude Projects for tool-order instructionsMeeting prep with CRM + internal searchPost-meeting notes to Coda/HubSpotDeterministic workflows vs agentic tool useCustomer feedback → FAQ/KB virtuous cycleGemini for file/PDF/HTML processingPersonal automations: family calendar, NotebookLM interview prep

In this episode of How I AI, featuring Claire Vo and Reid Robinson, How this PM uses MCPs to automate his meeting prep, CRM updates, and customer feedback synthesis explores zapier PM shows MCP connectors for faster, smarter customer workflows This episode demystifies MCPs by reframing them as “app integrations for your AI tools,” enabling an AI client to both read knowledge from your apps and take actions inside them.

Zapier PM shows MCP connectors for faster, smarter customer workflows

This episode demystifies MCPs by reframing them as “app integrations for your AI tools,” enabling an AI client to both read knowledge from your apps and take actions inside them.

Reid demonstrates Zapier’s MCP approach: build custom tool collections from 8,000+ apps/30,000+ actions, then connect a single server URL to tools like Claude, ChatGPT, or Cursor.

He shares practical workflows: daily meeting research, post-meeting note logging into Coda/HubSpot, and deterministic automations for longer-running data lookups (e.g., Databricks → Gemini → Coda).

The conversation emphasizes a “virtuous cycle” where support and chatbot transcripts are synthesized into new FAQ entries, keeping internal and external knowledge bases continuously up to date.

Key Takeaways

Think of MCPs as “connectors,” not a new abstract framework.

Reid suggests ignoring the term and focusing on outcomes: give your AI access to knowledge in your apps and the ability to take actions in those apps—those are the two core jobs MCPs enable.

Get the full analysis with uListen AI

Custom tool bundles reduce chaos and improve reliability.

Rather than adding many separate MCPs with overlapping capabilities, Zapier lets you build purpose-specific “collections of tools” (per client or per use case) and restrict them (e. ...

Get the full analysis with uListen AI

Claude Projects can act as a tool-usage playbook, not just a knowledge vault.

Reid encodes step-by-step instructions for which tools to call, in what sequence, and where fields should map—making multi-tool execution noticeably more accurate and repeatable.

Get the full analysis with uListen AI

Use agentic MCP interactions for “in-the-moment” work; use deterministic workflows for long-running steps.

MCP tool calls inside chat clients are time-bounded and can struggle with multi-minute research. ...

Get the full analysis with uListen AI

Automate meeting prep to eliminate ‘showing up cold’ to customer calls.

His workflow looks up the attendee/company, product usage, prior interactions, and internal context (e. ...

Get the full analysis with uListen AI

Post-meeting notes become maintainable when the AI can ‘create-if-missing’ and map custom CRM fields.

Instead of building brittle if/else chains manually, he teaches the model how his org’s unique CRM fields work, then lets it check for existing records, create new entries, and log activities/next steps automatically.

Get the full analysis with uListen AI

Turn support and chatbot transcripts into continuously improving knowledge bases.

A Zap reviews closed tickets/transcripts, extracts the core FAQ + solution, checks whether it’s already covered, proposes a new entry if not, and routes it through a human approval step—keeping the chatbot’s source KB fresh without quarterly cleanups.

Get the full analysis with uListen AI

Notable Quotes

Definitely don’t think about the word. It really just is like app integrations for your AI tools.

Reid Robinson

The two things we see people wanting to do is… giving their favorite AI tool the access to knowledge that lives in their apps, as well as giving them the ability to actually do things in those apps.

Reid Robinson

Check out Claude Projects… [you can] provide very detailed instructions… how it should use tools, in which order it should use tools, what data should go where.

Reid Robinson

If you could run ChatGPT in your sleep, what would you do?

Reid Robinson

Let’s say you had the perfect team with infinite time… your perfect support team… would look at every support question and go see, do we have the right help desk content here?

Claire Vo

Questions Answered in This Episode

When you build a Zapier MCP “tool collection,” what criteria do you use to decide which tools to include vs exclude for a given Claude Project (and how do you prevent tool overlap/ambiguity)?

This episode demystifies MCPs by reframing them as “app integrations for your AI tools,” enabling an AI client to both read knowledge from your apps and take actions inside them.

Get the full analysis with uListen AI

Can you share an example of the exact ‘tool calling order’ instructions you put into a Claude Project for CRM updates—what steps matter most to reduce wrong-tool calls?

Reid demonstrates Zapier’s MCP approach: build custom tool collections from 8,000+ apps/30,000+ actions, then connect a single server URL to tools like Claude, ChatGPT, or Cursor.

Get the full analysis with uListen AI

Where do agentic MCP flows fail most often for CRM logging (missing identifiers, custom fields, duplicate contacts), and what guardrails have been most effective?

He shares practical workflows: daily meeting research, post-meeting note logging into Coda/HubSpot, and deterministic automations for longer-running data lookups (e. ...

Get the full analysis with uListen AI

You mentioned MCP interactions can’t take too long—what’s your practical time limit before you switch a workflow to deterministic/asynchronous automation?

The conversation emphasizes a “virtuous cycle” where support and chatbot transcripts are synthesized into new FAQ entries, keeping internal and external knowledge bases continuously up to date.

Get the full analysis with uListen AI

In your customer interview prep workflow, what fields from Databricks ended up being most predictive/useful in real conversations (usage frequency, plan, integration count, past tickets, partner status)?

Get the full analysis with uListen AI

Transcript Preview

Claire Vo

MCPs, I will say, it's a concept that's really hard to understand for folks.

Reid Robinson

Yeah, definitely don't think about the word. It really just is like app integrations for your AI tools. You can create these collections of tools from all the apps you use and give them access to Claude, to ChatGPT, to Cursor, all the places that have inputs for MCP servers today.

Claire Vo

I use agents all the time, but it is hard to break that muscle memory of this is a deterministic workflow versus an instructive agent, even if it has access to the same tools and can do the same things.

Reid Robinson

And when it comes down to it, the two things we see people wanting to do is, one, giving their favorite AI tool the access to knowledge that lives in their apps, as well as giving them the ability to actually do things in those apps. Those are the two things that if that sounds like something that you need in an AI app you use, look for MCP or connectors, as it's often being called now as well, for that. [upbeat music]

Claire Vo

Welcome back to How I AI. I'm Claire Vo, product leader and AI obsessive, here on a mission to help you build better with these new tools. Today, I'm talking to Reid Robinson, product manager on AI at Zapier, and what I love about my conversation with Reid is he's gonna show us how to put MCPs to work inside Claude to take over tasks that you really hate. We also talk about whether AI can be the perfect always-on team that works while you sleep, and some use cases to make your kids and your partner a little happier. Let's get to it. This episode is brought to you by WorkOS. AI has already changed how we work. Tools are helping teams write better code, analyze customer data, and even handle support tickets automatically. But there's a catch: these tools only work well when they have deep access to company systems. Your copilot needs to see your entire code base. Your chatbot needs to search across internal docs. And for enterprise buyers, that raises serious security concerns. That's why these apps face intense IT scrutiny from day one. To pass, they need secure authentication, access controls, audit logs, the whole suite of enterprise features. Building all that from scratch, it's a massive lift. That's where WorkOS comes in. WorkOS gives you drop-in APIs for enterprise features, so your app can become enterprise-ready and scale upmarket faster. Think of it like Stripe for enterprise features. OpenAI, Perplexity, and Cursor are already using WorkOS to move faster and meet enterprise demands. Join them and hundreds of other industry leaders at workos.com. Start building today. Hey, Reid, thanks for joining How I AI.

Reid Robinson

Thanks for having me here, Claire. Excited to chat today.

Claire Vo

What I love about how you've described your role at Zapier, which I use all the time, I say, is like load-bearing infrastructure over at ChatPRD [chuckles] is you've, you've worked your way into a role where you get to kind of like pick what you're working on next in, in AI. And so I'd love to hear about what you're focused on and how that's actually impacted how you think some of- about some of your personal workflows.

Install uListen to search the full transcript and get AI-powered insights

Get Full Transcript

Get more from every podcast

AI summaries, searchable transcripts, and fact-checking. Free forever.

Add to Chrome