Skip to main content
Book a demo

Connect Salesforce to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Salesforce

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

  4. 4

    Use Salesforce from GitHub Copilot

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

Tools

21 Salesforce tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 7 read data only and 1 can change or delete data.

  • Create record

    Create a new Salesforce record.

  • Delete record

    Delete a Salesforce record by ID.

  • Describe object

    Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.

  • Get limits

    Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.

  • Get record

    Retrieve a single Salesforce record by its ID.

  • List objects

    List all sObjects (standard and custom objects) available in the Salesforce org.

  • Query

    Execute a SOQL (Salesforce Object Query Language) query.

  • Query more

    Retrieve the next page of results from a SOQL query.

See all 21 Salesforce 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 Salesforce 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