Two-way sync
Changes in Firebase or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Firebase 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.
Smartrecruiters is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Firebase is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Candidates, Applications, Jobs, Job Postings in Smartrecruiters need to exist as queryable Cloud Storage Objects, Cloud Functions Triggers, Firestore Collections, Firestore Documents in Firebase 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 Cloud Storage Objects, Cloud Functions Triggers, Firestore Collections, Firestore Documents in Firebase with Candidates, Applications, Jobs, Job Postings 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.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
Candidates, Applications, Jobs, Job Postings replicate into Firebase where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.
Groups, departments, managers, and reporting lines from Smartrecruiters stay consistent in Firebase, so hierarchy-driven logic and permissions don't drift.
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.
| Firebase objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Cloud Functions Triggers Server-side hooks that fire on document changes and can push updates outward. | 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. | Cloud Functions Triggers is specific to Firebase and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Firestore Collections Top-level groupings of documents that a sync maps to tables or SaaS objects. | 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. | Firestore Collections is specific to Firebase and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Firestore Documents Schemaless JSON-like records, the primary unit synced to and from external systems. | 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). | Firestore Documents is specific to Firebase and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Subcollections Nested collections under documents, typically flattened into related tables during sync. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Subcollections is specific to Firebase and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Realtime Database Nodes JSON tree paths in the older Realtime Database, synced by path. | 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). | Realtime Database Nodes is specific to Firebase and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Authentication Users User accounts read into CRMs and warehouses for customer records. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Authentication Users is specific to Firebase and Users 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.
DetectionStacksync polls Firebase for changes on an incremental schedule, reading only records changed since the previous pass. Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes.
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 Firebase through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Firebase–Smartrecruiters connection.
Changes in Firebase or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Firebase 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 Firebase or Smartrecruiters record.
Track your Firebase ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Firebase 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 Firebase 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 Firebase 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 Firebase and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Firebase's Cloud Functions Triggers and Firestore Collections), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Firebase and Smartrecruiters records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Firebase and Smartrecruiters connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Firebase–Smartrecruiters integration in-house.
Yes — Stacksync ships production-grade connectors for both Firebase and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Firebase: Real-time snapshot listeners on Firestore queries and Cloud Functions triggers on document changes. 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 Firebase side: Cloud Storage Objects, Cloud Functions Triggers, Firestore Collections, Firestore Documents, plus custom fields where Firebase exposes them. On the Smartrecruiters side: Candidates, Applications, Jobs, Job Postings. Stacksync auto-detects both schemas and converts types between the two systems.
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 532 integrations available for Firebase and Smartrecruiters.