Integrating Gumloop with Paylocity Data via CData Connect AI
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.
Step 1: Configure Paylocity Connectivity for Gumloop
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.
- Log into Connect AI, click Sources, and then click Add Connection
- Select "Paylocity" from the Add Connection panel
-
Enter the necessary authentication properties to connect to Paylocity.
Set the following to establish a connection to Paylocity:
- RSAPublicKey: Set this to the RSA Key associated with your Paylocity, if the RSA Encryption is enabled in the Paylocity account.
This property is required for executing Insert and Update statements, and it is not required if the feature is disabled.
- UseSandbox: Set to true if you are using sandbox account.
- CustomFieldsCategory: Set this to the Customfields category. This is required when IncludeCustomFields is set to true. The default value for this property is PayrollAndHR.
- Key: The AES symmetric key(base 64 encoded) encrypted with the Paylocity Public Key. It is the key used to encrypt the content.
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. - IV: The AES IV (base 64 encoded) used when encrypting the content. It is an optional property if the Key value not provided, The driver will generate an IV internally.
Connect Using OAuth Authentication
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
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.
- RSAPublicKey: Set this to the RSA Key associated with your Paylocity, if the RSA Encryption is enabled in the Paylocity account.
- Click Save & Test
-
Navigate to the Permissions tab in the Add Paylocity Connection page and update the User-based permissions.
Add a Personal Access Token
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.
- Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
With the Paylocity connection configured and a PAT generated, Gumloop is prepared to connect to Paylocity data through the CData MCP server.
Step 2: Connect to the MCP server in Gumloop
The MCP server endpoint and authentication values from Connect AI must be added to Gumloop credentials.
- Sign in to Gumloop and create an account
- Visit the Gumloop Credentials page to configure MCP server
- Click on Add Credentials and search and select MCP Server
- Provide the following details:
- URL: https://mcp.cloud.cdata.com/mcp
- Label: A descriptive name such as Paylocity-mcp-server
- Access Token / API Key: leave blank
- Additional Header: Authorization: Basic YOUR EMAIL:YOUR PAT
- Save the credentials
The MCP server is now available to build workflows in Gumloop.
Step 3: Build a workflow and explore live Paylocity data with Gumloop
- Visit Gumloop Personal workspace and click on the Create Flow
- Select the icon or press Ctrl + B to add a node or a subflow
- Search for Ask AI and select it
- Click Show More Options and enable the Connect MCP Server? option
- From the MCP Servers dropdown, choose the saved MCP credential
- Add a Prompt and Choose an AI Model according to your requirements
- After configuring the required details, Click Run to run the pipeline
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.
Get CData Connect AI
To get live data access to 300+ SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!