Two-way sync
Changes in Airtable or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Keep Airtable 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. Airtable 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 Linked records, Attachments, Collaborators, Bases in Airtable 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 Linked records, Attachments, Collaborators, Bases in Airtable 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.
Values assembled or corrected in Airtable write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
Records maintained in Smartrecruiters land as queryable Linked records, Attachments, Collaborators, Bases in Airtable, so internal apps and dashboards read live data instead of a periodic export.
When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.
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.
| Airtable objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Collaborators User fields useful for mapping record ownership to accounts in a CRM or database. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Collaborators is specific to Airtable and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Bases Top-level containers; each base has its own API endpoint and schema. | 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. | Bases is specific to Airtable and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Tables Map to sync tables; schema is readable through the base metadata endpoints. | 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. | Tables is specific to Airtable and Applications to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Records The row-level unit created, updated, and deleted during syncs, identified by rec-prefixed IDs. | 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. | Records is specific to Airtable and Jobs to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. | 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). | Fields is specific to Airtable and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Filtered subsets of a table that can scope which records a sync reads. | Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. | Views is specific to Airtable and Interviews 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.
DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).
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 Airtable through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Airtable–Smartrecruiters connection.
Changes in Airtable or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Airtable 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 Airtable or Smartrecruiters record.
Track your Airtable ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Airtable 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 Airtable 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 Airtable 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 Airtable and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Airtable's Collaborators and Bases), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Airtable and Smartrecruiters. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Airtable: Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour. 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 Airtable side: Linked records, Attachments, Collaborators, Bases, plus custom fields where Airtable 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.
Common patterns for Airtable and Smartrecruiters: Computed and operational fields flow back; Mirror people records into the database; One directory of record. Values assembled or corrected in Airtable write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
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 541 integrations available for Airtable and Smartrecruiters.