People ask about Zapier expecting it to mean everything on their Cantrip site is wired up to everything else: a new page goes live and it posts to Twitter, a domain connects and it emails their accountant, whatever chain they can dream up. That's not what's there. What's there is narrower, and once you see the actual shape of it, it's still genuinely useful. Just not magic.
Here's the whole catalog: one trigger, New Form Submission, and one action, Create Post. That's it, at least for now. Two doors, not a hundred of them.
The trigger side covers every contact form on your site, whether it's a section sitting on a page or one embedded in a post. Somebody fills it out, and Zapier can pick that submission up: drop it in a spreadsheet, ping a Slack channel, kick off a new contact in whatever CRM you're already paying for. The submission comes through with the field labels attached, not just raw values, so "Email Address" shows up as "Email Address" in your Zap, not some internal field code.
The honest catch: this is a polling trigger, not a live push. Zapier checks in on its own schedule rather than getting notified the second someone hits submit. On a free Zapier plan that's every fifteen minutes. Paid plans can tighten that up. Fine for routing leads into your inbox tool. Not something to build a "we'll call you back in five minutes" promise on top of.
The action side runs the other way: pushing a new post into Cantrip from somewhere else. You pick which collection it's allowed to write to, one at a time, in your website's Integrations settings, not site-wide. Check the box next to a collection and a little copy button shows up right beside it for grabbing the UUID Zapier wants. Leave a collection unchecked and Zapier can't touch it, no matter what key you hand out. Title and body are required. Slug, teaser, author name, and a featured image URL are optional. If that image URL fails to download, the post still gets created. It just quietly skips the image, so it's worth a glance at whatever gets published if you're feeding this from an automation you don't watch closely.
What isn't in there yet: no trigger for a new page going live, no trigger for a domain connecting, no action for editing an existing post, no action for touching page sections. If you want that kind of reach, that's what Cantrip's own MCP server and REST API are for. An AI assistant or a custom script connected there can do essentially anything you could do by hand in the dashboard. Zapier's slice is smaller on purpose.
Generating the key is a one-time thing worth doing carefully. It's shown in full exactly once, right after you click Generate. Copy it then. After that you only ever see the last four characters, with the rest replaced by dots, so if you lose it, regenerating is the only way back in, and every Zap using the old key stops working the moment you do.
That narrow scope is the right call, not a shortcoming. Most people connecting a website to Zapier don't want a general automation platform bolted onto their dashboard. They want new leads landing somewhere they already check, and a way to drop a post in without opening the editor. Cantrip's Zapier integration does exactly those two jobs and nothing else, which is honestly most of what anyone asks for.