> ## Documentation Index
> Fetch the complete documentation index at: https://f4c7a9e2d8b1-docs.tenzo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workday custom fields (WSDL import)

> Export the Recruiting WSDL from Workday Public Web Services so Tenzo can map job and application custom fields.

Tenzo needs the **Recruiting** web service metadata (the WSDL / related XML) from **your** Workday tenant so we can **update job and application custom fields** correctly—using the right **field ids, types, and paths**. We do not pull this file for you—you export it once (and again when custom fields change), then upload it in Admin.

<Warning>
  Upload **UTF-8** XML. Very large or stitched-together dumps may be rejected; use Workday’s normal export.
</Warning>

## Export from Workday

1. In the Workday search bar, open **Public Web Services**.
2. Scroll to **Recruiting (Public)**.
3. Open **Related Actions** (⋯) next to the service → **Web Service** → **View WSDL** (use **View Custom WSDL** if your tenant extensions require it). Workday opens the WSDL as XML in the browser—**download or save the page** (for example **Save As…** with a `.xml` filename) so you have a WSDL XML file on your machine.

<Frame caption="Public Web Services → Recruiting (Public) → Related Actions → Web Service → View WSDL">
  <img src="https://mintcdn.com/tenzoai/RXXiiW8hTf6nvQgA/images/ats-integrations/workday/recruiting-public-wsdl-menu.png?fit=max&auto=format&n=RXXiiW8hTf6nvQgA&q=85&s=34adf15b96586802f1eb911ac6c0337e" alt="Workday Public Web Services report with Recruiting (Public) selected and Web Service menu showing View WSDL" style={{ borderRadius: "0.5rem" }} width="1024" height="528" data-path="images/ats-integrations/workday/recruiting-public-wsdl-menu.png" />
</Frame>

## Upload the XML in Admin

Open **Import Workday Recruiting WSDL** and choose the WSDL XML file you saved from Workday under **WSDL XML file**, then click **Import WSDL**. That file is what builds the custom field catalog for job and application mapping (not workflow steps).

<Frame caption="Admin → Workday integration → Custom Field Mapping → Import Recruiting WSDL (custom fields)">
  <img src="https://mintcdn.com/tenzoai/RXXiiW8hTf6nvQgA/images/ats-integrations/workday/import-recruiting-wsdl-modal.png?fit=max&auto=format&n=RXXiiW8hTf6nvQgA&q=85&s=f4d39adfc8a8d6a9d024ece7826c5034" alt="Import Workday Recruiting WSDL modal with WSDL XML file picker and Import WSDL button" style={{ borderRadius: "0.5rem" }} width="1024" height="758" data-path="images/ats-integrations/workday/import-recruiting-wsdl-modal.png" />
</Frame>

Steps:

1. **Admin** → **ATS Integrations** → your **Workday** integration
2. **Custom Field Mapping** → **Import Recruiting WSDL (custom fields)**
3. **Choose file** → select your saved XML → **Import WSDL**

The response shows how many job vs application field rows were loaded. If pickers stay empty or fields change in Workday, **re-import**. **Workflow steps** are not from this import—use the [workflow step cache](/ats-integrations/workday/workflow-step-cache). For nested application fields, set the [tenant custom XML namespace](/ats-integrations/workday/tenant-namespace).

## See also

* [Workday setup (main checklist)](/ats-integrations/workday/setup)