Connect Pendo to GitHub Copilot
Give GitHub Copilot governed access to Pendo’s 54 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Pendo to GitHub Copilot in four steps
Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.
- 1
Approve Pendo in Runlayer
Add Pendo from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot to Runlayer
GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Pendo’s 54 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to Pendo
Sign in the way Pendo requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Pendo from GitHub Copilot
Pendo’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
54 Pendo tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call.
Account metadata schema
Return the set of metadata fields available for accounts.
Acquisition trend
Count new visitors or accounts per period - users whose first-ever interaction with the app (scope='app'), a specific page or feature (scope='page' or 'feature'), or a track event…
Agent analytics conversation analysis
Lists and ranks individual AI agent conversations with per-conversation metrics.
Agent analytics issue analysis
Returns issue diagnoses, flagged response tool/model usage, and user prompt content for the events of a specific detected issue cluster in AI Agent Analytics.
Agent analytics key metrics
Returns key aggregate metrics for AI agent conversations with period-over-period comparison.
Agent analytics tracked issue analysis
Deep-dives into a single tracked issue in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, sampled issue explanations from detected issue clusters, the tools and…
Agent analytics tracked use case analysis
Deep-dives into a single tracked use case in AI Agent Analytics for a specific AI agent, surfacing the visitors and accounts, the tools and models the agent invoked, sampled explanations, and a…
Aggregate entity usage
Rank pages, features, or track events by aggregate usage over a date range, or measure a named set of them as one population.
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 Pendo 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