Skip to content
Data warehouse ⇄ Human resources

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

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

Land the people and organization records from Smartrecruiters in Greenplum as live tables for workforce reporting, without extract jobs, and write computed results back where Smartrecruiters can use them.

Workforce data is some of the most requested data in the warehouse and some of the most awkward to move: the record types are many, the fields carry sensitive personal information, the APIs are strict, and hand-built extract jobs go stale or break quietly. Whether Smartrecruiters is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in Greenplum next to everything else the company measures.

Stacksync syncs Jobs, Job Postings, Interviews, Offers from Smartrecruiters into tables in Greenplum continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in Greenplum, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Smartrecruiters where the HR team acts on them. You configure which records and fields cross over, and in which direction, instead of maintaining pipeline code.

Common use cases

  • 01 Publish segments, scores, and aggregates computed in Greenplum back into business tools where teams act on them.
  • 02 Keep Greenplum and a cloud warehouse in sync during a migration so both platforms serve consistent data.
  • 03 Export Interviews and Offers to a data warehouse to analyze interviewer load, offer-acceptance rates, and hiring outcomes.
  • 04 Subscribe to the Webhooks API to react to new applications and status changes in near real time across downstream systems.

Common sync patterns

Fresh data instead of last night's load

Because changes stream continuously, reports query current workforce data rather than waiting for an overnight load window to finish.

Queryable history for planning and audit

A continuously synced copy in Greenplum gives you a durable, queryable record of how Smartrecruiters's records change over time, for headcount planning and audit questions.

Write-back of computed values

Segments, rollups, or risk flags computed in Greenplum sync back onto the matching records in Smartrecruiters, where the HR team sees them in the system they already use.

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

Greenplum objects Smartrecruiters objects How this pairing syncs
External tables Reference external files for bulk load paths alongside row-level syncs. Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. External tables is specific to Greenplum and Users to Smartrecruiters — each maps to any object or custom field on the other side.
Rows Read and written by key; distribution keys determine where rows live. Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. Rows is specific to Greenplum and Approvals to Smartrecruiters — each maps to any object or custom field on the other side.
Databases Top-level containers that scope a sync connection. 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. Databases is specific to Greenplum and Candidates to Smartrecruiters — each maps to any object or custom field on the other side.
Schemas Namespace tables and control which objects a sync can see. 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. Schemas is specific to Greenplum and Applications to Smartrecruiters — each maps to any object or custom field on the other side.
Tables Heap or append-optimized tables mapped directly to sync targets. 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. Tables is specific to Greenplum and Jobs to Smartrecruiters — each maps to any object or custom field on the other side.
Partitions Large tables are commonly partitioned by date, which shapes incremental reads. 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). Partitions is specific to Greenplum and Job Postings to Smartrecruiters — each maps to any object or custom field on the other side.

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

Greenplum Smartrecruiters Interval-based propagation

DetectionStacksync polls Greenplum for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key-based cursors.

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

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

Rate-limit considerations

  • Greenplum: Bounded by cluster resources and concurrency settings rather than an API quota.
  • 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 Greenplum ⇄ Smartrecruiters

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Greenplum and Smartrecruiters connectors work

Greenplum

Integration surface
PostgreSQL wire protocol (libpq), plus JDBC/ODBC drivers
Authentication
Database credentials
Change detection
Polling with timestamp or key-based cursors; Greenplum does not expose logical-decoding CDC
Capabilities
read · write
Rate limits
Bounded by cluster resources and concurrency settings rather than an API quota.

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

    Choose tables

    Pick the Greenplum 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 · Greenplum ⇄ 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
    Greenplum Smartrecruiters
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Greenplum 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.

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 438 integrations available for Greenplum and Smartrecruiters.

Popular · 7 of 438
Coworkers laughing in front of a laptop in a casual office setting

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