{"slug": "the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap", "title": "The jiu-jitsu coach who told Claude what he wanted and never opened the Zap", "summary": "Jiu-jitsu gym owner Jesse Walker used Claude connected through Zapier MCP to build and then repair a Zap that routes new leads from a Google Sheet into GymDesk, his CRM, without opening the Zap himself. The first version was built in under 10 minutes, mostly spent granting permissions, and Claude fixed a duplicate-lead bug in about five more minutes after Walker reported the same lead arriving repeatedly. Walker, who runs Rough Hands BJJ in Louisville, Kentucky, with about 200 students, said the connection from Claude to Zapier was \"trivially easy\" and that Claude sent him proof of the fix rather than requiring him to inspect the automation.", "body_md": "Jesse Walker spent years as a tech product manager. About 10 years ago he left the industry to turn his evening gig, coaching jiu-jitsu, into a full-time one. He now owns and coaches at [Rough Hands BJJ](https://roughhandsbjj.com) in Louisville, Kentucky.\n\nRough Hands BJJ has been open for 10 years and teaches Brazilian jiu-jitsu to about 200 students in the Louisville area.\n\nThe product brain came with him. \"I have lots of techie stuff kind of infused in my business,\" he says. He even worked with Claude to build an Apple TV app that runs a round timer and a clock on the gym floor.\n\nWhat he doesn't have is desk time. \"So much of my time is out teaching or answering emails or cleaning toilets,\" Jesse says. Ideas for fixing his processes tend to arrive as what he calls \"shower thoughts,\" not as time at a desk.\n\n## One business, two places for leads\n\nJesse has used Zapier for the jobs that sit between his apps for about seven years, by his own estimate. The longest-running one starts at the front desk. New students fill out a waiver on a [Google Form](https://zapier.com/apps/google-forms/integrations). The answers land in a [Google Sheet](https://zapier.com/apps/google-sheets/integrations), and a Zap copies each person into [GymDesk](https://zapier.com/apps/gymdesk/integrations), the CRM where he manages members and leads. That Zap has been \"running in the background for years and years.\"\n\nThen Jesse brought on [Martial Consulting](https://martialconsulting.com/), a marketing agency for martial arts schools, to run his ads and bookings. Its new leads landed in a separate Google Sheet that lived outside GymDesk. Jesse didn't want to run two systems side by side. He wanted every new lead in GymDesk, where he already manages them.\n\n\"I bet Zapier can help me integrate some of this stuff and get it funneled back into GymDesk for me,\" he remembers thinking. Then he logged in and saw that he could connect Claude. \"I'm like, oh, I bet I could have Claude do it.\"\n\n## Letting Claude out of the box\n\nUp to that point, Claude had been a writing partner, his \"don't-sound-like-a-jerk filter,\" as he puts it, and an occasional coding buddy. It never touched his other tools. \"It's usually just me and it, and I keep it in a box,\" Jesse says.\n\nConnecting Claude to [Zapier MCP](https://zapier.com/mcp) took a couple of quick back-and-forths. Most of those were reconnecting his Google apps to Zapier. The connection from Claude to Zapier itself was \"trivially easy,\" he says.\n\nThen he described the job in plain language. \"Hey, here's what I'm trying to do. Is this a thing? Can we do this?\" Claude, working through Zapier, built a Zap that watches the new Google Sheet and adds each new lead to GymDesk. The first version was done in under 10 minutes, and most of that was granting Claude permissions. \"The time investment was negligible,\" Jesse says.\n\nHe didn't go to Zapier to inspect it. \"Once I got Claude connected, I pretty much let it do it,\" Jesse says. \"As opposed to going and inspecting the Zaps afterwards, it would start giving me sample outputs or send me emails. So I really didn't have to fool with anything.\"\n\n## The fix he never had to open\n\nThe first version had a flaw. New rows didn't always land at the bottom of the sheet, and the Zap kept picking up the bottom row. The same lead came through again and again.\n\nSo Jesse told Claude. \"I was like, hey, you keep sending me the same thing over and over again. Can you actually fix it?\" He asked for the Zap to follow whichever row had actually changed. Claude explained what had gone wrong, named the two leads that should have come through and updated the Zap. The fix took about five more minutes. \"And it did it and it sent me the proof that it did it,\" Jesse says. \"So I didn't actually have to go back and fiddle with anything in the Zaps.\"\n\nThat proof is what earned his trust. Claude didn't just say the Zap was fixed. \"It would demonstrate to me that it understood the problem and could put the fix in,\" he says.\n\nHe still checks in, the way any owner would. \"I'm still kind of keeping eyeballs on it just to make sure that I haven't forgotten to give it any details,\" he says. A small school's lead volume makes problems easy to spot.\n\n## A different kind of Zap under the hood\n\nJesse assumed Claude was clicking through the same Zap editor he'd always used. \"My mental model was that Claude was basically going to be going through the same process I would go through to build that Zap,\" he says.\n\nIt wasn't. What Claude built is a [Next-Gen Zap](https://help.zapier.com/hc/en-us/articles/48391476448141-Get-started-with-Next-Gen-Zaps). Next-Gen Zaps are a new kind of Zap, written in TypeScript under the hood, so AI tools can build and edit them faster and more accurately. Next-Gen Zaps also come with agentic management, which watches for errors and can draft or publish a fix. It's on by default, and so far it hasn't had anything to fix.\n\nFor Jesse, the difference showed up as speed. \"It's so much easier to quickly ask if a thing were possible rather than me having to map through all the little fields and this and that and try to figure it out myself,\" he says.\n\n## Where the shower thoughts go now\n\nGymDesk handles the messages inside his business, like texting new leads the day before their appointments. Anything that has to cross between apps goes to Zapier. \"Anytime I'm talking between different apps, you all are my go-to,\" Jesse says.\n\nThe lead Zap was the first one he built this way. He already has the next ones in mind. Every spring, Rough Hands BJJ hosts the [BJJ Mental Models Spring Camp](https://roughhandsbjj.com/spring-camp), tied to the podcast of the same name. Jesse wants a Zap that compares camper emails in GymDesk against his waiver sheet and sends the waiver form to anyone who hasn't signed it. After that, he wants to pull the camp roster out of GymDesk and see who's coming: how many black belts, what the average age is. If any of his older Zaps ever need structural changes, he plans to hand those to Claude, too.\n\nWhen the next shower thought hits, he knows where he's starting. \"I would certainly try it first and see how far I could get with it.\"\n\n*Jesse Walker owns and coaches at* *Rough Hands BJJ**, a Brazilian jiu-jitsu school in Louisville, Kentucky.*\n\nLearn more about [Next-Gen Zaps](https://help.zapier.com/hc/en-us/articles/48391476448141-Get-started-with-Next-Gen-Zaps).", "url": "https://wpnews.pro/news/the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap", "canonical_source": "https://zapier.com/blog/rough-hands-bjj-next-gen-zaps", "published_at": "2026-11-19 18:43:30.097293+00:00", "updated_at": "2026-11-19 18:43:32.878545+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "agent-protocols"], "entities": ["Jesse Walker", "Rough Hands BJJ", "Claude", "Zapier", "Zapier MCP", "GymDesk", "Google Sheets", "Martial Consulting"], "also_reported_by": [], "takeaway": "Connecting Claude to Zapier MCP let a non-desk-bound owner build a Google Sheets-to-GymDesk lead-routing Zap in under 10 minutes and fix a duplicate-row bug in about 5 more by describing the problem in plain language and relying on Claude's sample outputs as verification.", "recommendation": {"advice": "Describe the integration goal in plain language and let the agent build the Zap, then verify through its sample outputs and emails instead of manually inspecting each step.", "playbook": "agent-architecture", "playbook_url": "https://wpnews.pro/playbooks/agent-architecture"}, "alternates": {"html": "https://wpnews.pro/news/the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap", "markdown": "https://wpnews.pro/news/the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap.md", "text": "https://wpnews.pro/news/the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap.txt", "jsonld": "https://wpnews.pro/news/the-jiu-jitsu-coach-who-told-claude-what-he-wanted-and-never-opened-the-zap.jsonld"}}