Skip to main content

Connect Gmail to GitHub Copilot

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

Set up

Add Gmail 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 Gmail in Runlayer

    Add Gmail 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 Gmail’s 16 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Gmail

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

  4. 4

    Use Gmail from GitHub Copilot

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

Tools

16 Gmail tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 6 read data only.

  • Add labels

    Add one or more labels to a message or multiple messages

  • Archive messages

    Archive one or more messages (remove from inbox)

  • Create draft

    Create a draft email that can be edited later or sent

  • Create label

    Create a new label in the user's Gmail account

  • Fetch attachment

    Fetch a Gmail message attachment.

  • Fetch message

    Fetch the full content of a Gmail message using its message ID (don't use external tools to read messages)

  • List drafts

    List all draft messages with pagination support

  • List labels

    List all available labels in the Gmail account

See all 16 Gmail 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 Gmail 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