Real-time
Two-way sync
Changes in Folk CRM or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Folk CRM to Smartrecruiters integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Smartrecruiters
Keep the people who own accounts in Folk CRM in step with the workforce records in Smartrecruiters, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.
Folk CRM runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Smartrecruiters. Smartrecruiters is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.
Stacksync syncs Groups, Custom fields, Notes, Reminders in Folk CRM with Job Postings, Interviews, Offers, Users in Smartrecruiters field by field, in real time, and in both directions. You decide which system owns which fields, so Smartrecruiters stays authoritative on roles and org structure while Folk CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 02 Keep folk and a billing or customer success tool aligned on company records as deals close.
- 03 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.
- 04 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.
Common sync patterns
Deactivate access when someone leaves
When Smartrecruiters marks a worker as departed, the matching user in Folk CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
One directory of people
A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.
Where Smartrecruiters tracks people the business also engages: contacts stay in sync
A person recorded in Smartrecruiters, such as a candidate or applicant, can create or update the matching contact in Folk CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
What you can sync between Folk CRM 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.
| Folk CRM objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | 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). | Groups is specific to Folk CRM and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Custom fields is specific to Folk CRM and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Notes is specific to Folk CRM and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | 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. | Reminders is specific to Folk CRM and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and kept aligned with billing or CS systems. | 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. | Companies is specific to Folk CRM and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Smartrecruiters Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate limits.
- 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 Folk CRM ⇄ Smartrecruiters
Connect Folk CRM and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Smartrecruiters record.
Observability
Monitoring
Track your Folk CRM ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Smartrecruiters.
How the Folk CRM and Smartrecruiters connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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 Folk CRM 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 Folk CRM 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.
Folk CRM
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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 · Folk CRM ⇄ 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.
Folk CRM SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Folk CRM's Groups and Custom fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. 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 Folk CRM side: Groups, Custom fields, Notes, Reminders, plus custom fields where Folk CRM exposes them. On the Smartrecruiters side: Job Postings, Interviews, Offers, Users. 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 Folk CRM and Smartrecruiters: Deactivate access when someone leaves; One directory of people; Where Smartrecruiters tracks people the business also engages: contacts stay in sync. When Smartrecruiters marks a worker as departed, the matching user in Folk CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
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 416 integrations available for Folk CRM and Smartrecruiters.
Popular · 7 of 416
-
Folk CRM ⇄ Greenhouse -
Folk CRM ⇄ Jobvite -
Folk CRM ⇄ Lever -
Smartrecruiters ⇄ Infor CRM -
Smartrecruiters ⇄ Insightly -
Smartrecruiters ⇄ Intercom -
Smartrecruiters ⇄ Kommo
No integrations match .
