Real-time
Two-way sync
Changes in MongoDB or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
MongoDB to Smartrecruiters integration — real-time, two-way sync
Keep MongoDB 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 MongoDB and Smartrecruiters
Put your workforce data where your apps can reach it: MongoDB and Smartrecruiters share the same people, positions, and org structure in real time.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. MongoDB is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Interviews, Offers, Users, Approvals in Smartrecruiters need to exist as queryable GridFS files, Databases, Collections, Documents in MongoDB before an app can act on them. When that bridge is a nightly export or a hand-run CSV, every downstream system spends the day working from a roster that has already moved on.
Stacksync syncs GridFS files, Databases, Collections, Documents in MongoDB with Interviews, Offers, Users, Approvals in Smartrecruiters field by field, in real time. You decide which system owns which fields — Smartrecruiters typically owns identity and org attributes, while operational or computed values can flow back the other way — and Stacksync keeps every copy consistent, matching records on a stable key and resolving conflicts by rules you set.
The result is one live picture of the workforce on both sides: HR keeps its source of truth, and the database keeps a current mirror that internal apps, reports, and access controls can trust without a batch window in between.
Common use cases
- 01 Consolidate documents from multiple clusters or tenants into a single warehouse-facing store.
- 02 Sync MongoDB collections with a CRM so customer documents written by the application appear as CRM records, and CRM edits flow back as document updates.
- 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
Reporting and analytics on current data
Interviews, Offers, Users, Approvals replicate into MongoDB where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Org and structure stay aligned
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in MongoDB, so hierarchy-driven logic and permissions don't drift.
Computed and operational fields flow back
Values assembled or corrected in MongoDB write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
What you can sync between MongoDB 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.
| MongoDB objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Views Read-only aggregation-defined sources for filtered sync datasets. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Views is specific to MongoDB and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Change streams The oplog-backed event feed that powers real-time change capture. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Change streams is specific to MongoDB and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| GridFS files Chunked file storage whose metadata can be referenced by synced documents. | 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. | GridFS files is specific to MongoDB and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Databases Logical groupings of collections that scope a sync connection. | 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. | Databases is specific to MongoDB and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Collections The table-like sync unit; each collection maps to a table or object in the paired system. | 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. | Collections is specific to MongoDB and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Documents BSON records created, updated, and deleted during syncs, keyed by _id. | 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). | Documents is specific to MongoDB and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between MongoDB 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.
MongoDB Smartrecruiters Sub-second propagation
DetectionChanges in MongoDB are captured at the source via change data capture — no polling loop against its API. MongoDB oplog and change streams (requires the database to run as a replica set — even single-node).
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters MongoDB 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 applied to MongoDB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- 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 MongoDB ⇄ Smartrecruiters
Connect MongoDB and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every MongoDB–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever MongoDB 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 MongoDB or Smartrecruiters record.
Observability
Monitoring
Track your MongoDB ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between MongoDB and Smartrecruiters.
How the MongoDB and Smartrecruiters connectors work
MongoDB
- Integration surface
- MongoDB wire protocol via official drivers; Atlas additionally offers an administration REST API for cluster management
- Authentication
- Database credentials (username/password) or TLS/SSL X.509 certificate (.pem upload), entered individually or via a MongoDB connection string (SRV or standard); Stacksync IP allowlisting required
- Change detection
- MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time
- Capabilities
- read · write · CDC
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 MongoDB 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 MongoDB 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.
MongoDB
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the MongoDB 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 · MongoDB ⇄ 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.
MongoDB SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
MongoDB and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between MongoDB and Smartrecruiters: authenticate both systems, choose the objects to sync (such as MongoDB's Views and Change streams), 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 MongoDB and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom MongoDB–Smartrecruiters integration in-house.
-
Yes — Stacksync ships production-grade connectors for both MongoDB and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on MongoDB: MongoDB oplog and change streams (requires the database to run as a replica set — even single-node); Stacksync leverages these built-in tools to track changes in real time. 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 MongoDB side: GridFS files, Databases, Collections, Documents, plus custom fields where MongoDB 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.
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 540 integrations available for MongoDB and Smartrecruiters.
Popular · 8 of 540
-
MongoDB ⇄ Ceridian Dayforce -
MongoDB ⇄ D2l Brightspace -
MongoDB ⇄ Oracle Fusion Cloud HCM -
MongoDB ⇄ Ukg Pro -
Smartrecruiters ⇄ Apache Cassandra -
Smartrecruiters ⇄ Azure Cosmos DB -
Smartrecruiters ⇄ Azure SQL Database -
Smartrecruiters ⇄ Citus
No integrations match .
