Skip to main content
Book a demo

Connect Zapier to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Zapier to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI 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 Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Zapier’s 17 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI 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 Cline CLI

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

Tools

17 Zapier tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination