Skip to content
Business productivity ⇄ Human resources

Notion to Smartrecruiters integration — real-time, two-way sync

Keep Notion 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 Notion and Smartrecruiters

Keep the people, teams, and status that Notion 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 Notion 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 Pages, Databases / Data sources, Properties, Blocks in Notion with Job Postings, Interviews, Offers, Users in Smartrecruiters bi-directionally and in real time. A person added, moved, or offboarded in Smartrecruiters creates or updates the matching user in Notion within seconds, with field-level mapping and conflict resolution in place of spreadsheets and one-off account changes. Where Notion 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 Two-way sync a Notion projects or tasks data source with a Postgres table so engineers work in SQL while the team edits Pages in Notion, mapping status, date, and assignee properties both ways.
  • 02 Push rows from a warehouse or another database into a Notion data source as Pages so ops and leadership read live metrics in a familiar Notion view.
  • 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

Org and team structure kept current

Department, team, and reporting-line changes from Smartrecruiters keep the groups, queues, or projects in Notion assigned to the right people.

Where Notion routes or assigns work by person: assignments follow the org

When someone changes teams or managers in Smartrecruiters, the queues, ownership, or approvals in Notion update to match, so work reaches whoever holds the role now.

Onboarding: access ready on day one

A new hire recorded in Smartrecruiters creates the matching user in Notion with the right team and manager already set, so people can start working without waiting on a provisioning ticket.

What you can sync between Notion 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.

Notion objects Smartrecruiters objects How this pairing syncs
Users Workspace members and bots referenced by people properties; read-only — users cannot be created or invited through the API. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Databases / Data sources Collections of pages with a typed property schema. Since the 2025-09-03 API a database is a container holding one or more data sources; syncs target a specific data_source_id. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Databases / Data sources is specific to Notion and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Properties Typed columns on a page — title, rich_text, number, select, multi_select, date, people, relation, status, checkbox, URL. Read and written both ways. 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). Properties is specific to Notion and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Blocks The page body — paragraphs, headings, to-dos, tables — nested as children and fetched recursively, separate from a page's properties. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Blocks is specific to Notion and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Formula and Rollup properties Values computed by Notion from other fields; read-only, so they are pulled out for reporting but never written back. 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. Formula and Rollup properties is specific to Notion and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
Comments Page and inline discussion threads; can be read and created, useful for surfacing Notion activity in another system. 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. Comments is specific to Notion and Applications to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between Notion 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.

Notion Smartrecruiters Sub-second propagation

DetectionNotion notifies Stacksync of record changes through webhook events. Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created.

DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.

Smartrecruiters Notion 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 Notion through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Notion: Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.
  • 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 Notion ⇄ Smartrecruiters

Connect Notion and Smartrecruiters for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Notion–Smartrecruiters connection.

Real-time

Two-way sync

Changes in Notion or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Notion 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 Notion or Smartrecruiters record.

Observability

Monitoring

Track your Notion ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Notion and Smartrecruiters.

How the Notion and Smartrecruiters connectors work

Notion

Integration surface
REST API (api.notion.com/v1)
Authentication
OAuth 2.0 for public integrations, or an internal integration secret (bearer token); every request must send a Notion-Version header
Change detection
Workspace webhooks (page.created, page.content_updated, data_source.schema_updated, comment.created; HMAC-SHA256 signed) plus polling on each page's last_edited_time
Capabilities
read · write · webhooks
Rate limits
Average of ~3 requests/second per integration with some bursts; 429 with a Retry-After header when exceeded. Payloads capped at 500 KB and 1000 block elements.

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.
Smartrecruiters setup guide
How it works

How to connect Notion 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.

  1. 01

    Connect your apps

    Authenticate Notion 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Notion connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Notion 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Notion ⇄ Smartrecruiters
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Notion Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Notion and Smartrecruiters integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 511 integrations available for Notion and Smartrecruiters.

Popular · 8 of 511
All Notion integrations All Smartrecruiters integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own