Skip to content
Database ⇄ Human resources

Citus to Paylocity integration — real-time, two-way sync

Keep Citus and Paylocity 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 Citus and Paylocity

Put your workforce data where your apps can reach it: Citus and Paylocity share the same people, positions, and org structure in real time.

Paylocity is the system of record for the people side of the business — employees, candidates, roles, and the org structure around them. Citus is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) in Paylocity need to exist as queryable Distributed tables, Reference tables, Local tables, Schemas in Citus 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 Distributed tables, Reference tables, Local tables, Schemas in Citus with Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) in Paylocity field by field, in real time. You decide which system owns which fields — Paylocity 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 high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • 02 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.
  • 03 Push hired candidates from an ATS into Paylocity via the Onboarding endpoint, then read Onboarding Status to confirm the record before the first payroll run.
  • 04 Upsert recurring Deductions and Earnings on employee records when benefits or 401(k) elections change in a benefits admin system, without re-keying payroll setup.

Common sync patterns

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.

Reporting and analytics on current data

Employees, Onboarding, Deductions (Pay Setup), Earnings (Pay Setup) replicate into Citus where they join operational tables, so headcount, roles, and status reports run on the live state without manual pulls.

Org and structure stay aligned

Groups, departments, managers, and reporting lines from Paylocity stay consistent in Citus, so hierarchy-driven logic and permissions don't drift.

What you can sync between Citus and Paylocity

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.

Citus objects Paylocity objects How this pairing syncs
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Schemas is specific to Citus and Company Codes to Paylocity — each maps to any object or custom field on the other side.
Views Curated projections over distributed data, often used as read-only sync sources. Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Views is specific to Citus and Custom Fields to Paylocity — each maps to any object or custom field on the other side.
Sequences Key generators that matter when external writes must not collide with application inserts. Employees Core HR record keyed by companyId + employeeId; two-way via Create New Employee (POST) and Update Employee (PATCH), plus Get Employee / Get All Employees for reads. Sequences is specific to Citus and Employees to Paylocity — each maps to any object or custom field on the other side.
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Onboarding Create Employee Onboarding pushes new-hire data into Paylocity's onboarding workflow; Get Onboarding Status reads back partner onboarding progress. Write-in for hires from an ATS. Distributed tables is specific to Citus and Onboarding to Paylocity — each maps to any object or custom field on the other side.
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Deductions (Pay Setup) Recurring deduction codes at the employee level; two-way via Upsert Deduction and Delete, with Get Deduction / Get All Deductions for reads. Reference tables is specific to Citus and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Earnings (Pay Setup) Recurring earning codes at the employee level; two-way via Upsert Earning and Delete, with Get All Earnings and Get by earning code for reads. Local tables is specific to Citus and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side.

How changes propagate between Citus and Paylocity

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.

Citus Paylocity Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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

Paylocity Citus Sub-second propagation

DetectionPaylocity notifies Stacksync of record changes through webhook events. Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Paylocity: 25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
What ships with Citus ⇄ Paylocity

Connect Citus and Paylocity for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Citus or Paylocity instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Paylocity 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 Citus or Paylocity record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and Paylocity.

How the Citus and Paylocity connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

Paylocity

Integration surface
REST API (v1 and v2), JSON payloads
Authentication
OAuth 2.0 client credentials via the Paylocity Identity Provider (/IdentityServer/connect/token) with the WebLinkAPI scope; access tokens expire after one hour and API access must be enabled by Paylocity for the company
Change detection
Webhooks — Paylocity POSTs Employee New Hire, Employee Change, Termination, Payroll Processed, and Time Off Approval events to a callback URL; payloads carry only companyId and employeeId, so the receiver calls the relevant API to fetch changed values. Scheduled polling is used for objects without webhooks.
Capabilities
read · write · webhooks
Rate limits
25 requests per second (1,500 per minute); exceeding it returns HTTP 429. Every path is scoped to a Paylocity-assigned companyId (a company code, not a UUID).
How it works

How to connect Citus to Paylocity — 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 Citus and Paylocity 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
    Citus connected
    Paylocity connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Paylocity 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 · Citus ⇄ Paylocity
    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
    Citus Paylocity
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Paylocity 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 432 integrations available for Citus and Paylocity.

Popular · 7 of 432
All Citus integrations All Paylocity 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