Integration · HubSpot
Push Bug Reports + Session Replays To HubSpot In One Click
Every HubSpot ticket from Relyv ships with a deep link to the session replay, the AI-drafted bug report, console + network evidence, and environment metadata. Customer-success teams stop translating between marketing-tool screenshots and engineering bug trackers.
What you get
OAuth in 60 seconds
Authorise once via HubSpot OAuth. We exchange a code for an access + refresh token, fetch your portal display name, and route every Relyv-generated ticket into the pipeline you pick — no API keys to copy or rotate manually.
Pipeline + priority picker
Choose which HubSpot ticket pipeline receives Relyv reports (Support, Engineering, Marketing, custom — every pipeline you have appears in the dropdown). Severity maps to HubSpot priority verbatim — URGENT / HIGH / MEDIUM / LOW.
AI bug report pre-filled
The Subject is the AI-written title; the Content field carries the AI reproduction steps + environment block + failing-network calls + console errors + replay deep link. Engineers open the HubSpot ticket and have everything they need to fix.
Token refresh handled
HubSpot access tokens expire every 30 minutes — Relyv's integration layer auto-refreshes using the long-lived refresh token. No manual reconnection required.
Setup in four steps
- 1
Connect HubSpot via OAuth
A workspace admin clicks "Connect HubSpot" in Relyv settings. Standard HubSpot OAuth prompt; we request the tickets + oauth + crm.objects.contacts.read scopes. No code, contact-list, or marketing-data access.
- 2
Map Relyv projects to HubSpot pipelines
After connect, Relyv loads your HubSpot ticket pipelines. Pick the default pipeline for each Relyv project; override per-ticket at creation time.
- 3
Click "Send to..." from any session
From the dock, the side panel, or the angular-viewer session page, pick HubSpot in the "Send to..." dropdown. Title, Content, Pipeline, and Priority are pre-filled.
- 4
Ticket lands in HubSpot
The ticket appears in the chosen pipeline's first stage with the AI repro + session evidence packet. Customer-success agents respond from HubSpot natively; the ticket's status, owner, and stage are visible to Relyv via the refresh-token-backed API.
Implementation details
What gets attached to a HubSpot ticket
AI-written subject; AI repro steps in the Content body; severity-mapped HubSpot priority; deep link back to the replay frame; environment block (browser + OS + viewport + connection type); list of failing fetch / XHR / WebSocket calls with status codes; list of console errors with stack traces; AI session summary; optional attached Playwright spec (Pro+ feature).
Stage selection
By default the ticket lands in the pipeline's first stage. To target a specific stage (e.g. "Needs Triage"), pass `stage:<stageId>` in the labels list at ticket-creation time. The integration parses that convention and sets `hs_pipeline_stage` accordingly.
Permissions and security
OAuth scopes: tickets (create + read), oauth (refresh tokens), crm.objects.contacts.read (associate tickets with contacts when known). No code, no marketing-list access, no email-content access. Token rotation is automatic; revoking from HubSpot admin instantly cuts access.
Frequently asked
Which HubSpot tiers are supported?
All HubSpot Service Hub tiers that include the Tickets object (Starter and above). Ticket pipelines were rolled out by HubSpot in 2022; portals without pipelines fall back to the default pipeline automatically.
Can I associate the ticket with a HubSpot contact?
Yes — when Relyv has the user's email (via the Identify API), the integration can look up the matching HubSpot contact and associate it on ticket creation. Useful for CSM workflows where the same contact ties to a deal + company.
What if our ticket priority enum is customised?
HubSpot's standard priority enum is URGENT / HIGH / MEDIUM / LOW; Relyv maps severity verbatim. If your portal uses a custom property (`hs_custom_priority`), set it via the integrations service's extra-fields hook — the standard `hs_ticket_priority` field is still always populated.
How is this different from Zapier-based HubSpot integration?
Zapier sees only the high-level Relyv events; it can't attach the AI repro or session evidence to the ticket body. Relyv's native integration (gt-relyv-integrations/internal/handler/providers/hubspot.go) uses the HubSpot CRM v3 API directly and posts the full evidence packet in the Content field at ticket creation — single round-trip, no Zapier subscription.
Can my AI agent file HubSpot tickets via MCP?
Yes — Relyv is MCP-native. Claude, Cursor, and Continue call get_session_intelligence to read the session, then invoke the integrations service to create the HubSpot ticket. The same flow a human triggers from the dock works for agents.
How is PII handled in the ticket body?
PII is masked on-device via 12-category regex + Luhn validation in the SDK (plus ONNX/WebGPU GLiNER deep-scan when the Relyv extension is installed) before bytes leave the browser. The ticket Content that lands in HubSpot already has credit cards, SSNs, emails, IBANs, etc. redacted. EU + US data residency available.
Ready to wire up HubSpot?
Every HubSpot ticket from Relyv ships with a deep link to the session replay, the AI-drafted bug report, console + network evidence, and environment metadata. Customer-success teams stop translating between marketing-tool screenshots and engineering bug trackers.