Connect Zapier to Crush
Give Crush governed access to Zapier’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Zapier to Crush in four steps
Admins approve the server once. Everyone in Crush then gets it through the same governed connection.
- 1
Approve Zapier in Runlayer
Add Zapier from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Crush to Runlayer
Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches Zapier’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Crush setup guide - 3
Sign in to Zapier
Sign in the way Zapier requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Zapier from Crush
Zapier’s approved tools appear in Crush. Every call is checked against policy and recorded.
Tools
17 Zapier tools in Crush
Runlayer policy decides which of these Crush users can call.
Auto provision MCP
Automatically set up this MCP server based on the user's existing connected accounts.
Create Zapier skill
Saves a workflow as a reusable Zapier Skill — a good fit for multi-step workflows the user runs repeatedly or tool calls that always use the same parameters.
Delete Zapier skill
Permanently delete a Zapier Skill by name.
Disable Zapier action
Remove an app's actions from this MCP server.
Discover Zapier actions
Search 9,000+ apps to find actions you can enable.
Enable Zapier action
Enable an app's actions on this MCP server.
Execute Zapier read action
Execute a search or read action to get data from a connected app.
Execute Zapier write action
Execute a write or create action in a connected app.
Control
What Runlayer can see and stop in Crush
Some controls apply to every client at the gateway. Others depend on what Crush exposes to Runlayer.
Gateway policy (available)
Every Zapier call from Crush passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Crush as the client, the tool, and the policy and scanner decisions.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Crush yet, so control happens at the gateway.
Frequently asked questions
Connect more