![]() |
VOOZH | about |
Through standards-based interfaces like OData and Swagger, the CData API Server provides a native experience in Logic Apps and Power Automate with Workday. OData enables real-time connectivity to data; Swagger enables scaffolding, or code generation, of wizards in Logic Apps and Power Automate, as well as scaffolding Power Apps. This article shows how to add Workday to an IFTTT (if-this-then-that) workflow in a Logic App.
CData provides the easiest way to access and integrate live data from Workday. Customers use CData connectivity to:
Users frequently integrate Workday with analytics tools such as Tableau, Power BI, and Excel, and leverage our tools to replicate Workday data to databases or data warehouses. Access is secured at the user level, based on the authenticated user's identity and role.
For more information on configuring Workday to work with CData, refer to our Knowledge Base articles: Comprehensive Workday Connectivity through Workday WQL and Reports-as-a-Service & Workday + CData: Connection & Integration Best Practices.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Workday OData services:
To work with Workday data in a Logic App, we start by creating and configuring a Workday connection. Follow the steps below to configure the API Server to connect to Workday data:
To connect to Workday, users need to find the Tenant and BaseURL and then select their API type.
To obtain the BaseURL and Tenant properties, log into Workday and search for "View API Clients." On this screen, you'll find the Workday REST API Endpoint, a URL that includes both the BaseURL and Tenant.
The format of the REST API Endpoint is: https://domain.com/subdirectories/mycompany, where:
The value you use for the ConnectionType property determines which Workday API you use. See our Community Article for more information on Workday connectivity options and best practices.
| API | ConnectionType Value |
|---|---|
| WQL | WQL |
| Reports as a Service | Reports |
| REST | REST |
| SOAP | SOAP |
Your method of authentication depends on which API you are using.
See the Help documentation for more information on configuring OAuth with Workday.
π Connecting to a datasource (SQLite is shown)Next, create a user to access your Workday data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the Workday tables:
Having configured a connection to Workday data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsYou can use the API Server in a Logic App to create process flows around Workday data. The HTTP + Swagger action provides a wizard to define the operations you want to execute to Workday. The following steps below show how to retrieve Workday data in a Logic App.
If your table has a column containing the creation date of a record, you can follow the steps below to write a function to check the column values for any new records. Otherwise, skip to the Create a Logic App section to send out emails to entities that match a filter.
To find new Workday entities since a certain time, you can write a function that retrieves a datetime value for the start of the interval:
module.exports = function (context, data) {
var d = new Date();
d.setHours(d.getHours()-1);
// Response of the function to be used later.
context.res = {
body: {
start: d
}
};
context.done();
};
Follow the steps below to create a trigger that searches Workday for results that match a filter. If you created the function above, you can search for objects that were created after the start of the interval returned.
http://MySite:MyPort/api.rsc/@MyAuthtoken/$oas
Use the descriptions for each property to specify additional parameters such as the columns to retrieve, filters, etc. Below is an example filter:
Legal_Name_Last_Name eq 'Morgan'
The API Server returns the descriptions and other documentation in the swagger document. You can find more information on using the OData API and supported OData in the API Server help documentation.
To use the datetime value returned from the getInterval function, use the "ge" operator with a datetime column in the Workers table and select the Body parameter in the dialog. Note that quotes must be used to surround the datetime value.
π An OData filter on the results of an Azure Function App, getToday. (Salesforce is shown.)Switch to Code View and modify the $filter expression to extract the property containing the start of the interval. Use the syntax '@{body('MyFunc')['MyProp']'.
"getAllAccount": {
"inputs": {
"method": "get",
"queries": {
"$filter": "CreatedDate ge '@{body('getInterval')['start']}'"
},
"uri": "https://MySite:MyPort/api.rsc/@MyAuthtoken/Workers"
}
You can now access Workday as data sources and destinations in your workflows.
Follow the steps below to email a report with any new Workers entities.
Click Save and then click Run to send email notifications on any Workday records created in the last hour.
π Dynamic columns added to template the body of an email. (Salesforce is shown.)Learn more or sign up for a free trial:
CData API Server