Get company
Read selected company identity/name/status/industry metadata without address, phone or tax information.
Connector library
Paylocity connector.
Read selected company metadata, bounded cost center levels and job code references through four explicit Paylocity API Hub actions using managed OAuth bearer credentials.
Connector download
Download Paylocity
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.0 Choose version
- Release
- 2026-10-04
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- Environment
- Package size
- 12 KB
- SHA-256
4da74b03f003bfeea55c16dd2a326946e4df018fb989456b3a688497808bcd10
Version history
What's new
- v0.2.0.0Latest · 2026-10-04 · Implemented source
Four native API Hub GET reads replace the generic scaffold: selected company metadata, nested cost center references, one bounded job code page and exact job metadata using managed OAuth Bearer credentials.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical configurable HTTP scaffold without implemented vendor actions.
Included in this version
Included actions
Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.
List cost centers
Read bounded selected cost center levels and nested reference codes/names/flags.
List job codes
Read one bounded returned job code page with selected description and nullable flags.
Get job code
Read selected metadata for an exact company and job code.
Vendor API
API and access
Implementation considerations
- Company metadata: Read selected company ID/name/status/industry metadata without contact, address or tax details.
- Cost center references: Read checked levels and nested ID/code/name/active metadata under a combined local cap.
- Job code references: Read one bounded job code page or selected metadata for an exact company and job code.
- Caller-managed reference reads; no payroll synchronization or webhook trigger is included.
- Select sandbox or production to use the fixed Paylocity API Hub gateway. Use a managed bearer-token credential with an issued OAuth client-credentials access token. Registration, issuance/renewal and secret rotation remain external; WebLink uses different servers and is unsupported.
- Company and job codes are exact strings, preserving leading zeroes and case. Company IDs support nine letters/digits and job codes ten. The optional vendor testMode mock header is omitted.
- Maximum Cost Centers is a combined local cap, without server paging or truncation. Level IDs and per-level reference IDs/codes are checked for duplicates. Numeric identities retain exact decimal strings; nullable/empty text and false flags remain distinct.
- Job Page Limit/Row Offset map to the documented request. Returned pages and cost center levels do not establish complete coverage; caller owns pacing, consistency and iteration/completeness checks. Status/active/certified metadata does not establish operational, employment or financial readiness.
- No writes, employee/payroll/financial transactions, addresses/phone/tax data, pay rates, Time and Labor cost center API, arbitrary filters or token jobs are included. Hosted import, executor dependencies/BigInt support and live company/role/field/header/paging require validation.
- Four packaged API Hub reads use native OAuth Bearer credentials. Current vendor-owned collection examples establish the contract; live company/role/field/header/pagination behavior requires validation.
Related connectors
More in Enterprise, ERP & HR APIs
Support
Need help with Paylocity?
Tell us what you need to connect or change.