Connect HubSpot to GitHub Copilot
Give GitHub Copilot governed access to HubSpot’s 30 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add HubSpot 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 HubSpot in Runlayer
Add HubSpot 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 HubSpot’s 30 tools through the plugin’s search and execute tools.
GitHub Copilot setup guide - 3
Sign in to HubSpot
Sign in the way HubSpot requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use HubSpot from GitHub Copilot
HubSpot’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.
Tools
30 HubSpot tools in GitHub Copilot
Runlayer policy decides which of these GitHub Copilot users can call. 16 read data only and 5 can change or delete data.
Discover HubSpot schema
Searches HubSpot schema to discover available data types or look up known types directly.
Get AEO metrics
Portal-level AEO analytics: brand visibility, mentions, citations, competitor share-of-voice, and per-assistant breakdowns for a date window.
Get campaign attribution reports
REQUIRED FIRST STEP: before your first call, invoke tool_guidance for "get_campaign_attribution_reports" and follow it.
Get content analytics report
Run a content analytics report across landing pages, website pages, and blog posts in the portal.
Get conversation channel metadata
List inboxes, channels, and channel instances in this portal.
Get CRM objects
Fetches multiple CRM objects of the same object type in a single request.
Get marketing email analytics
Provides analytics data for marketing emails based on sends in the given date range.
Get organization details
Get organization-wide teams, job titles (roles), seats, and account info (timezone, currency, account type, portal name).
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 HubSpot 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
