Skip to content
Database ⇄ Human resources

Google Cloud SQL to Smartrecruiters integration — real-time, two-way sync

Keep Google Cloud SQL 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 Google Cloud SQL and Smartrecruiters

Put your workforce data where your apps can reach it: Google Cloud SQL 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. Google Cloud SQL is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Job Postings, Interviews, Offers, Users in Smartrecruiters need to exist as queryable Rows, Views, Transaction logs, Instances in Google Cloud SQL 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 Rows, Views, Transaction logs, Instances in Google Cloud SQL with Job Postings, Interviews, Offers, Users 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 Migrate from a self-managed database by syncing Cloud SQL and the legacy system during cutover.
  • 02 Keep an internal admin application backed by Cloud SQL consistent with an ERP or billing system.
  • 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

Computed and operational fields flow back

Values assembled or corrected in Google Cloud SQL write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.

Mirror people records into the database

Records maintained in Smartrecruiters land as queryable Rows, Views, Transaction logs, Instances in Google Cloud SQL, so internal apps and dashboards read live data instead of a periodic export.

One directory of record

When a person record is added, changed, or deactivated in either system, the matching row in the other stays current, ending dual maintenance.

What you can sync between Google Cloud SQL 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.

Google Cloud SQL objects Smartrecruiters objects How this pairing syncs
Schemas Namespace tables in PostgreSQL and SQL Server instances. 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). Schemas is specific to Google Cloud SQL and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.
Tables Mapped directly to sync targets; schema changes can be propagated. Interviews Interview types, timeslots, templates, and scheduled interviews with interviewers and times; created, updated, and read for scheduling and interviewer-load analytics. Tables is specific to Google Cloud SQL and Interviews to Smartrecruiters — each maps to any object or custom field on the other side.
Rows Read and written by primary key during each sync cycle. 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). Rows is specific to Google Cloud SQL and Offers to Smartrecruiters — each maps to any object or custom field on the other side.
Views Read-only sources for shaping data before syncing it out. 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 Google Cloud SQL and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Transaction logs MySQL binlog or PostgreSQL WAL, the source for log-based 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. Transaction logs is specific to Google Cloud SQL and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Instances The managed MySQL, PostgreSQL, or SQL Server server a sync connects to. 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. Instances is specific to Google Cloud SQL and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.

How changes propagate between Google Cloud SQL 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.

Google Cloud SQL Smartrecruiters Sub-second propagation

DetectionChanges in Google Cloud SQL are captured at the source via change data capture — no polling loop against its API. Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking.

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

Smartrecruiters Google Cloud SQL 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 Google Cloud SQL as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Google Cloud SQL: Constrained by instance size and connection limits rather than API quotas.
  • 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 Google Cloud SQL ⇄ Smartrecruiters

Connect Google Cloud SQL and Smartrecruiters for flexible, real-time data sync.

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Cloud SQL and Smartrecruiters.

How the Google Cloud SQL and Smartrecruiters connectors work

Google Cloud SQL

Integration surface
Native SQL wire protocols (MySQL, PostgreSQL, SQL Server) plus a REST admin API for instance management
Authentication
Database credentials; IAM database authentication is available for MySQL and PostgreSQL
Change detection
Engine-dependent log-based CDC: MySQL binlog, PostgreSQL logical replication, SQL Server change tracking; polling as a fallback
Capabilities
read · write · CDC
Rate limits
Constrained by instance size and connection limits rather than API quotas.

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 Google Cloud SQL 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 Google Cloud SQL 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
    Google Cloud SQL connected
    Smartrecruiters connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Cloud SQL 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 · Google Cloud SQL ⇄ 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
    Google Cloud SQL Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Google Cloud SQL 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 435 integrations available for Google Cloud SQL and Smartrecruiters.

Popular · 8 of 435
All Google Cloud SQL 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