# Workday connector

The Workday connector brings the HR data held in an organisation's Workday tenant into TechWolf, where it is used to infer the skills of employees and the skill requirements of jobs. Workday HCM typically holds most of an organisation's HR data, which makes it one of the richest sources for skill inference. The integration is one-way: data flows from Workday to TechWolf.

## Key attributes

The connector covers up to fourteen distinct data types from Workday, and an organisation enables only the ones relevant for its use case:

- **Workers and organisational units.** Each worker's identifier, current job profile, and supervisory organisation, plus the organisation hierarchy.
- **Jobs, job families, and vacancies.** The job profile catalogue with names and descriptions, the job family structure, and job requisitions.
- **Courses and learning.** The learning content catalogue and each worker's completed learning enrolments.
- **Working histories.** Internal staffing history, consolidated into job periods, and previous work history from before the current employer.
- **Certificates and education.** Certifications with issue and expiration dates, and education history.
- **Goals, performance reviews, and feedback.** Development and performance data. Goals and feedback load as skill events on the employee.

## How it works

Workday data reaches TechWolf through one of two routes:

- **API-based connector.** The organisation creates a connector per data type on the **Connectors** page in the Console. Each connector queries the Workday REST API with the Workday Query Language on its own schedule, daily, weekly or on a custom cron, or when someone clicks **Run now**. A run writes the results to the organisation's TechWolf storage, and the Data Integrator integrations linked to the connector then load them into the tenant. For the per-worker histories, learning, goals, performance reviews and feedback, a Diff variant re-reads only the workers with changes since the previous run. Filters keep the loaded data relevant, for example only completed learning enrolments are loaded.
- **File-based exports.** Workday's Enterprise Interface Builder generates scheduled CSV exports following TechWolf's specification and writes them to the organisation's TechWolf S3 bucket. Files are full dumps: each export describes the complete state of the entities it covers. Fields can be renamed, split, or combined in the export, as long as the mapping is agreed with TechWolf.

For the API-based connector, the organisation creates an Integration System User in Workday with the security permissions for the selected data types, registers an API client, and adds the client's credentials on the **Connectors** page. TechWolf stores the credentials encrypted and decrypts them only during a run. When a connector is created, it runs its query against Workday and lists the security domains that are missing, if any. **Set up the Workday connector** covers these steps.

With either route, an integration per data type loads the data into the tenant, as described in **Set up an integration**. **Load in datasources** covers the whole path from source system to tenant.

## Prerequisites

The Workday connector is part of TechWolf's input integrations. It requires a Workday HCM tenant and a TechWolf tenant. The API-based connector requires the Workday Query Language feature in the Workday tenant and an Integration System User with the permissions for the enabled data types; the file-based route requires Enterprise Interface Builder exports configured to TechWolf's specification.

## Availability

- **Console:** the **Connectors** page for the Workday connector's credentials, schedules and runs, with each run's status, record counts and the integration runs it started, and **File-Based Integrations** for the integrations that load the data from either route.

## Related pages

- [Data Integrator](/input-integrations/data-integrator)