Two-way sync
Changes in GitHub or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep GitHub and Smartrecruiters in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
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. Smartrecruiters 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 Pull Requests, Commits, Releases, Workflow runs (Actions) in GitHub with Interviews, Offers, Users, Approvals in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters 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 Smartrecruiters 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.
When someone is marked as leaving in Smartrecruiters, the matching account in GitHub is deactivated or flagged, so departures do not leave open access behind.
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.
Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in GitHub assigned to the right people.
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 | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Users Author and assignee identities matched to internal directories. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | 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. | Applications Links a Candidate to a Job and carries the current hiring status and source; created and advanced through statuses (screening, interview, offer, hired, rejected) via the Application API. | Issues is specific to GitHub and Applications to Smartrecruiters — 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. | Jobs Requisitions (positions) with openings, departments, locations, and hiring team; created, patched, and read out for requisition and time-to-fill reporting via the Jobs API. | Pull Requests is specific to GitHub and Jobs to Smartrecruiters — 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. | Job Postings Job ads and publications pushed to the career site and job boards; created and managed via the job publication endpoints (rate-limited to 2 requests/sec). | Commits is specific to GitHub and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Releases Tagged versions synced into changelogs, CRMs, or customer-notification systems. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Releases is specific to GitHub and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Workflow runs (Actions) CI results synced into incident and reporting systems. | Offers Offer records tied to an Application with status, custom offer fields, and offer documents; readable and writable, commonly synced to an HRIS on hire (documents endpoint limited to 2 requests/sec). | Workflow runs (Actions) is specific to GitHub and Offers to Smartrecruiters — each maps to any object or custom field on the other side. |
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.
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 Smartrecruiters through its API, with automatic retries and rate-limit backoff.
DetectionSmartrecruiters notifies Stacksync of record changes through webhook events. Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs.
DeliveryEach detected change is written to GitHub through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every GitHub–Smartrecruiters connection.
Changes in GitHub or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever GitHub or Smartrecruiters data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single GitHub or Smartrecruiters record.
Track your GitHub ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between GitHub and Smartrecruiters.
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.
Authenticate GitHub and Smartrecruiters with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the GitHub and Smartrecruiters 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between GitHub and Smartrecruiters: authenticate both systems, choose the objects to sync (such as GitHub's Users and Issues), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on GitHub: Webhooks with a broad event catalog covering issues, pull requests, pushes, and releases; polling for backfill. On Smartrecruiters: Webhooks API — subscribe to events (new application, candidate updated, status changed) delivered with a signing secret and retrievable callback logs; otherwise poll list endpoints with updated-after-style filters. No log-based change data capture. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the GitHub side: Pull Requests, Commits, Releases, Workflow runs (Actions), plus custom fields where GitHub exposes them. On the Smartrecruiters side: Interviews, Offers, Users, Approvals. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for GitHub and Smartrecruiters: Offboarding: no standing access after a departure; One employee directory; Org and team structure kept current. When someone is marked as leaving in Smartrecruiters, the matching account in GitHub is deactivated or flagged, so departures do not leave open access behind.
GitHub: REST API and GraphQL API. Authentication: OAuth 2.0, fine-grained personal access tokens, or GitHub App installation tokens. Smartrecruiters: SmartRecruiters REST APIs (SmartAPIs) on api.smartrecruiters.com — Candidates, Application, Jobs, Interviews, Offers, Users, Approvals, plus a Webhooks API for event subscriptions. Authentication: X-SmartToken API key header for a customer's own integration (grants full company access, no scopes or expiry), or OAuth 2.0 authorization-code flow for partner and Marketplace apps with user-scoped permissions. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 457 integrations available for GitHub and Smartrecruiters.