Appearance
Workday
Access HR, payroll, and talent management data from Workday.
| Detail | Value |
|---|---|
| Category | HR |
| Base URL | https://wd2-impl-services1.workday.com/ccx/api/v1/{tenant} |
| Authentication | OAuth2 |
| Endpoints | 5 |
| Connector key | workday |
Using Workday in a workflow
- Go to Connections and click New Connection.
- Pick Workday from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /workers | List workers |
GET /workers/{workerId} | Get a worker |
GET /organizations | List organizations |
GET /locations | List locations |
GET /timeOff | List time off entries |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /workers
List workers
| Detail | Value |
|---|---|
| Operation ID | hr.listWorkers |
| Method | GET |
| Path | /workers |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
limit | query | integer | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Workday connection from the Connection dropdown.
- In the Operation dropdown, select
hr.listWorkers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Workday API reference.
GET /workers/{workerId}
Get a worker
| Detail | Value |
|---|---|
| Operation ID | hr.getWorker |
| Method | GET |
| Path | /workers/{workerId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
workerId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Workday connection from the Connection dropdown.
- In the Operation dropdown, select
hr.getWorker. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Workday API reference.
GET /organizations
List organizations
| Detail | Value |
|---|---|
| Operation ID | hr.listOrganizations |
| Method | GET |
| Path | /organizations |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Workday connection from the Connection dropdown.
- In the Operation dropdown, select
hr.listOrganizations. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Workday API reference.
GET /locations
List locations
| Detail | Value |
|---|---|
| Operation ID | hr.listLocations |
| Method | GET |
| Path | /locations |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Workday connection from the Connection dropdown.
- In the Operation dropdown, select
hr.listLocations. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Workday API reference.
GET /timeOff
List time off entries
| Detail | Value |
|---|---|
| Operation ID | hr.listTimeOff |
| Method | GET |
| Path | /timeOff |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Workday connection from the Connection dropdown.
- In the Operation dropdown, select
hr.listTimeOff. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Workday API reference.