Skip to content
Human resources ⇄ Database

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

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

Put your workforce data where your apps can reach it: Supabase 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. Supabase is where internal tools, dashboards, provisioning jobs, and analytics actually read and store records. The overlap is the workforce itself: Company Codes, Custom Fields, Employees, Onboarding in Paylocity need to exist as queryable Row Level Security Policies, JSONB Columns, Database Functions, Storage Object Metadata in Supabase 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 Row Level Security Policies, JSONB Columns, Database Functions, Storage Object Metadata in Supabase with Company Codes, Custom Fields, Employees, Onboarding 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 application tables in Supabase with the CRM two-way so new signups appear as contacts and sales edits flow back to the app
  • 02 Mirror billing and subscription records into Supabase tables the application can join directly
  • 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

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

Company Codes, Custom Fields, Employees, Onboarding replicate into Supabase 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 Supabase, so hierarchy-driven logic and permissions don't drift.

What you can sync between Paylocity and Supabase

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.

Paylocity objects Supabase objects How this pairing syncs
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. auth.users Managed authentication users, often mirrored into CRM or support systems. Local and State Taxes is specific to Paylocity and auth.users to Supabase — each maps to any object or custom field on the other side.
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. Row Level Security Policies Row-level access rules that govern what the REST layer exposes. Direct Deposit is specific to Paylocity and Row Level Security Policies to Supabase — each maps to any object or custom field on the other side.
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. JSONB Columns Semi-structured payloads such as event properties or nested objects. Pay Statements is specific to Paylocity and JSONB Columns to Supabase — each maps to any object or custom field on the other side.
Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Database Functions Postgres functions that can transform or validate synced rows. Company Codes is specific to Paylocity and Database Functions to Supabase — each maps to any object or custom field on the other side.
Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Storage Object Metadata File metadata rows that can be joined to synced application data. Custom Fields is specific to Paylocity and Storage Object Metadata to Supabase — each maps to any object or custom field on the other side.
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. Tables Standard Postgres tables; the primary two-way sync target. Employees is specific to Paylocity and Tables to Supabase — each maps to any object or custom field on the other side.

How changes propagate between Paylocity and Supabase

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.

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

Supabase Paylocity Sub-second propagation

DetectionSupabase pushes changes as they happen — webhook events backed by change data capture. Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime.

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

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).
  • Supabase: SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits.
What ships with Paylocity ⇄ Supabase

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Paylocity and Supabase connectors work

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

Supabase

Integration surface
Direct PostgreSQL wire protocol connection, plus an auto-generated REST API (PostgREST)
Authentication
Database credentials (connection string) for SQL access; API keys (anon / service role) for the REST layer
Change detection
Log-based CDC via Postgres logical replication, the same WAL feed that powers Supabase Realtime; database webhooks can also fire on row changes
Capabilities
read · write · CDC · webhooks
Rate limits
SQL access is bounded by connection limits (pooled connections are provided); the REST layer is subject to the platform's limits
How it works

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

    Choose tables

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

Paylocity and Supabase 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 Paylocity and Supabase.

Popular · 8 of 540
All Paylocity integrations All Supabase 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