Matt Canning, Founder and CEO of NoPlex, has a simple first question before using automation: "Is this worth the effort?"
That filter matters at NoPlex. The team is small, the product serves people with ADHD and neurodivergent workflows, and the company has used automation and AI since day one. If a workflow adds overhead, the team can feel it quickly. If a workflow saves attention, the team keeps it.
That is how Zapier MCP moved from experiment to operating rhythm.
The gap
NoPlex runs primarily on Google Workspace and Slack. The team wanted Claude to research topics, create reports, update files, move data into Sheets, and send Slack notifications.
Matt had already tested Anthropic's native Google MCPs. They worked on some tasks, but NoPlex needed deeper Google Workspace coverage to reflect how the team actually operates. As Matt put it, Zapier was "a more effective intervention for things like Claude because of the versatility offered."
Drive and Sheets were the clearest examples. NoPlex needed Claude to work inside Google Workspace, where the rest of the team already lives.
The workflows
One workflow starts with Claude searching the web for trending topics relevant to the NoPlex community. Claude gathers examples and citations, turns the research into a report, and delivers the output to the Head of Community and Growth.
The output lands outside the chat thread, in Google Drive as Docs and Sheets, where the team can read, edit, and reuse it.
Another workflow uses Zapier's Gmail capabilities to scan the NoPlex media inbox for relevant requests. That triage used to take about 4 hours of human review each week. Now it takes about 15 minutes.
NoPlex also built a custom analytics system for business trends: engagement, retention, digital ad spend, performance, and other operating signals. Data comes from source-of-truth APIs and data lakes, then moves into Google Sheets as the working database.
That Sheets layer is a deliberate choice. Non-technical teammates can add commentary next to the data. When a product change, ad campaign, or community push might explain a shift in behavior, the team can annotate the timeline directly. The result is an analytics view with both the number and the human context beside it.
One example: the analytics system alerted NoPlex that certain onboarding behaviors correlate with engagement during the critical first few days of exploration. Now the team can run experiments to optimize for those behaviors.
Slack is the notification layer. NoPlex uses the Zapier Slack integration as the central place for alerts across the business, so the team sees what changed and what needs attention.
What MCP changed
Claude can decide what matters in a trend search. Zapier MCP can create the Google Doc, update the Sheet, route the file, and notify the right Slack channel. Claude can reason over the analytics context. Zapier MCP can connect that reasoning to the Google Workspace and Slack actions that make the output usable.
That split also explains the usage pattern. Some early NoPlex experiments had a high-volume testing stretch. Once the workflows proved useful, NoPlex moved them into a steadier cadence. Some now run weekly.
For NoPlex, lower task volume meant the work had stabilized.
What it looks like now
AI sits inside the NoPlex operating rhythm: weekly trend reports, analytics views the whole team can annotate, and Slack notifications that keep work moving.
Zapier MCP gives Claude the reach to act where NoPlex already works.
Matt Canning is Founder and CEO of NoPlex, which builds tools for ADHD and neurodivergent workflows.
