Quick Start Guide
Connect Revenue Growth Agent (RGA) to HubSpot in one step. This guide is for HubSpot admins. The connection takes about five minutes, and you only do it once for your whole portal.
What you get: the RGA Meeting Prepper, embedded as a native card on your Contact records — and on Lead records if your subscription includes HubSpot's leads feature. Reps launch AI-powered meeting prep without leaving HubSpot. Discovery, proposals, and the rest of the RGA agent suite run in the RGA web app today; HubSpot-embedded versions are on the roadmap.
No package, no certificate, no copy-pasted keys. The connection is standard HubSpot OAuth: you click Connect, approve the scopes on HubSpot's consent screen, and you're done. RGA encrypts the resulting tokens with AES-256-GCM before they are stored, and creates the custom contact properties it needs automatically.
Before you begin
You'll need:
- HubSpot Super Admin access (or a user with permission to install apps). Only an admin connects the portal once; your reps don't need admin rights to use the prepper.
- Any HubSpot subscription for the Contacts card. App cards from the marketplace work across HubSpot hubs and tiers. The Leads card additionally requires Sales Hub Professional or Enterprise, the tiers that include HubSpot's leads feature.
- An active Revenue Growth Agent subscription. The HubSpot integration is included with your RGA plan. If you're not yet a customer, we'll get you set up during onboarding.
The entire connection is driven from one page: Settings → Integrations → HubSpot in the RGA web app.
Step 1: Connect your portal
- In the RGA web app, go to Settings → Integrations → HubSpot.
- Click Connect HubSpot. You'll be redirected to HubSpot's authorization screen.
- Pick the account to connect (if you belong to more than one) and review the scopes. RGA requests contact read/write and the ability to create its custom contact properties, plus optional company and lead read access. No deal or timeline scopes are requested.
- HubSpot shows an "unverified app" notice and asks you to type "I accept the risk." This is expected: it appears for any app while its HubSpot Marketplace verification is in progress, and it goes away once the listing is approved. Type the phrase and continue.
- Click Connect app.
Behind the scenes, RGA verifies with HubSpot which portal the authorization actually belongs to before storing anything, so a connection can never be bound to the wrong account. Tokens are encrypted at rest, and the RGA custom contact properties (prep session, prep date, prep document link, sync status) are created in your portal automatically.
Back on the Integrations page you'll see a read-only Connected status with your Hub ID, domain, and granted scopes. There is nothing else to configure.
Step 2: Find the card
- Open any Contact record in HubSpot.
- Look for RGA Meeting Prepper in the right sidebar.
- If you don't see it, click Customize at the top of the record, then Add cards to the right sidebar. Open the Card library tab and search for RGA — add RGA Meeting Prepper. This is a one-time, portal-wide layout change an admin can make for everyone.
On portals with leads enabled, the RGA Meeting Prepper (Leads) card appears in the lead preview panel — click a lead in the leads list to open it. HubSpot places lead cards in the preview panel rather than on a full record page.
Run your first meeting prep
- On a contact, the card loads with the fields HubSpot already knows — name, email, company, title, LinkedIn, website, industry, and company size.
- Click Enrich Contact Data to fill the blanks from public data. Your entries are never overwritten, and the exact spelling of the name and company matters: the research keys off them.
- Complete any remaining fields. Run Meeting Prep enables once every field is filled, because partial input produces a noticeably weaker brief.
- Click Run Meeting Prep. Progress shows in the card; a typical prep takes one to two minutes.
- The brief opens right inside HubSpot when it's ready. You can also open it in a browser tab or download it as a .docx.
Everything is saved back to the contact: the prep date, the session, a shareable brief link, and the contact fields your rep confirmed. Reopen the record any time and the card shows the latest prep at a glance — opener, pain points, and discovery questions — with the full brief one click away.
On a lead
The same flow runs from the lead preview panel. A HubSpot lead is built around a contact, so the card works with the lead's associated contact: it reads that contact's details and saves the prep results to it. If the connection was made before lead support existed, reconnect once from Settings → Integrations → HubSpot to grant the lead read scope.
Troubleshooting
| Symptom | Fix |
|---|---|
| RGA isn't in the Card library at all | Until RGA is approved on the HubSpot Marketplace, the card is enabled per-portal. If you've connected but the card doesn't appear anywhere in Customize → Add cards → Card library, contact support@revenuegrowthagent.com and we'll enable it for your Hub ID. |
| Card is in the library but not on the record | Click Customize on the record page, Add cards to the right sidebar, and add RGA Meeting Prepper from the Card library tab. |
| Card says HubSpot isn't connected | An admin needs to connect (or reconnect) from Settings → Integrations → HubSpot in the RGA web app. |
| No Leads card | Leads require Sales Hub Professional or Enterprise, and the leads feature must be active in the portal. The Contacts card works regardless. |
| Lead card asks for a reconnect | The connection predates lead support. Reconnect once from the RGA Integrations page to grant the lead read scope. |
| A field didn't save to the contact | RGA creates its custom properties on connect. If a portal customizes or removes a standard property, RGA saves everything else and skips just that field. Check the property's options under Settings → Properties in HubSpot. |
Security at a glance
- Standard HubSpot OAuth; you can revoke the connection from either side at any time.
- Tokens are encrypted at rest with AES-256-GCM, with the encryption key held in a separate system from the encrypted data.
- Every request from the in-CRM card is cryptographically signed by HubSpot and verified by RGA before any data moves.
- Your HubSpot data is never used to train AI models.
The full write-up for your security team is at Security & Privacy, and platform-wide controls are in the Trust & Security Center.
Questions? Email support@revenuegrowthagent.com.