Skip to main content
Book a demo

Connect Zoom to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Zoom to GitHub Copilot in four steps

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

  1. 1

    Approve Zoom in Runlayer

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

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Zoom’s 20 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Zoom

    Each user signs in to Zoom with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Zoom from GitHub Copilot

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

Tools

20 Zoom tools in GitHub Copilot

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

  • Ask

    READ-ONLY

  • Canvas add file collaborators

    Adds collaborators (Zoom users, Team Chat channels, or email addresses) to a Zoom Canvas (formerly Zoom Docs) file, granting them a specified access role.

  • Canvas list file collaborators

    Retrieves the list of collaborators for a specified Zoom Canvas (formerly Zoom Docs) file (supports doc and data table file types only).

  • Canvas modify file collaborator role

    Modifies the role of an existing collaborator on a Zoom Canvas (formerly Zoom Docs) file.

  • Canvas remove file collaborator

    Removes a specified collaborator from a file in Zoom Canvas (formerly Zoom Docs).

  • Create new file with markdown

    ⚠️ DEPRECATED: This tool has been replaced by hub_create_file_from_content.

  • Get file content

    [DEPRECATED] This tool is deprecated.

  • Get meeting assets

    READ-ONLY

See all 20 Zoom tools

Control

What Runlayer can see and stop in GitHub Copilot

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

  • Gateway policy (available)

    Every Zoom call from GitHub Copilot 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 as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination