Skip to content
Per-pair page

GitHub + Intercom: bug reports flowing both ways.

Create GitHub issues from Intercom bug reports, and notify the original Intercom user when the fix ships. Closes the loop between support conversation and engineering.

Trigger app
GitHub as the trigger

Workflows fire when something happens in GitHub.

Action app
Intercom as the action

Workflows do something in Intercom, instantly.

See all 20 actions →
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

GitHubIntercom

When something happens in GitHub, do it in Intercom.

1 GitHub triggers wired to 20 Intercom actions. Most-used pairing: New GitHub EventAssign Conversation.

IntercomGitHub

Or fire it the other way around.

5 Intercom triggers wired to 23 GitHub actions downstream.

See IntercomGitHub
Popular pairings

Common GitHub → Intercom workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 4 of 20 combinations
How it works

Connect GitHub and Intercom in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize GitHub and Intercom

    Open Tiny Command, authorize GitHub and Intercom once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitHub trigger

    Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/github.trigger-event
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Intercom action

    Drop the Intercom → Assign Conversation action below it. Map fields from the GitHub payload into the Intercom inputs.

    intercom.assign-conversation
  5. 5
    Publish
    Publish and forget

    Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about GitHub + Intercom.

How do I file an Intercom bug as a GitHub issue?
Intercom Conversation tagged "bug" → GitHub Create Issue with body = full conversation transcript and customer email. Engineering triages in their tool of choice.
Can I notify the Intercom user when their bug is fixed?
Yes. GitHub Issue Closed (with "bug" + "shipped" labels) → look up the Intercom conversation ID stored in the issue body → Intercom Add Reply with "Fix shipped in version X. Thanks for the report!"
How do I avoid creating duplicate GitHub issues from the same bug report?
Trigger on Intercom tag added (manual support action), not every message. The agent decides when to escalate; the workflow fires once per escalation. Search GitHub for existing issue with the conversation ID first.
Can I AI-classify Intercom messages before creating GitHub issues?
Yes. Insert a Claude/OpenAI step. Confirmed bug → GitHub Issue. Feature request → different workflow (Linear, Notion). User error → suggest help-article reply. Filters out non-engineering work.
How do I label the GitHub issue with customer context?
Get the Intercom contact's plan tier, monthly spend, and any custom attributes. Pass into the issue body and as labels (e.g., "tier:enterprise"). Triage prioritizes by customer impact.
Can I auto-link related GitHub issues for similar Intercom reports?
Yes. AI checks if the bug description matches an existing GitHub issue. If similar, add the new Intercom conversation as a comment on the existing issue instead of creating a duplicate.
Related

Other apps that pair well with GitHub.


Wire GitHub to Intercom in 2 minutes.

Free tier available. No credit card. No onboarding call.