Workday Connector Reference | MuleSoft Documentation
# Workday Connector Reference
Use Workday as a data source or data target. Some details of how to work with data in a flow are specific to the data source or data target, and to the specific trigger or actions you choose.
## Connections
To connect to a system, whether it is a source of data or the target where you are sending data, you must create a connection with that system’s required credentials. You typically connect to different systems within a flow and can reuse each connection every time you need to connect.
This system requires the following credential information for its connections: 

Connection Name
    
Enter a connection name that will help you remember the details of this connection. You can reuse connections multiple times in a single flow, and in more than one flow, and the credentials are hidden after you create the connection. Therefore, it’s helpful to provide a name that easily identifies this connection from others.
Only you can see the connection. Other users in your Composer app must create their own connections.
To validate and test connectivity, Workday Connector uses a `Performance_Management` service with the `Get_Degrees` operation. You must ensure that your service account has the required permissions to operate on that service:
Security Policy | Domain/Functional Areas | Permitted Security Groups  
---|---|---  
Set Up: Skills and Experience | Worker Profile and Skills | 
  * HR Administrator
  * HR System
  * Implementers
  * Job and Position Administrator
  * Learning Management System

  
Implementation | Implementers  
Special OX Web Services | Implementation 

Tenant Name
      
The name or ID of your Workday tenant.
For example, if the URL where you log into Workday is `na.workday.com/wday/authgwy/global-modern/`, then your tenant name is `global-modern`.
To obtain the tenant name from the sandbox:
  1. View the upper left corner of the page, in which the tenant details are displayed in the format `Sandbox Type - Tenant Name`.



User Name
    
The username that you use to log in to Workday. 

Password
    
The password that you use to log in to Workday. 

Host Name
    
The host name of your Workday instance. For example, `wd2-impl-services1.workday.com`.
To find your host name:
  1. Log into Workday via the web interface.
  2. In the search box, type `Public Web Service` and then select **Public Web Service** from the search results.
  3. Click on **…​** and select **Web Service > View WSDL**. Check `soapbind:address` to ensure you are using the correct host name, for example, `<soapbind:address location=”https://hostname/ccx/…​. />`.


## Triggers
Each flow starts with either a _scheduler_ or a _trigger_. Schedulers are set to a default frequency of 15 minutes. Triggers, such as "each time a new record is created", are defined by you and provide multiple options related to the data in your system.
Triggers use a polling process to actively check for new updates from an external system. The polling frequency is 15 seconds.
This system provides the following trigger options: 

New or updated object
    
This trigger checks for a new or updated object in Workday Financial Management. A value is required in the following field: **Object**.
### Polling Frequency
For triggers in this connector, the **Polling Frequency** field is required. This field enables you to select how often Composer makes a request to the underling system API to look for changes to records in active flows. You can select a different polling frequency for each flow in your organization. With a shorter frequency, the flow executes more often; however, a shorter frequency consumes more API calls. For example, if you have an order management flow, you might require nearly real-time updates, which can be achieved with a 15-second polling interval (which equates to 5760 API calls per day). In contrast, if your flow updates a pricing catalog, you could poll the flow every hour (which equates to 24 API calls per day).
## Actions
After you connect to a system and define the trigger or configure a scheduler, you define the actions that the flow performs. For example, you can copy a record between different systems, such as Workday and Salesforce. The actions you can perform depend on which system you are connected to.
This system provides the following actions: 

Get Worker Details by ID
    
This action returns the worker details corresponding to the employee’s `Workday ID` that you supply. 

Create Worker
    
This action creates a new worker. 

Update Job Requisition
    
This action updates the details on a job requisition. 

Get Customer
    
This action returns the customer details corresponding to the customer ID that you supply. 

Create Object
    
This action creates a new object in Workday Financial Management. Provide a value for **Object**. 

Update Object
    
This action updates an existing object in Workday Financial Management. Provide a value for the following fields:
  * **Unique ID**



Get Object
    
This action returns an existing object in Workday Financial Management. Provide a value for the following fields:
## Object Types
The following object types are available:
  * Triggers
    * JOB_REQUISITIONS
    * WORKER
  * Actions
    * COMPANY
    * CONTRACT
    * CUSTOMER
    * INVOICE
    * JOB_REQUISITIONS
    * PROJECT
    * SALES_ITEM
    * WORKER


## Custom Fields
Custom fields are not supported. Using MuleSoft Composer, you can access standard field values for actions and triggers that you set in the Workday record.
## See Also
  * Mulesoft Composer: Overview
  * MuleSoft Composer: Getting Started
  * Composer Connector Reference
  * Knowledge Articles