Skip to content
CRM ⇄ Business productivity

Freshworks CRM to GitHub integration — real-time, two-way sync

Keep Freshworks CRM and GitHub 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 Freshworks CRM and GitHub

Sync what happens in GitHub with the customer records in Freshworks CRM, 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 Workflow runs (Actions), Organizations and Teams, Users, Labels and Milestones in GitHub to Lists, Notes, Contacts, Accounts in Freshworks CRM with bi-directional, real-time sync. Activity and record changes in GitHub update the matching contact or account in Freshworks CRM, and CRM data flows the other way wherever GitHub can store and use it.

Common use cases

  • Sync organization and team membership with an identity or HR system to automate access reviews and offboarding.
  • Create GitHub issues automatically from records written elsewhere, such as bug reports logged in a CRM case object.
  • Keep list membership aligned with segments computed in the warehouse.
  • Mirror deal and activity data into a Postgres database that internal tools query directly.

Where GitHub handles support or shared inboxes

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

Where GitHub supplies contact or company data

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

Where GitHub can store CRM context: fields kept current

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

What you can sync between Freshworks CRM and GitHub

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.

Freshworks CRM objects GitHub objects
Accounts Company records kept consistent with ERP and billing systems. Repositories Top-level containers whose metadata and settings syncs read to scope other objects.
Deals Pipeline records synced out for forecasting and full-funnel reporting. Issues Synced two-way with project trackers and support tools, including labels and assignees.
Tasks Follow-ups created from external signals such as product usage events. Pull Requests Review state, status checks, and merge status feed engineering dashboards and workflow tools.
Appointments Meeting records readable for activity reporting. Commits Read-only history used to link code activity to tickets and releases.
Sales activities Logged activity types used in engagement and productivity analysis. Releases Tagged versions synced into changelogs, CRMs, or customer-notification systems.
Lists Contact list membership synced against segments computed in a warehouse. Workflow runs (Actions) CI results synced into incident and reporting systems.
What ships with Freshworks CRM ⇄ GitHub

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Freshworks CRM and GitHub connectors work

Freshworks CRM

Integration surface
REST API
Authentication
API key sent as a Token authorization header
Change detection
Polling with updated-at filters; outbound webhooks can be configured through workflow automations
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that vary by plan

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.
How it works

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

    Choose tables

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

Freshworks CRM and GitHub 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 Freshworks CRM and GitHub.

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