Two-way sync
Changes in Smartrecruiters or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Keep Smartrecruiters and Sysaid 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 Sysaid 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 Service Requests, Problems, Changes, Users in Sysaid with Applications, Jobs, Job Postings, Interviews in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Sysaid within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Sysaid 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 Sysaid 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 Sysaid 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.
| Smartrecruiters objects | Sysaid objects | How this pairing syncs | |
|---|---|---|---|
| Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Companies Customer and department organizations that scope tickets and users; mapped to Accounts in a CRM or org tables in a database. | Interviews is specific to Smartrecruiters and Companies to Sysaid — each maps to any object or custom field on the other side. | |
| 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). | Custom Fields Org-specific fields on service records, discoverable through the API so mappings can be generated without hardcoding names. | Offers is specific to Smartrecruiters and Custom Fields to Sysaid — each maps to any object or custom field on the other side. | |
| Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Incidents Break/fix tickets under /api/v1/sr with type=incident; created and updated two-way with status, priority, assignee, category, and SLA fields. | Approvals is specific to Smartrecruiters and Incidents to Sysaid — each maps to any object or custom field on the other side. | |
| Candidates Person records with contact details, tags, attachments, custom properties, and consent; created, updated, and searched via the Candidates API, often populated from sourcing or enrichment pipelines. | Service Requests Catalog and help-desk requests on the same /sr endpoint (type=request); written or read so fulfillment can be driven from another system. | Candidates is specific to Smartrecruiters and Service Requests to Sysaid — each maps to any object or custom field on the other side. | |
| 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. | Problems Root-cause records that group related incidents; read and written to keep problem management aligned with an external ITSM or reporting store. | Applications is specific to Smartrecruiters and Problems to Sysaid — 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.
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 Sysaid through its API, with automatic retries and rate-limit backoff.
DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartrecruiters–Sysaid connection.
Changes in Smartrecruiters or Sysaid instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Smartrecruiters or Sysaid data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Smartrecruiters or Sysaid record.
Track your Smartrecruiters ⇄ Sysaid sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Smartrecruiters and Sysaid.
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 Smartrecruiters and Sysaid 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 Smartrecruiters and Sysaid 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 Smartrecruiters and Sysaid: authenticate both systems, choose the objects to sync (such as Smartrecruiters's Users and Interviews), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Smartrecruiters and Sysaid. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection 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. On Sysaid: Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature; otherwise poll the /sr endpoint filtering on update_time.gte. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Sysaid side: Service Requests, Problems, Changes, Users, plus custom fields where Sysaid exposes them. On the Smartrecruiters side: Applications, Jobs, Job Postings, Interviews. 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 Smartrecruiters and Sysaid: 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 Sysaid is deactivated or flagged, so departures do not leave open access behind.
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 511 integrations available for Smartrecruiters and Sysaid.