Real-time
Two-way sync
Changes in Postgres Heroku or Smartrecruiters instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ Human resources
Postgres Heroku to Smartrecruiters integration — real-time, two-way sync
Keep Postgres Heroku 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 Postgres Heroku and Smartrecruiters
Put your workforce data where your apps can reach it: Postgres Heroku 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. Postgres Heroku is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Jobs, Job Postings, Interviews, Offers in Smartrecruiters need to exist as queryable Schemas, Primary and Unique Keys, JSONB Columns, Sequences in Postgres Heroku 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 Schemas, Primary and Unique Keys, JSONB Columns, Sequences in Postgres Heroku with Jobs, Job Postings, Interviews, Offers 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 Sync Heroku Postgres into a warehouse for reporting without running ETL dynos
- 02 Keep several Heroku app databases aligned with one system of record
- 03 Write enriched or sourced Candidates from external sourcing tools into SmartRecruiters and keep contact fields refreshed as data changes.
- 04 Stream Jobs and Job Postings into a reporting database for requisition, funnel, and time-to-fill dashboards.
Common sync patterns
Computed and operational fields flow back
Values assembled or corrected in Postgres Heroku 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 Schemas, Primary and Unique Keys, JSONB Columns, Sequences in Postgres Heroku, 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 Postgres Heroku 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.
| Postgres Heroku objects | Smartrecruiters objects | How this pairing syncs | |
|---|---|---|---|
| Tables Standard Postgres tables; the primary two-way sync target for app data. | 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 Postgres Heroku and Interviews to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Views Read-side projections exposed to outbound syncs. | 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). | Views is specific to Postgres Heroku and Offers to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Materialized Views Precomputed result sets synced outward on refresh. | Users Company users (recruiters, hiring managers) with roles, access groups, and activation state; read and written via the User Management API. | Materialized Views is specific to Postgres Heroku and Users to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Schemas Namespaces that scope which tables a sync reads and writes. | Approvals Approval requests for jobs and offers; requests can be created, retrieved as pending, commented on, and approved or rejected via the Approvals API. | Schemas is specific to Postgres Heroku and Approvals to Smartrecruiters — each maps to any object or custom field on the other side. | |
| Primary and Unique Keys Match keys for idempotent upserts from connected systems. | 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. | Primary and Unique Keys is specific to Postgres Heroku and Candidates to Smartrecruiters — each maps to any object or custom field on the other side. | |
| JSONB Columns Semi-structured payloads for nested SaaS objects and metadata. | 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. | JSONB Columns is specific to Postgres Heroku and Applications to Smartrecruiters — each maps to any object or custom field on the other side. |
How changes propagate between Postgres Heroku 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.
Postgres Heroku Smartrecruiters Interval-based propagation
DetectionStacksync polls Postgres Heroku for changes on an incremental schedule, reading only records changed since the previous pass. Trigger-based capture or polling in most configurations.
DeliveryEach detected change is written to Smartrecruiters through its API, with automatic retries and rate-limit backoff.
Smartrecruiters Postgres Heroku 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 Postgres Heroku as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Postgres Heroku: No API rate limits; connection counts and performance are bounded by the Heroku Postgres plan.
- 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 Postgres Heroku ⇄ Smartrecruiters
Connect Postgres Heroku and Smartrecruiters for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Postgres Heroku–Smartrecruiters connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Postgres Heroku 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 Postgres Heroku or Smartrecruiters record.
Observability
Monitoring
Track your Postgres Heroku ⇄ Smartrecruiters sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Postgres Heroku and Smartrecruiters.
How the Postgres Heroku and Smartrecruiters connectors work
Postgres Heroku
- Integration surface
- SQL wire protocol (standard PostgreSQL)
- Authentication
- Database credentials from the Heroku DATABASE_URL config var; SSL required
- Change detection
- Trigger-based capture or polling in most configurations; log-based logical replication availability depends on plan and Heroku's managed server settings
- Capabilities
- read · write
- Rate limits
- No API rate limits; connection counts and performance are bounded by the Heroku Postgres plan
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.
How it works
How to connect Postgres Heroku 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.
- 01
Connect your apps
Authenticate Postgres Heroku 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.
Postgres Heroku
connected
Smartrecruiters
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Postgres Heroku 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.
objects · Postgres Heroku ⇄ SmartrecruitersCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Postgres Heroku SmartrecruitersCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Postgres Heroku and Smartrecruiters integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Postgres Heroku and Smartrecruiters: authenticate both systems, choose the objects to sync (such as Postgres Heroku's Tables and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Postgres Heroku side: Schemas, Primary and Unique Keys, JSONB Columns, Sequences, plus custom fields where Postgres Heroku exposes them. On the Smartrecruiters side: Jobs, Job Postings, Interviews, Offers. 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 Postgres Heroku and Smartrecruiters: Computed and operational fields flow back; Mirror people records into the database; One directory of record. Values assembled or corrected in Postgres Heroku write onto the matching record in Smartrecruiters where those fields are writable, keeping the people system enriched.
-
Postgres Heroku: SQL wire protocol (standard PostgreSQL). Authentication: Database credentials from the Heroku DATABASE_URL config var; SSL required. Smartrecruiters: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Postgres Heroku: All connections require SSL, and server-level settings such as replication configuration are controlled by Heroku rather than the user. Smartrecruiters: Change tracking uses the Webhooks API (event subscriptions with a signing secret and callback logs) plus updated-after-style polling; there is no log-based change data capture. Stacksync's field mapping accounts for these differences between Postgres Heroku and Smartrecruiters without custom code.
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 448 integrations available for Postgres Heroku and Smartrecruiters.
Popular · 7 of 448
-
Postgres Heroku ⇄ Greenhouse -
Postgres Heroku ⇄ Jobvite -
Postgres Heroku ⇄ Lever -
Smartrecruiters ⇄ MySQL -
Smartrecruiters ⇄ MariaDB -
Smartrecruiters ⇄ SQL Server -
Smartrecruiters ⇄ Airtable
No integrations match .
