Skip to main content
Book a demo

Connect Zapier to VS Code

Give VS Code governed access to Zapier’s 17 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Zapier to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Zapier in Runlayer

    Add Zapier from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Zapier’s 17 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 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. 4

    Use Zapier from VS Code

    Zapier’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

17 Zapier tools in VS Code

Runlayer policy decides which of these VS Code 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.

See all 17 Zapier tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Zapier call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination