Harmony Workday Connector¶
The Harmony Workday Connector is accessed from the design component palette's Connections tab (see Design Component Palette).
This connector is used to first configure a Workday connection, establishing access to an account on the Workday server, and then used to configure one or more Workday activities associated with that connection as either a source or target within an operation.
The operations of each web service are categorized under these activities on the basis of the starting token of the operation. Examples:
Operations that aren't covered by the above categorization (operations whose starting token is not listed above) such as the Start_International_Assignment or the Switch_Primary_Job operations, from the Staffing web service, are available in the Other activity.
In this documentation, only a generic Workday activity is documented, as each activity has a similar design.
- Workday activity: A Workday activity retrieves data from and/or sends data to a selected Workday web service and is used as a source or target in an operation.
The Workday connector requires the use of an agent version 10.1 or later.
Together, a specific Workday connection and its activities are referred to as a Workday endpoint. Once a connection is configured, activities associated with the endpoint are available from the Endpoints filter:
This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.
To connect with the Workday server, contact the Workday administrator for the required credentials. You will need:
- Workday host (this will be a URL such as
- Workday tenant
- Workday username
- Workday password
If you experience issues with the Workday connector, these troubleshooting steps are recommended:
Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).
Check the operation logs for any information written during execution of the operation.
If using Private Agents, you can enable connector verbose logging for this connector using this specific configuration entry of logger name and level:
<logger name="org.jitterbit.connector.workday" level="DEBUG"/>
If using Private Agents, you can check the agent logs for more information.