Skip to content
CRM ⇄ Human resources

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

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

Keep the people who own accounts in Close in step with the workforce records in Paylocity, so ownership, roles, and org structure stay current in both systems, in real time and in both directions.

Close runs on people as much as on accounts: every contact, deal, and account has an owner, and those owners are employees whose roles, teams, and status are held in Paylocity. Paylocity is the system of record for the workforce, from new hires to promotions to departures, and often for the candidates the business is still deciding on. When the two systems are connected only by re-keying or an overnight export, they drift apart, and the CRM ends up assigning accounts to people who have left, holding territories that no longer match the org chart, and waiting days to give a new rep access.

Stacksync syncs Contacts, Opportunities, Activities, Tasks in Close with Direct Deposit, Pay Statements, Company Codes, Custom Fields in Paylocity field by field, in real time, and in both directions. You decide which system owns which fields, so Paylocity stays authoritative on roles and org structure while Close keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.

Common use cases

  • 01 Push call, SMS, and email activity data into a warehouse for rep performance and outreach-cadence analysis.
  • 02 Write product usage or firmographic data from an internal database onto Close lead custom fields to prioritize follow-up.
  • 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 people

A person's name, title, email, phone, or manager corrected in either system updates the other, so both stop maintaining separate copies of the same individual.

Where Paylocity tracks people the business also engages: contacts stay in sync

A person recorded in Paylocity, such as a candidate or applicant, can create or update the matching contact in Close, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.

New team members provisioned when they are hired

When Paylocity records a new hire, a matching user or owner is created in Close, so a new rep can start working accounts without waiting on a manual setup ticket.

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

Close objects Paylocity objects How this pairing syncs
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. 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. Leads is specific to Close and Local and State Taxes to Paylocity — each maps to any object or custom field on the other side.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. 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. Contacts is specific to Close and Direct Deposit to Paylocity — each maps to any object or custom field on the other side.
Opportunities Deal records with value, confidence, and status; commonly synced to reporting and billing systems. 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. Opportunities is specific to Close and Pay Statements to Paylocity — each maps to any object or custom field on the other side.
Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. Activities is specific to Close and Company Codes to Paylocity — each maps to any object or custom field on the other side.
Tasks Follow-up items assigned to users; synced for workload and SLA reporting. 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. Tasks is specific to Close and Employees to Paylocity — each maps to any object or custom field on the other side.

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

Close Paylocity Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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

Paylocity Close 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 written to Close through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Close: Subject to per-endpoint rate limits communicated in response headers.
  • 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 Close ⇄ Paylocity

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Close and Paylocity connectors work

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers

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

    Choose tables

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

Close 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 529 integrations available for Close and Paylocity.

Popular · 8 of 529
All Close 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