Skip to main content

Connect ZoomInfo to GitHub Copilot CLI

Give GitHub Copilot CLI governed access to ZoomInfo’s 24 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add ZoomInfo to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.

  1. 1

    Approve ZoomInfo in Runlayer

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

  2. 2

    Connect GitHub Copilot CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches ZoomInfo’s 24 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 3

    Sign in to ZoomInfo

    Sign in the way ZoomInfo requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use ZoomInfo from GitHub Copilot CLI

    ZoomInfo’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.

Tools

24 ZoomInfo tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI users can call.

  • Account research

    Research a company/account/organization using ZoomInfo market data with your CRM and conversation history.

  • Audience analysis

    Compute answers about the contents of a GTM Studio audience.

  • Browse audiences

    Browse GTM Studio audiences with basic metadata.

  • Browse engagements

    Retrieve engagements (meetings and emails).

  • Contact research

    Research a specific person/contact using ZoomInfo market data with your CRM and conversation history.

  • Conversation intelligence

    Answers natural-language questions about calls, meetings, and emails, scoped to a single engagement, an account, or a contact.

  • Enrich companies

    Enrich company data with comprehensive business intelligence from ZoomInfo's database.

  • Enrich company signals

    Fetch multiple signal types for specific companies in a single request, enriching company details with Intent, News, and Scoops data.

See all 24 ZoomInfo tools

Control

What Runlayer can see and stop in GitHub Copilot CLI

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

  • Gateway policy (available)

    Every ZoomInfo call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot 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 or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination