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.

Connect Intercom and GitHub See reverse direction

Trigger app

Intercom as the trigger

Workflows fire when something happens in Intercom.

Action app

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

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

Intercom → GitHub

When something happens in Intercom, do it in GitHub.

5 Intercom triggers wired to 23 GitHub actions. Most-used pairing: New Contact → Add Labels.

GitHub → Intercom

Or fire it the other way around.

1 GitHub triggers wired to 20 Intercom actions downstream.

New GitHub Event

See GitHub → Intercom →

Popular pairings

Common Intercom → GitHub workflows.

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

Showing 9 of 115 combinations

When new contact in Intercom, add labels in GitHub.

Fires when a new contact (lead or user) is created in Intercom. Use to enrich, sync into your CRM, or kick off a welcome sequence.

When new contact in Intercom, create comment in GitHub.

Fires when a new contact (lead or user) is created in Intercom. Use to enrich, sync into your CRM, or kick off a welcome sequence.

When new contact in Intercom, create issue in GitHub.

Fires when a new contact (lead or user) is created in Intercom. Use to enrich, sync into your CRM, or kick off a welcome sequence.

When new contact in Intercom, create pull request in GitHub.

Fires when a new contact (lead or user) is created in Intercom. Use to enrich, sync into your CRM, or kick off a welcome sequence.

When conversation closed in Intercom, add labels in GitHub.

Fires when an Intercom conversation is closed by an admin. Common use: send CSAT survey, log resolution to CRM, run an AI quality check on the resolved thread.

When conversation closed in Intercom, create comment in GitHub.

Fires when an Intercom conversation is closed by an admin. Common use: send CSAT survey, log resolution to CRM, run an AI quality check on the resolved thread.

When conversation closed in Intercom, create issue in GitHub.

Fires when an Intercom conversation is closed by an admin. Common use: send CSAT survey, log resolution to CRM, run an AI quality check on the resolved thread.

When conversation closed in Intercom, create pull request in GitHub.

Fires when an Intercom conversation is closed by an admin. Common use: send CSAT survey, log resolution to CRM, run an AI quality check on the resolved thread.

When new conversation in Intercom, add labels in GitHub.

Fires when a new conversation is started in Intercom (by a user via messenger/email or by an admin). The standard inbound hook for AI triage, routing, and bot handoff.

How it works

Connect Intercom and GitHub in five steps.

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

1
Connect
Authorize Intercom and GitHub
Open Tiny Command, authorize Intercom and GitHub once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Intercom trigger
Drop the Intercom → New Contact trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/intercom.trigger-contact-created
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
Action
Add the GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the Intercom payload into the GitHub inputs.
github.add-labels-to-issue
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 Intercom + GitHub.

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.

Other apps that pair well with Intercom.

Intercom + Gmail

Intercom + Slack

Communication

Intercom + Google Sheets

Spreadsheets & Databases

Wire Intercom to GitHub in 2 minutes.

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

Try for free Request a demo

GitHub + Intercom: bug reports flowing both ways.

Pick the way that fits your stack.

When something happens in Intercom, do it in GitHub.

Or fire it the other way around.

Common Intercom → GitHub workflows.

Connect Intercom and GitHub in five steps.

Questions about Intercom + GitHub.

Other apps that pair well with Intercom.

Wire Intercom to GitHub in 2 minutes.

Be the first to know what's next.