Skip to content
Business productivity ⇄ CRM

GitHub to Intercom integration — real-time, two-way sync

Keep GitHub and Intercom in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect GitHub and Intercom

Sync what happens in GitHub with the customer records in Intercom, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever GitHub holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Repositories, Issues, Pull Requests, Commits in GitHub to Data Events, Custom Data Attributes, Tags, Segments in Intercom with bi-directional, real-time sync. Activity and record changes in GitHub update the matching contact or account in Intercom, and CRM data flows the other way wherever GitHub can store and use it.

Common use cases

  • 01 Publish release data into customer-communication tools when a new version ships.
  • 02 Two-way sync of GitHub issues with Jira, Linear, or a support system so engineering and customer-facing teams work in their own tools.
  • 03 Route qualified leads from Intercom conversations into the CRM as leads or opportunities in near real time
  • 04 Sync contacts and companies bi-directionally with the CRM so support sees deal context and sales sees conversation history

Common sync patterns

Where GitHub handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Intercom, so sales sees open issues before the next call.

Where GitHub supplies contact or company data

Enriched fields land directly on records in Intercom, and refreshes keep them from going stale.

Where GitHub can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Intercom sync into GitHub, so people working there have the context without switching tools.

What you can sync between GitHub and Intercom

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

GitHub objects Intercom objects How this pairing syncs
Issues Synced two-way with project trackers and support tools, including labels and assignees. Articles Help center content is accessible via API for knowledge sync and audits. Issues is specific to GitHub and Articles to Intercom — each maps to any object or custom field on the other side.
Pull Requests Review state, status checks, and merge status feed engineering dashboards and workflow tools. Contacts A single contact model covers both users and leads, distinguished by a role attribute. Pull Requests is specific to GitHub and Contacts to Intercom — each maps to any object or custom field on the other side.
Commits Read-only history used to link code activity to tickets and releases. Companies Company records group contacts and carry plan and account attributes used in segmentation. Commits is specific to GitHub and Companies to Intercom — each maps to any object or custom field on the other side.
Releases Tagged versions synced into changelogs, CRMs, or customer-notification systems. Conversations Support and sales threads sync outward for analytics and CRM context. Releases is specific to GitHub and Conversations to Intercom — each maps to any object or custom field on the other side.
Workflow runs (Actions) CI results synced into incident and reporting systems. Tickets Structured ticket records track issues alongside conversational threads. Workflow runs (Actions) is specific to GitHub and Tickets to Intercom — each maps to any object or custom field on the other side.
Organizations and Teams Membership data synced with identity systems and HR directories for access reviews. Data Events Behavioral events pushed in from product databases trigger messages and flows. Organizations and Teams is specific to GitHub and Data Events to Intercom — each maps to any object or custom field on the other side.

How changes propagate between GitHub and Intercom

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

GitHub Intercom Sub-second propagation

DetectionGitHub notifies Stacksync of record changes through webhook events. Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases.

DeliveryEach detected change is written to Intercom through its API, with automatic retries and rate-limit backoff.

Intercom GitHub Sub-second propagation

DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.

DeliveryEach detected change is written to GitHub through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • GitHub: Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.
  • Intercom: Subject to per-app rate limits on the Intercom API.
What ships with GitHub ⇄ Intercom

Connect GitHub and Intercom for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every GitHub–Intercom connection.

Real-time

Two-way sync

Changes in GitHub or Intercom instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever GitHub or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single GitHub or Intercom record.

Observability

Monitoring

Track your GitHub ⇄ Intercom sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between GitHub and Intercom.

How the GitHub and Intercom connectors work

GitHub

Integration surface
REST API and GraphQL API
Authentication
OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens
Change detection
Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases; polling for backfill
Capabilities
read · write · webhooks
Rate limits
Authenticated REST requests are limited to 5,000 per hour per user; GitHub Apps scale limits per installation.

Intercom

Integration surface
REST API
Authentication
OAuth 2.0 for public apps or a workspace access token
Change detection
Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-app rate limits on the Intercom API
How it works

How to connect GitHub to Intercom — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate GitHub and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    GitHub connected
    Intercom connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the GitHub and Intercom objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · GitHub ⇄ Intercom
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    GitHub Intercom
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

GitHub and Intercom integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 464 integrations available for GitHub and Intercom.

Popular · 7 of 464
All GitHub integrations All Intercom integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own