Workday
Arcade Optimized
Arcade.dev tools for interacting with Workday
Author:Arcade
Version:
0.1.0Auth:User authorization
7tools
7require secrets
The Workday toolkit lets Arcade agents interact with a Workday tenant on behalf of the signed-in worker via OAuth. It covers the full time-off self-service workflow — from identity resolution through balance checks, date validation, request creation, and status tracking.
Capabilities
- Worker identity — Resolve the authenticated worker and their job context before performing any other operation; all tools act on that same worker and cannot be redirected to another.
- Time-off eligibility & balances — List the time-off types a worker can request (with rules: units, reason requirements, position requirements, clock-time handling, draft support) and retrieve current plan balances exactly as Workday calculates them.
- Date validation — Check candidate dates against a specific time-off type before submitting, with per-date acceptance results and booking context where computable.
- Request creation — Submit or save draft time-off requests; the toolkit resolves type rules from Workday first, then writes the request. Existing requests must be modified or cancelled in Workday directly.
- History & status tracking — Browse past time-off entries with date-windowed paging, and check current request status with group-level action guidance, incomplete-read signals, and UI-action flags for drafts or sent-back requests.
OAuth
Authentication uses OAuth 2.0 via the Workday provider. Users authorize access through their Workday account; the toolkit then operates on the signed-in worker's record.
Secrets
Two secrets must be configured for the toolkit to reach the correct Workday environment.
-
WORKDAY_BASE_URL— The base URL of your organization's Workday REST API endpoint. This is the root URL specific to your tenant, typically in the formhttps://<hostname>/ccx/api. Obtain it from your Workday administrator or by inspecting your Workday tenant's API endpoint configuration. The exact path is determined by how your organization has deployed Workday. -
WORKDAY_TENANT_NAME— The Workday tenant name (also called the tenant ID) that identifies your organization's Workday instance. It appears in your Workday URLs (e.g.,https://wd3.myworkday.com/<tenant_name>/...). Your Workday administrator can confirm the exact value. If you have access to the Workday admin interface, it is visible in System Configuration or in the URL when logged in.
For instructions on configuring secrets in Arcade, see the Arcade secrets guide. You can also manage secrets at https://api.arcade.dev/dashboard/auth/secrets.
Available tools(7)
7 of 7 tools
Operations
Behavior
| Tool name | Description | Secrets | |
|---|---|---|---|
List the time-off types the signed-in worker can request, with their rules.
Each entry includes its display name and time_off_type_id. Retrieve the options here
and pass the chosen ID to the date check and request tools. Each entry also carries what
Workday reports for that type: a default quantity, whether a reason is mandatory
and which reasons are allowed, whether a position must be named, and whether clock
times are required, determine the quantity, or may cross midnight. `draft_support`
reports evidence of existing drafts. Requests use draft mode by default; set mode
to submit only when the worker asks for submission.
Each type's unit is the unit to use for request quantities; do not pass fractions
of a full day for an hourly type. start_and_end_time_required requires both clock
times. calculate_quantity_based_on_start_and_end_time means Workday determines the
recorded quantity from those times. crossing_over_midnight_enabled permits an
earlier end time on the following date, keeping the span under 24 hours. | 2 | ||
Show how much time off the signed-in worker has left, by plan.
Balances come back exactly as Workday calculates them for the as-of date; this
tool never projects or totals an accrual Workday did not return. It reads the
signed-in worker record to address the balances to that worker. Read `coverage`
before relaying an empty list: it says whether no plan is tracked for this worker
or the read simply did not finish, and a worker whose time off is not
balance-tracked can still request time off. | 2 | ||
Browse the time off the signed-in worker has already logged.
Matching entries come back in ascending date order, earliest first. Defaults to a
three-month window either side of today. These date bounds are sent to Workday
before paging, so a narrow window does not scan the worker's whole history.
A request with mixed attributes
appears as separate groups sharing one request_id. All matching groups stay on
one page and count as one request. Dates and quantities cover only matching day
entries, including only the in-window portion of an overlapping request. A capped
read marks groups incomplete and omits totals; narrow the window to reduce the
upstream read. Existing requests must be changed
or cancelled in Workday; this toolkit cannot modify them.
requests[].dates are YYYY-MM-DD dates inside the selected window; out-of-window
days of the same request are excluded. Each group's unit applies only to that group.
result_count, total_count, limit, and offset count distinct request IDs, not groups.
Page with has_next_page and next_offset. results_truncated means the upstream read
was capped; no offset completes that read, so narrow the date bounds or check Workday.
requires_workday_ui_action identifies drafts or sent-back groups needing action;
use their workday_ui_action, falling back to the response's shared guidance.
status=unknown means Workday's status was missing or unrecognized. Check Workday
to confirm its state and any required action; requires_workday_ui_action=false
does not establish that no action is needed for an unknown status. | 2 | ||
Show where the signed-in worker's time-off requests stand right now.
Defaults to no date bound, subject to the read cap. Provide dates to narrow the
upstream search when results are incomplete. Requests come back in ascending order
of their earliest matching date. The first page contains the earliest matching
requests, which may be years in the past when no lower date bound is supplied.
For upcoming or next time off, set from_date to today's date in YYYY-MM-DD;
the unbounded first page does not identify the next time off.
A request with different types, units, statuses, positions, reasons, or notes
appears as separate groups sharing one request_id. All matching groups stay on
one page and count as one request. Dates and quantities describe only matching
entries within the requested window. Capped reads mark groups incomplete and omit
quantity totals. Each group reports its own status and action guidance. Existing
requests must be changed or cancelled in Workday; this toolkit cannot modify them.
requests[].dates are YYYY-MM-DD dates inside the selected window; out-of-window
days of the same request are excluded. Each group's unit applies only to that group.
result_count, total_count, limit, and offset count distinct request IDs, not groups.
Page with has_next_page and next_offset. results_truncated means the upstream read
was capped; no offset completes that read, so narrow the date bounds or check Workday.
requires_workday_ui_action identifies drafts or sent-back groups needing action;
use their workday_ui_action, falling back to the response's shared guidance.
status=unknown means Workday's status was missing or unrecognized. Check Workday
to confirm its state and any required action; requires_workday_ui_action=false
does not establish that no action is needed for an unknown status. | 2 | ||
Check whether Workday accepts each date for the selected time-off type.
Send the candidate dates together before creating a request. Each result separates
date acceptance from the configured default and existing bookings. A default does
not establish a maximum, and a missing default says nothing about the worker's
schedule. Accepted dates therefore have unknown capacity; Workday validates the
requested quantity on submission.
Booking totals include only matching known units and position scope. Incompatible
units or ambiguous positions leave the total unknown. Worker-based checks include
bookings regardless of their position reference; position-scoped checks exclude
bookings against another position. Incomplete booking lookups omit all booked totals
and disclose that the booking names shown are partial results.
dates[].valid reports date acceptance, not available quantity. valid_count counts
accepted dates. bookable_spans stays empty because maximum capacity is unknown;
this does not mean none of the dates are valid. Read coverage_note for lookup limits. | 2 | ||
Request time off for the signed-in worker, asking for a draft by default.
Set mode to submit only when the worker asks for submission. Existing drafts must
be submitted in the Workday UI; existing requests must also be changed or cancelled
there. The receipt reports the confirmed state, or created_status_unknown when
read-back cannot confirm it. In that case, check list_time_off_status using the
returned identifiers; do not repeat the create. Recorded amounts appear in days;
requested_days preserves the values sent, and missing amounts are unconfirmed. The type's
rules are resolved from Workday first, so a reason, a position, and an omitted
quantity are checked against that type before anything is written. Workday owns the
rest of the validation; its rejections come back as errors describing what to change.
In the receipt, days[].date matches the requested date and days[].unit labels only
that entry's recorded amount. Missing quantity means unconfirmed, never zero.
requested_days contains the quantities (including defaults) and clock times sent.
status is draft_saved, submitted, approved, or sent_back when confirmed;
created_status_unknown means the request exists but its state is unknown, and
blocked_by_warning means nothing was written. requires_workday_ui_action=false
on an unconfirmed receipt means no action was established; read status before advising. | 2 | ||
Identify the Workday worker the connection is signed in as, and their jobs.
Call this before acting on the worker's record so the answer is anchored to the
right person and tenant. Every other tool in this toolkit acts on this same worker
and cannot be pointed at anyone else. | 2 |
Last updated on