![]() |
VOOZH | about |
Gumloop is a visual automation platform designed to create AI-powered workflows by combining triggers, AI nodes, APIs, and data connectors. By integrating Gumloop with CData Connect AI through the built-in MCP (Model Context Protocol) Server, workflows can seamlessly access and interact with live Paylocity data.
The platform provides a low-code environment, making it easier to orchestrate complex processes without heavy development effort. Its flexibility allows integration across multiple business applications, enabling end-to-end automation with live data.
This article outlines the steps required to configure Paylocity connectivity in Connect AI, register the MCP server in Gumloop, and build a workflow that queries Paylocity data.
Connectivity to Paylocity from Gumloop is made possible through CData Connect AI's Remote MCP Server. To interact with Paylocity data from Gumloop, we start by creating and configuring a Paylocity connection in CData Connect AI.
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)
A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Gumloop. It is best practice to create a separate PAT for each service to maintain granularity of access.
With the Paylocity connection configured and a PAT generated, Gumloop is prepared to connect to Paylocity data through the CData MCP server.
The MCP server endpoint and authentication values from Connect AI must be added to Gumloop credentials.
The MCP server is now available to build workflows in Gumloop.
With the workflow run completed, Gumloop demonstrates successful retrieval of Paylocity data through the CData Connect AI MCP server, with the MCP Client node providing the ability to ask questions, retrieve records, and perform actions on the data.
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!
Learn more about CData Connect AI or sign up for free trial access:
Free Trial