Skip to content
Data warehouse ⇄ Human resources

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

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

Land the people and organization records from Paylocity in ClickHouse as live tables for workforce reporting, without extract jobs, and write computed results back where Paylocity 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 Paylocity is the system of record for employees and payroll, for candidates and applications, or for learners and course completions, the reporting belongs in ClickHouse next to everything else the company measures.

Stacksync syncs Direct Deposit, Pay Statements, Company Codes, Custom Fields from Paylocity into tables in ClickHouse continuously, handling API limits and schema drift as they come. The connection is bi-directional, so values computed in ClickHouse, such as headcount rollups, cost allocations, or attrition risk flags, can be written back to fields in Paylocity 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 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.
  • 02 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 03 Two-way sync of Employees between Paylocity and an HRIS or identity provider so new hires, terminations, and demographic edits flow both directions.
  • 04 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.

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 ClickHouse gives you a durable, queryable record of how Paylocity's records change over time, for headcount planning and audit questions.

Write-back of computed values

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

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

ClickHouse objects Paylocity objects How this pairing syncs
Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. 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. Dictionaries is specific to ClickHouse and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side.
Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. 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. Tables (MergeTree family) is specific to ClickHouse and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side.
Databases Namespaces that group tables and scope permissions for sync users. Local and State Taxes Two-way via Create/Update/Delete Local Tax and Upsert Primary / Non-Primary State Tax; Get by tax code and Get All for reads. Databases is specific to ClickHouse and Local and State Taxes to Paylocity — each maps to any object or custom field on the other side.
Views Saved queries used as curated, read-only sync sources. Direct Deposit Read-only: Get All Direct Deposit and Get Employee Bank Accounts return main and additional allocations. Bank details cannot be written through the API. Views is specific to ClickHouse and Direct Deposit to Paylocity — each maps to any object or custom field on the other side.
Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Pay Statements Read-only detailed payroll statement data — earnings, deductions, taxes, and direct deposit allocations by year, check date, or date range. Pulled for reporting, never written. Materialized views is specific to ClickHouse and Pay Statements to Paylocity — each maps to any object or custom field on the other side.
Distributed tables Query-routing tables over cluster shards in self-managed deployments. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Distributed tables is specific to ClickHouse and Company Codes to Paylocity — each maps to any object or custom field on the other side.

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

ClickHouse Paylocity Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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

Paylocity ClickHouse 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 ClickHouse 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 ClickHouse ⇄ Paylocity

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the ClickHouse and Paylocity connectors work

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write

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

    Choose tables

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

ClickHouse 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 540 integrations available for ClickHouse and Paylocity.

Popular · 8 of 540
All ClickHouse 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