![]() |
VOOZH | about |
Jitterbit is an enterprise iPaaS (integration platform as a service) that lets you streamline your data workflows. When paired with CData Connect AI, Jitterbit gets access to live Paylocity data. This article demonstrates how to connect to Paylocity using Connect AI and integrate with live Paylocity data in Jitterbit.
CData Connect AI provides a pure OData interface for Paylocity, allowing you to query data from Paylocity without replicating the data to a natively supported database. Using optimized data processing out of the box, CData Connect AI pushes all supported SQL operations (filters, JOINs, etc.) directly to Paylocity, leveraging server-side processing to return the requested Paylocity data quickly.
To work with Paylocity data from Jitterbit, we need to connect to Paylocity from Connect AI, provide user access to the connection, and create a Workspace for the Paylocity data.
CData Connect AI uses a straightforward, point-and-click interface to connect to data sources.
Set the following to establish a connection to Paylocity:
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
Paylocity will decrypt the AES key using RSA decryption.
It is an optional property if the IV value not provided, The driver will generate a key internally.
You must use OAuth to authenticate with Paylocity. OAuth requires the authenticating user to interact with Paylocity using the browser. For more information, refer to the OAuth section in the Help documentation.
The Pay Entry API is completely separate from the rest of the Paylocity API. It uses a separate Client ID and Secret, and must be explicitly requested from Paylocity for access to be granted for an account. The Pay Entry API allows you to automatically submit payroll information for individual employees, and little else. Due to the extremely limited nature of what is offered by the Pay Entry API, we have elected not to give it a separate schema, but it may be enabled via the UsePayEntryAPI connection property.
Please be aware that when setting UsePayEntryAPI to true, you may only use the CreatePayEntryImportBatch & MergePayEntryImportBatchgtable stored procedures, the
InputTimeEntry table, and the OAuth stored procedures. Attempts to use other features of the product will result in an error. You must also store your OAuthAccessToken
separately, which often means setting a different OAuthSettingsLocation when using this connection property.
π Configuring a connection (Salesforce is shown)
When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.
After connecting to Paylocity, create a workspace for your desired table(s).
With the connection, PAT, and Workspace configured, you are ready to connect to Paylocity data from Jitterbit.
To establish a connection from Jitterbit to CData Connect AI using the OData protocol, follow these steps.
You can now transform and integrate live Paylocity data in Jitterbit.
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Jitterbit, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial