Skip to content
Business productivity ⇄ CRM

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

Keep GitHub and Salesforce 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 Salesforce

Sync what happens in GitHub with the customer records in Salesforce, 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 Labels and Milestones, Repositories, Issues, Pull Requests in GitHub to Campaigns, Tasks and Events, Products and Price Books, Custom Objects in Salesforce with bi-directional, real-time sync. Activity and record changes in GitHub update the matching contact or account in Salesforce, and CRM data flows the other way wherever GitHub can store and use it.

Common use cases

  • Publish release data into customer-communication tools when a new version ships.
  • Two-way sync of GitHub issues with Jira, Linear, or a support system so engineering and customer-facing teams work in their own tools.
  • Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.

Where GitHub can store CRM context: fields kept current

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

Where GitHub handles support or shared inboxes

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

Where GitHub supplies contact or company data

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

What you can sync between GitHub and Salesforce

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 Salesforce objects
Workflow runs (Actions) CI results synced into incident and reporting systems. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce.
Organizations and Teams Membership data synced with identity systems and HR directories for access reviews. Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated.
Users Author and assignee identities matched to internal directories. Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP.
Labels and Milestones Classification fields mapped to statuses and sprints in external trackers. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records.
Repositories Top-level containers whose metadata and settings syncs read to scope other objects. Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines.
Issues Synced two-way with project trackers and support tools, including labels and assignees. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close.
What ships with GitHub ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever GitHub or Salesforce 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 Salesforce record.

Observability

Monitoring

Track your GitHub ⇄ Salesforce 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 Salesforce.

How the GitHub and Salesforce 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.

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect GitHub to Salesforce — 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 Salesforce 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
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the GitHub and Salesforce 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 ⇄ Salesforce
    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 Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

GitHub and Salesforce integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for GitHub and Salesforce.

Popular · 8 of 386
All GitHub integrations All Salesforce 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