Question 1

How does IssueLinker connect HubSpot and GitHub?

Accepted Answer

Install IssueLinker, then authorize GitHub once with OAuth. From then on, every HubSpot ticket gets an IssueLinker card where you create or link a GitHub issue. There's nothing to deploy and no middleware to run.

Question 2

Does HubSpot have a native GitHub integration?

Accepted Answer

No. Unlike Jira, there is no first-party GitHub card for HubSpot tickets, so teams stitch it together with Zapier or other row-sync tools. IssueLinker is the embedded card that gap is missing.

Question 3

How is this different from a Zapier GitHub sync?

Accepted Answer

Zapier and similar tools copy fields one record at a time, usually one direction, with no card on the ticket. IssueLinker gives you an embedded card with true two-way sync of comments and issue state, with no per-record mapping to maintain.

Question 4

Do I have to create the GitHub issue manually?

Accepted Answer

No. From any HubSpot ticket, click Create issue in the card and the GitHub issue is created with the ticket subject and details pre-filled, plus a link back to the ticket.

Question 5

What syncs between HubSpot and GitHub?

Accepted Answer

The issue state, comments, and the link itself. When engineering comments on or closes the GitHub issue, that lands on the ticket; notes added in HubSpot show up on the issue. It's two-way and automatic on every linked ticket.

Question 6

Can I link an existing GitHub issue instead of creating a new one?

Accepted Answer

Yes. Search GitHub from the ticket card and link any existing issue. From that point on the ticket and issue stay in sync, so several tickets can point at the same issue when one bug affects many customers.

Question 7

Do we need a paid HubSpot tier or workflows?

Accepted Answer

No. IssueLinker works from the ticket card directly, so you don't need HubSpot's workflow tiers to create, link, or sync GitHub issues. You do need HubSpot tickets (Service Hub) enabled.

Question 8

Who needs to authorize the connection, and does it see our code?

Accepted Answer

Connecting GitHub runs through GitHub's OAuth, authorized once by someone with access to your repositories. IssueLinker works with issues and comments, not your source code.

Question 9

Can I choose which repository issues are created in?

Accepted Answer

Yes. When you create an issue from the ticket card you pick the GitHub repository it goes into, so issues land in the right project for your engineering team.

Question 10

Does engineering have to change anything?

Accepted Answer

No. Developers keep working in issues and pull requests as they do today. When they comment on or close the issue, that flows back to HubSpot automatically.

Question 11

Is my data secure?

Accepted Answer

IssueLinker connects over official HubSpot and GitHub OAuth and only touches the tickets and issues needed to keep them in sync. See our privacy policy for the specifics.

Question 12

Is there a free trial?

Accepted Answer

Yes, a 14-day free trial, no credit card required. After that it's $19/month.

Close the loop between support and GitHub.

What changes when support and engineering stay in sync

Built for the support-to-engineering handoff

Comment sync that actually works

An embedded card, not a Zapier sync

Status flows back on its own

Engineering never leaves GitHub

One flat price for connected teams

IssueLinker for GitHub

Put the support-to-engineering handoff on autopilot.

Frequently asked questions