Connect Zapier to Goose
Give Goose governed access to Zapier’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Zapier to Goose in four steps
Admins approve the server once. Everyone in Goose 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 Goose to Runlayer
Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Zapier’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Goose 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 Goose
Zapier’s approved tools appear in Goose. Every call is checked against policy and recorded.
Tools
17 Zapier tools in Goose
Runlayer policy decides which of these Goose 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 Goose
Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.
Gateway policy (available)
Every Zapier call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call before Goose runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Goose’s model sees it.
Redact output in place (not available)
Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.
Frequently asked questions
Connect more