Two-way sync
Changes in Intercom or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Keep Intercom 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.
Intercom 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 Segments, Admins & Teams, Articles, Contacts in Intercom with Custom Fields, Employees, Onboarding, Deductions (Pay Setup) 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 Intercom keeps ownership and territory current, and Stacksync resolves conflicts by the rules you set.
A person recorded in Paylocity, such as a candidate or applicant, can create or update the matching contact in Intercom, so relationship history and outreach are not rebuilt from scratch when the same individual appears in both.
When Paylocity records a new hire, a matching user or owner is created in Intercom, so a new rep can start working accounts without waiting on a manual setup ticket.
When a person changes team, manager, or region in Paylocity, their accounts and territory assignments in Intercom update to match, so pipeline stays with the right owner.
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.
| Intercom objects | Paylocity objects | How this pairing syncs | |
|---|---|---|---|
| Contacts A single contact model covers both users and leads, distinguished by a role attribute. | 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. | Contacts is specific to Intercom and Earnings (Pay Setup) to Paylocity — each maps to any object or custom field on the other side. | |
| Companies Company records group contacts and carry plan and account attributes used in segmentation. | 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. | Companies is specific to Intercom and Local and State Taxes to Paylocity — each maps to any object or custom field on the other side. | |
| Conversations Support and sales threads sync outward for analytics and CRM context. | 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. | Conversations is specific to Intercom and Direct Deposit to Paylocity — each maps to any object or custom field on the other side. | |
| Tickets Structured ticket records track issues alongside conversational threads. | 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. | Tickets is specific to Intercom and Pay Statements to Paylocity — each maps to any object or custom field on the other side. | |
| Data Events Behavioral events pushed in from product databases trigger messages and flows. | Company Codes Read-only reference codes and descriptions (cost centers, departments, positions) used to validate field mappings on employee writes. | Data Events is specific to Intercom and Company Codes to Paylocity — each maps to any object or custom field on the other side. | |
| Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Custom Fields Read-only company-specific custom fields returned by category, used to enrich the employee record downstream. | Custom Data Attributes is specific to Intercom and Custom Fields to Paylocity — each maps to any object or custom field on the other side. |
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.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Paylocity through its API, with automatic retries and rate-limit backoff.
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 Intercom through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Intercom–Paylocity connection.
Changes in Intercom or Paylocity instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Intercom or Paylocity data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Intercom or Paylocity record.
Track your Intercom ⇄ Paylocity sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Intercom and Paylocity.
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.
Authenticate Intercom 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.
Pick the Intercom 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Intercom and Paylocity: authenticate both systems, choose the objects to sync (such as Intercom's Contacts and Companies), map fields visually, and changes propagate both ways in milliseconds — no code required.
Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Paylocity: 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. Stacksync manages authentication, retries, and rate limits on both sides.
Intercom: Intercom's Contacts API unifies users and leads into one object with a role attribute, replacing the older separate users and leads endpoints. 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 Intercom 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 Intercom and Paylocity records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Intercom and Paylocity connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Intercom–Paylocity integration in-house.
Yes — Stacksync ships production-grade connectors for both Intercom and Paylocity. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 513 integrations available for Intercom and Paylocity.