GitHub Issues as native HubSpot records.
Resonate Issues syncs GitHub issues two-way into HubSpot as a first-class Issue object - associated with the tickets, deals, companies, and projects they affect. Support escalates in one click, engineering never leaves GitHub, and nobody asks “any update on that bug?” again.
| Issue | Status | Repository | PR | Actions |
|---|---|---|---|---|
| Checkout 500 for EU Visa cards acme/webapp#214 | In progress | acme/webapp | PR open | PreviewUnlink |
| Add retry to payment webhook acme/api-server#188 | Done | acme/api-server | Merged | PreviewUnlink |
Support runs on tickets. Engineering runs on GitHub.
Between them: pasted links that go stale, “any update?” pings, and a CRM that can't answer which customers are waiting on which fix. HubSpot's built-in tracker integrations write a few read-only fields onto a ticket - you can't edit them, the sync can lag by hours, and there's still no object to build issue-level views or reports around. The work your customers care about most is invisible to the system that manages your customers.
Support can't see status
Reps tab over to GitHub - or interrupt an engineer - to answer a customer about a bug they reported weeks ago.
Engineering gets pinged
Every “is this fixed yet?” lands in Slack, because the CRM has no live view of the issue, its assignee, or its PR.
RevOps can't measure it
No object means no reporting: open bugs by customer, revenue blocked on engineering, time from escalation to fix - all unanswerable.
Issues become records - with everything records get for free.
Not fields bolted onto a ticket: a first-class Issue object, auto-provisioned in your portal on install. It shows up next to contacts and deals with its own index page, and every native HubSpot capability - views, workflows, reports, associations - just works.
| Title | Repository (synced path) | Status Category | URL | Object create date/time | Owner |
|---|---|---|---|---|---|
| Checkout 500 for EU Visa cards | acme/webapp | In progress | github.com/acme/webapp/is… | Today at 9:14 AM | No owner |
| SSO session expires after 15 min | acme/webapp | Open | github.com/acme/webapp/is… | Yesterday at 4:51 PM | No owner |
| Feature: bulk export to S3 | acme/api-server | Open | github.com/acme/api-serve… | Aug 4, 2026 3:56 PM | No owner |
| Add retry to payment webhook | acme/api-server | Done | github.com/acme/api-serve… | Aug 1, 2026 11:02 AM | No owner |
| Dark mode for customer portal | acme/webapp | Canceled | github.com/acme/webapp/is… | Jul 28, 2026 2:19 PM | No owner |
Lists and views
Filter, search, and segment Issues like contacts or deals - by repository, status, priority, or any property.
Five associations
Every Issue associates with the Tickets, Deals, Companies, Contacts, and Projects it affects.
Workflow triggers
Enroll on any Issue property change. Issue closed → update the ticket, email the contact, ping the owner.
Real reporting
Dashboards on engineering work: open issues by repo, cycle time, or revenue-weighted open work via deal associations.
PR state included
Each Issue carries its related pull request and state - open, merged, or closed - visible to support without asking.
Usable standalone
No GitHub? The Issue object works on its own inside HubSpot - connect a tracker any time and sync picks up from there.
Escalate a ticket to engineering in one click.
The Issues card sits on every Ticket record. Create an issue - title, description, and priority prefill from the ticket - pick a repository, and it's in GitHub seconds later, permanently associated to the ticket. Or link an issue that already exists. The mocks below are interactive - click around.
| Issue | Status | Repository | PR | Actions |
|---|---|---|---|---|
| Checkout 500 for EU Visa cards acme/webapp#214 | In progress | acme/webapp | PR open | PreviewUnlink |
| Add retry to payment webhook acme/api-server#188 | Done | acme/api-server | Merged | PreviewUnlink |
Issues on Tickets
- Live status, repository, and PR state for every linked issue
- Create issue prefills from the ticket and associates automatically
- Link existing issues by search; unlink never deletes anything
- Pick a repo and it pushes to GitHub - or stay HubSpot-only when no default repo is set
GitHub Issues on Projects
- Link a repository to a HubSpot Project and manage its issues there
- Board view: a read-only kanban that follows tracker status
- Open / In progress / Done / Canceled - normalized across trackers
- The same create and link flows, scoped to the project's repo
One admin step: cards aren't added to record views automatically. Open a Ticket, hit Customize record → middle column → Add cards, and place Issues where your team works.
Edit on either side. It converges in one hop.
Webhooks drive both directions - no scheduled polling, no overnight batch. Close an issue in GitHub and the record flips to Done in seconds; retitle it in HubSpot and GitHub follows. Every write carries a content fingerprint and an origin tag, so when the change echoes back it's recognized and dropped: two-way sync that provably can't loop.
- Both directions: title, description, status (open, in progress, done, canceled), labels, assignees
- From GitHub: related pr and its state, comment count and author, milestone, repository and issue number, created / updated / closed timestamps
- GitHub comments become notes on the Issue record
- Notes → GitHub comments only if you opt in (off by default)
A change lands - GitHub webhook or HubSpot property update - and is signature-verified.
The sync engine computes a fingerprint of the synced fields and tags the write with its origin.
The counterpart is updated. When that update echoes back as a webhook, the fingerprint matches - and it's dropped.
Convergence in at most one hop, each direction. No infinite loops, no API spam, no scheduled polling.
The moment issues are records, HubSpot does the rest.
Everything below is native HubSpot working on a native object - no extra tooling, no exports.
Close the loop automatically
Issue flips to Done → workflow updates the associated ticket and emails the customer who reported it. The escalation resolves itself.
Revenue-weighted engineering
Issues associate with deals and companies, so you can finally report on open ARR blocked by engineering work - per repo, per customer, per quarter.
SLA on escalations
Time from ticket escalation to issue Done is just two timestamps on associated records. Put it on a dashboard; watch it drop.
PR-aware follow-ups
Related PR state lives on the record. Notify account owners when the fix merges - before the customer asks.
Sync you don't have to babysit.
Two-way sync tools have a reputation: loops, floods, and mystery overwrites. This one was engineered against all three - and it's conservative by default everywhere data crosses the boundary.
Provably loop-free
Every write is fingerprinted and origin-tagged, so echoes are dropped at the boundary. Changes converge in one hop - two-way sync can't ping-pong.
Least-privilege GitHub access
A per-repository GitHub App: you pick exactly which repos it can see, and you can change or revoke access any time.
Notes stay private by default
GitHub comments become HubSpot notes automatically. The reverse - HubSpot notes posted to GitHub - is off until you switch it on, because notes can hold customer context.
Webhooks, not polling
Both directions are event-driven. Changes land in seconds, and nothing scans your portal or repos on a schedule.
Connected in four steps. GitHub optional.
Connect GitHub (optional)
Install the GitHub App and pick exactly which repositories it can access. Or skip - Issues work inside HubSpot on their own.
Choose repositories
Select the repos to sync and set a default repository for issues created from HubSpot.
Connect HubSpot
One OAuth click. The Issue object and its properties are provisioned automatically - usable right away.
Import history
Bring in recent issues (last 30 days), everything, or start clean. Sync stays two-way from that point on.
Frequently asked questions.
What teams ask before wiring GitHub into HubSpot - including the honest limits.
More HubSpot apps by Resonate.
Native HubSpot extensions that pair naturally with your support and revenue stack.
0CodeTools
Workflow actions for associations, custom integrations no code required.
View appHubSpot appDocsHub
Document automation and search embedded in HubSpot records.
View appHubSpot appTelegram for HubSpot
Connect Telegram to HubSpot four ways: support inbox, team notifications, workflow messages to customers, and your personal account via Telegram Business.
View appPut engineering work inside your CRM.
Connect GitHub and HubSpot at github.resonatehq.com - or book a walkthrough and we'll map the escalation flow to your pipelines together.
- Issue object provisioned automatically on connect
- Two-way, webhook-driven sync - changes land in seconds
- Works standalone too: track Issues in HubSpot without a tracker
Get started
GitHub is supported today via a per-repository GitHub App; Jira and Linear are planned behind the same Issue object. Comment mirroring is create-only, and posting HubSpot notes to GitHub is off by default.