> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/guides/integrations/integrations-hris/workday-integration.md). # Connect Workday Connect Workday to Siit with a read-only Integration System User to sync employees, employment, groups and locations on a schedule, with optional field mapping and FAQ ### Overview The Siit–Workday integration automatically synchronises employee and HR data from Workday into Siit on a regular schedule, so your service management data always reflects the current state of your workforce — with no manual imports required. This integration is read-only from Workday's perspective. Siit reads data from Workday but never writes back to it. ### Prerequisites Before setting up the integration, make sure the following are in place: * A Workday tenant with API access enabled * An Integration System User (ISU) in Workday with read-only permissions on HR data * Admin access in Siit to configure integrations * Your Workday tenant URL, ISU username, and password {% hint style="success" %} 💡 Tip: We recommend creating a dedicated Workday ISU with read-only permissions scoped to the data objects below. This follows the principle of least privilege and keeps your integration secure. {% endhint %} ### Synced Data Objects & Fields The tables below list every object synced from Workday, along with the specific fields available in Siit. All data flows from Workday into Siit only (one-way sync). #### Employee Core employee profile information. | **Field** | **Description** | | ------------------------- | ---------------------------------------------------------- | | **employee\_number** | Unique employee identifier in Workday | | **first\_name** | Employee's first name | | **last\_name** | Employee's last name | | **display\_full\_name** | Full display name | | **work\_email** | Work email address | | **personal\_email** | Personal email address | | **mobile\_phone\_number** | Mobile phone number | | **username** | System username | | **hire\_date** | Date the offer letter was signed / most recent hire date | | **start\_date** | Date the employee started working (most recent if rehired) | | **termination\_date** | Date of termination, if applicable | | **employment\_status** | ACTIVE, PENDING, or INACTIVE | | **gender** | Gender identity | | **ethnicity** | Ethnicity | | **date\_of\_birth** | Date of birth | | **avatar** | URL of the employee's profile photo | | **manager** | Reference to the employee's manager | | **team** | Team the employee belongs to | | **pay\_group** | Pay group assignment | | **company** | Legal entity / company reference | | **locations** | List of locations associated with the employee | | **remote\_id** | Workday's native ID for the record | #### Employment Employment history and position details. A new record is created whenever job title or pay changes. | **Field** | **Description** | | -------------------- | --------------------------------------------------------------- | | **job\_title** | The position's title | | **employment\_type** | Type of employment (e.g. FULL\_TIME, PART\_TIME, CONTRACTOR) | | **pay\_rate** | Compensation rate for the position | | **pay\_period** | Period the pay rate covers (HOUR, DAY, WEEK, MONTH, YEAR, etc.) | | **pay\_frequency** | How often the employee is paid | | **pay\_currency** | Currency code in ISO 4217 format | | **flsa\_status** | FLSA classification (EXEMPT or NON\_EXEMPT) | | **effective\_date** | Date this employment record became effective | | **employee** | Reference to the associated Employee | | **remote\_id** | Workday's native ID for the record | #### Group Organisational groups — departments, cost centres, and other groupings. | **Field** | **Description** | | ----------------- | ------------------------------------------------ | | **name** | Group name | | **type** | Group type (e.g. DEPARTMENT, TEAM, COST\_CENTER) | | **parent\_group** | Reference to the parent group in the hierarchy | | **remote\_id** | Workday's native ID for the record | #### Location Office and remote work locations assigned to employees. | **Field** | **Description** | | -------------- | ---------------------------------- | | **name** | Location name | | **type** | Location type (HOME, WORK) | | **street\_1** | Street address line 1 | | **street\_2** | Street address line 2 | | **city** | City | | **state** | State or region | | **zip\_code** | Postal / ZIP code | | **country** | Country code (ISO 3166-1 alpha-2) | | **remote\_id** | Workday's native ID for the record | ### Setting Up the Integration #### Step 1 — Connect Workday in Siit 1. In Siit, go to Settings > Integrations > Workday. 2. Click Add Integration and select Workday. 3. Enter your Workday tenant URL, ISU username, and password. 4. Click Authorise. Siit will validate the connection and begin the first sync. #### Step 2 — Configure Field Mapping (Optional) Once connected, you can review and adjust how Workday fields map to Siit user attributes under Settings > Employee Groups > People Fields #### Step 3 — Verify the Sync After the first sync completes, go to Resources > People to verify that data has been imported correctly. ### Frequently Asked Questions #### Can Siit update data in Workday? No. This integration is strictly read-only. Siit reads data from Workday and never writes back to it. #### What happens when an employee is offboarded in Workday? When an employee's status changes to INACTIVE in Workday, Siit will reflect this change on the next sync. The employee will be marked as Alumni and will no longer count as an active employee. #### How long does the initial sync take? For most organisations, the initial sync completes within a few minutes. For large organisations with 10,000+ employees, it may take up to 30 minutes. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/guides/integrations/integrations-hris/workday-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.