Real-time
Two-way sync
Changes in Front or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Business productivity ⇄ Human resources
Front to Smartrecruiters integration — real-time, two-way sync
Keep Front 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.
- 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 Front and Smartrecruiters
Keep the people, teams, and status that Front and Smartrecruiters share aligned in real time, so a hire, role change, or departure recorded in one reaches the other within seconds.
Each tool in Front 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 Comments, Contacts, Accounts, Inboxes in Front with Offers, Users, Approvals, Candidates in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Front within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Front 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.
Common use cases
- 01 Write CRM account tier, owner, and renewal data into Front contact and account custom fields so it shows next to the conversation.
- 02 Keep Front contacts and accounts aligned with CRM contacts and accounts in both directions.
- 03 Two-way sync Candidates and Applications with Postgres so recruiting-ops apps read and update hiring status, tags, and custom fields in SQL while recruiters keep working in SmartRecruiters.
- 04 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
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 Smartrecruiters keep the groups, queues, or projects in Front assigned to the right people.
Where Front routes or assigns work by person: assignments follow the org
When someone changes teams or managers in Smartrecruiters, the queues, ownership, or approvals in Front update to match, so work reaches whoever holds the role now.
What you can sync between Front and Smartrecruiters
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.
| Front objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Comments Internal team notes on conversations; usually read-only in syncs. | 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). | Comments is specific to Front and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Contacts People across channels; matched to CRM contacts, with custom fields carrying external context. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Contacts is specific to Front and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Accounts Company groupings of contacts; kept aligned with CRM accounts. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Accounts is specific to Front and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Inboxes Shared queues that conversations live in; used to segment reporting by team or channel. | 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. | Inboxes is specific to Front and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tags Labels applied to conversations; drive routing and category-level analytics. | 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. | Tags is specific to Front and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Teammates Agents; used for ownership mapping and workload reporting. | 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. | Teammates is specific to Front and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Front and Smartrecruiters
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.
Front Smartrecruiters Sub-second propagation
DetectionFront notifies Stacksync of record changes through webhook events. Application webhooks and rule-triggered webhooks, with the events endpoint available for polling.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Front Sub-second propagation
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 Front through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Front: Request limits vary by plan.
- Smartrecruiters: Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
What ships with Front ⇄ Smartrecruiters
Connect Front and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Front–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Front or Smartrecruiters 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 Front or Smartrecruiters record.
Observability
Monitoring
Track your Front ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Front and Smartrecruiters.
How the Front and Smartrecruiters connectors work
Front
- Integration surface
- REST API (Core API)
- Authentication
- OAuth authorization via the Stacksync UI ("Connections" > "create new connection" > "Front" > "Authorize") — no coding required
- Change detection
- Application webhooks and rule-triggered webhooks, with the events endpoint available for polling
- Capabilities
- read · write · webhooks
- Rate limits
- Request limits vary by plan.
Smartrecruiters
- Integration surface
- 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
- Change detection
- 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.
- Capabilities
- read · write · webhooks
- Rate limits
- Per API credential: most endpoints allow up to 10 requests/sec (job publication and offer documents 2/sec), plus a concurrency limiter of up to 8 simultaneous requests (GET /candidates capped at 1). Exceeding returns 429; responses carry X-RateLimit-Limit/Remaining and concurrent-limit headers.
How it works
How to connect Front to Smartrecruiters — 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.
- 01
Connect your apps
Authenticate Front 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.
Front
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Front 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.
objects · Front ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Front SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Front and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Front and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Front's Comments and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Front and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Front–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Front and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Front: Application webhooks and rule-triggered webhooks, with the events endpoint available for polling. 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 Front side: Comments, Contacts, Accounts, Inboxes, plus custom fields where Front exposes them. On the Smartrecruiters side: Offers, Users, Approvals, Candidates. 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.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 489 integrations available for Front and Smartrecruiters.
Popular · 7 of 489
-
Front ⇄ Paylocity -
Front ⇄ Ukg Ready -
Front ⇄ Success Factors -
Smartrecruiters ⇄ Customer.io -
Smartrecruiters ⇄ eClinicalWorks -
Smartrecruiters ⇄ Full Enrich -
Smartrecruiters ⇄ Google Sheets
No integrations match .
