A Claude Code skill for building and editing Zapier Zaps by driving the web editor with browser automation — because Zapier has no public write API for authoring Zaps, and the editor fights automation in specific, learnable ways.
Written the hard way, while building a three-Zap prospecting system live. Every trap in here cost real time to find.
Don't have Zapier yet? Get started here →
Don't use the data picker. Type the mapping as a raw expression and it resolves into a proper token first time, every time:
{{=gives["<STEP_ID>"]["<outputFieldName>"]}}
The step id is in the editor URL while that step is open. The field name must be the machine name from that step's Data out panel, not the friendly label — guessing it produces a token that renders perfectly and evaluates to empty.
Split the work with Zapier's own Copilot. It is excellent at filling fields, finding required fields you cannot see, and scaffolding a brand-new Zap from a description. It cannot add Delay steps or some app steps mid-Zap. So you add the step shells, it fills the fields, and you type the awkward mappings by hand.
- Clicking things that resist:
find+ref, DOM event dispatch for virtualised rows, and why you must screenshot immediately before every click - The React Flow opacity-0 fix (the canvas renders empty in an automated window without it)
- Required fields hiding below the fold, and why a disabled Continue is almost never the field you're fighting
- Zapier's 30-second synchronous timeout, and the async → Delay → fetch-results shape that replaces it
- Aggregating many rows with Digest by Zapier instead of a multi-record lookup
- The AI-by-Zapier prompt being silently truncated at 50,000 characters on save
- Verification and safety: read the Data in panel, never test steps that send email, never publish without asking
git clone https://github.com/boringmarketer/zapier-browser.git
cp -r zapier-browser/skills/zapier-browser ~/.claude/skills/Then ask Claude Code to build or edit a Zap. The skill triggers on Zap authoring, step mapping and editor debugging.
Needs a browser-automation tool (Claude in Chrome or similar) and a logged-in Zapier account — start one here.
MIT. Built by @boringmarketer · boringmarketing.com