Skip to content
Business productivity ⇄ Human resources

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

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

Keep the people, teams, and status that GitHub and Greenhouse share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.

Each tool in GitHub keeps its own list of who can use it: users, members, or agents, along with the team they sit on and whether they are still active. Greenhouse is the authoritative record of the same people as employees, with their department, manager, and employment status. When those two are connected only by manual account admin or a periodic export, the work tools drift: new hires wait days for access, team and manager changes never catch up, and people who have left keep standing accounts.

Stacksync syncs Releases, Workflow runs (Actions), Organizations and Teams, Users in GitHub with Scheduled Interviews, Users, Departments and Offices, Candidates in Greenhouse bi-directionally and in real time. A person added, moved, or offboarded in Greenhouse creates or updates the matching user in GitHub within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where GitHub captures details of its own, such as a corrected contact or a login identity, those can flow back to Greenhouse in whichever direction you configure.

Because the sync is field-level, each system keeps its own extras; only the shared facts, who a person is, which team they belong to, and whether their access should be on, are held in agreement.

Common use cases

  • 01 Mirror repository, PR, and workflow-run data into a Postgres database for engineering-metrics reporting.
  • 02 Sync organization and team membership with an identity or HR system to automate access reviews and offboarding.
  • 03 Stream Jobs, Departments, and Offices into a reporting database for recruiting funnel and time-to-fill dashboards.
  • 04 Export Scorecards and Scheduled Interviews to a data warehouse to analyze interviewer load and interview outcomes.

Common sync patterns

One employee directory

A person's name, title, contact details, or status corrected in either system updates the other, so both sides stop maintaining separate copies of the same person.

Org and team structure kept current

Department, team, and reporting-line changes from Greenhouse keep the groups, queues, or projects in GitHub assigned to the right people.

Where GitHub routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Greenhouse, the queues, ownership, or approvals in GitHub update to match, so work reaches whoever holds the role now.

What you can sync between GitHub and Greenhouse

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 Greenhouse objects How this pairing syncs
Users Author and assignee identities matched to internal directories. Users Greenhouse users (recruiters, hiring managers); read and written, and referenced by the On-Behalf-Of header on every write. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Issues Synced two-way with project trackers and support tools, including labels and assignees. Jobs Requisitions with openings, hiring team, departments, and offices; created and patched via Harvest, read out for funnel and time-to-fill reporting. Issues is specific to GitHub and Jobs to Greenhouse — 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. Offers Offer records tied to an Application with status and custom offer fields; readable and patchable, commonly synced to HRIS on hire. Pull Requests is specific to GitHub and Offers to Greenhouse — 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. Scorecards Interviewer feedback and ratings tied to interviews; read-only in Harvest, exported to a warehouse for interview analytics. Commits is specific to GitHub and Scorecards to Greenhouse — each maps to any object or custom field on the other side.
Releases Tagged versions synced into changelogs, CRMs, or customer-notification systems. Scheduled Interviews Interview events with interviewers, times, and rooms; full create/update/delete support for calendar and reporting syncs. Releases is specific to GitHub and Scheduled Interviews to Greenhouse — each maps to any object or custom field on the other side.
Workflow runs (Actions) CI results synced into incident and reporting systems. Departments and Offices Org structure attached to Jobs; read and written to keep reporting hierarchies aligned with an HRIS or warehouse. Workflow runs (Actions) is specific to GitHub and Departments and Offices to Greenhouse — each maps to any object or custom field on the other side.

How changes propagate between GitHub and Greenhouse

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 Greenhouse 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 Greenhouse through its API, with automatic retries and rate-limit backoff.

Greenhouse GitHub Sub-second propagation

DetectionGreenhouse notifies Stacksync of record changes through webhook events. HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after /.

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.
  • Greenhouse: Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
What ships with GitHub ⇄ Greenhouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Greenhouse

Integration surface
Harvest REST API (plus read-only Job Board API and the Ingestion API for bulk candidate import)
Authentication
HTTP Basic Auth with a Harvest API key (key as username, blank password, colon appended then Base64-encoded); write calls require an On-Behalf-Of header naming the Greenhouse user
Change detection
HMAC-SHA256 signed webhooks for candidate, application, job, and interview events, plus polling list endpoints with created_after / updated_after / last_activity_after filters
Capabilities
read · write · webhooks
Rate limits
Harvest enforces a per-integration limit over a rolling 10-second window (X-RateLimit-Limit, commonly 50 requests / 10s for approved integrations); responses carry X-RateLimit-Remaining and, on a 429, X-RateLimit-Reset and Retry-After.
Greenhouse setup guide
How it works

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

    Choose tables

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

GitHub and Greenhouse 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 457 integrations available for GitHub and Greenhouse.

Popular · 8 of 457
All GitHub integrations All Greenhouse 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