Real-time
Two-way sync
Changes in Folk CRM or Paylocity instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Human resources
Folk CRM to Paylocity integration — real-time, two-way sync
Keep Folk CRM 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 Folk CRM and Paylocity
Keep the people who own accounts in Folk CRM 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.
Folk CRM 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 Companies, Groups, Custom fields, Notes in Folk CRM 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 Folk CRM keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
Common use cases
- 01 Push enriched contact data from a data warehouse into folk custom fields.
- 02 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 03 Read Pay Statements and Direct Deposit allocations into a Postgres or warehouse database for labor-cost, GL, and headcount reporting in SQL.
- 04 React to the Employee Change webhook to pull the updated Employee record and propagate title, location, or manager changes to downstream apps within minutes.
Common sync patterns
Deactivate access when someone leaves
When Paylocity marks a worker as departed, the matching user in Folk CRM is flagged or deactivated, so former employees do not keep CRM access after their last day.
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 Folk CRM, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
What you can sync between Folk CRM 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.
| Folk CRM objects | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | 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. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Groups is specific to Folk CRM and Company Codes to Paylocity — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for 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. | Notes is specific to Folk CRM and Employees to Paylocity — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | 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. | Reminders is specific to Folk CRM and Onboarding to Paylocity — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | 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. | People is specific to Folk CRM and Deductions (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and kept aligned with billing or CS systems. | 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. | Companies is specific to Folk CRM and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM 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.
Folk CRM Paylocity Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
Paylocity Folk CRM 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 Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate limits.
- 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 Folk CRM ⇄ Paylocity
Connect Folk CRM and Paylocity for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Paylocity connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM 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 Folk CRM or Paylocity record.
Observability
Monitoring
Track your Folk CRM ⇄ Paylocity sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Paylocity.
How the Folk CRM and Paylocity connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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 Folk CRM 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.
- 01
Connect your apps
Authenticate Folk CRM 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.
Folk CRM
connected
Paylocity
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM 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.
objects · Folk CRM ⇄ PaylocityCustomers 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.
Folk CRM PaylocityCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Paylocity integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Paylocity: authenticate both systems, choose the objects to sync (such as Folk CRM's Custom fields and Groups), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Folk CRM: Custom fields are defined per group, which means field mappings can differ across groups within the same workspace. Paylocity: Direct Deposit, Pay Statements, Company Codes, and Custom Fields are read-only through the API — bank and processed-payroll data can be pulled but not written. Stacksync's field mapping accounts for these differences between Folk CRM and Paylocity without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Folk CRM and Paylocity records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Folk CRM and Paylocity connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Folk CRM–Paylocity integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Paylocity. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Paylocity: 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. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 416 integrations available for Folk CRM and Paylocity.
Popular · 7 of 416
-
Folk CRM ⇄ Oracle Fusion Cloud HCM -
Folk CRM ⇄ Smartrecruiters -
Folk CRM ⇄ Ukg Pro -
Paylocity ⇄ Kustomer -
Paylocity ⇄ Nimble -
Paylocity ⇄ Nutshell -
Paylocity ⇄ Oracle CX Sales
No integrations match .
