Workday

Approves the specified business process event step (Approval step type). Use this to move an Approval-typed step from awaiting state to approved and continue the workflow. The caller must be in the awaiting-person list for the step.

Bulk-import employee review rating updates into Workday Performance Management as an asynchronous EIB import. Each item in `update_employee_review_rating_requests` must contain an `Update_Employee_Review_Rating_Data` element and may contain an `Update_Employee_Review_Rating_Reference`. Do not include an outer `Update_Employee_Review_Rating_Request` key: Composio adds it automatically, and double-wrapping makes the asynchronous Workday job fail despite an HTTP 200. HTTP 200 only means Workday accepted the import for asynchronous processing; verify final success via the returned Import_Process_Reference with the Get Import Processes / Get Import Process Messages tools.

Cancels an in-progress business process event. Use this to terminate a business process before it completes. The optional comment is preserved on the event record. The caller must have permission to cancel the event under Workday's security model for the business process type.

Replace an employee's complete Workday benefit election set for one life event. This operation is not incremental: include every benefit plan available for the event type because omitted elections may be removed or waived. Empty election submissions are rejected because Workday defines no universal waive-all request.

Change one worker's marital status with the Workday Human_Resources v46.2 Change_Personal_Information SOAP operation. This initiates the tenant's single Personal Information Change business process with configured approvals intact. The request exits on initiation-step validation errors instead of leaving an invalid event in progress. Requires the Staffing scope, access to the Person Data: Personal Information or Self-Service: Personal Information security domain, and permission to initiate the Personal Information Change business process. For integration-system-user initiation, Workday may not run every validation that interactive user initiation runs; validate tenant business rules before submitting.

Add or update one worker military service entry with Workday Human_Resources v46.2 Change_Personal_Information while preserving all other entries. Requires the Personal Data scope, access to the Person Data: Personal Information or Self-Service: Personal Information security domain, military-status localization configuration, and permission to initiate the Personal Information Change business process. The process keeps configured approvals, reviews, notifications, and to-dos, and exits on initiation-step validation errors; an initiated response does not mean those steps completed. Deletion is not supported.

Closes a specified request with a given resolution. Security is evaluated based on the request event awaiting the processing person's action. If ``workdayObjectValue`` is provided, ensure the user has View permission on the referenced Workday Object.

Creates a business title change instance for a worker via the Workday Common API v1. Use when you need to initiate a business title change request for an employee, setting the proposed new business title.

Create one Workday Help case. The selected case type must be available to the case owner; use List Case Types with the same worker ID before creating on behalf of another worker.

Creates a new Compensation Scorecard on Workday's Compensation v3 API. Use this to introduce a new merit-and-bonus evaluation template — for example, when modeling FY-level goals or rolling out a refreshed scoring structure to managers. Secured by: Set Up: Merit and Bonus. Required body fields: scorecardName, effectiveDate, and a non-empty defaultScorecardGoals[] (each entry needs goalName and goalWeight). scorecardProfiles[] is optional but each profile must specify eligibilityRule.id and at least one profileScorecardGoals[] entry when supplied.

Creates a new custom field type in Workday's custom object configuration store. Use this when you need to register a new field type (e.g. a list of custom values, a numeric field with bespoke validation) that custom object definitions can subsequently reference via their ``fields`` collection.

Adds a single list value to a custom list field type used by custom object definitions. Use this when you need to extend the set of selectable values exposed by a custom list field (for example, a "Region" field whose options grow over time).

Creates (or updates) custom object instance(s) attached to a Workday business object. The same endpoint serves both single-instance custom objects (at most one instance per business object, e.g. a worker's Parking Space) and multi-instance custom objects (many instances per business object, e.g. a worker's Stock Grants). The custom object's definition determines the mode; bulk=true accepts an array body and is typically used with multi-instance definitions.

Adds a condition rule to an existing custom object definition. Use this when you need to attach a visibility, edit-restriction, or business-logic rule to the custom object before it is activated.

Adds a field to an existing custom object definition. Use this once a custom object definition is created and you need to populate its schema with individual data fields (text, numeric, list-of-values, etc.) prior to activation.

Adds a validation to an existing custom object definition. Use this to attach data-quality / business-rule validations to a custom object before it is activated (for example, "Effective Date must be in the future" or "Amount must be greater than zero").

Creates a Quick Expense entry in Workday Expense v1. The ``date`` (Transaction Date) and ``expenseItem`` fields are required; merchant, memo, amount and receipt attachments are optional but typically supplied. Use this when an LLM needs to record a fresh expense on behalf of a worker before it is later attached to an expense report.

Creates a new attachment (e.g. receipt image) on an existing expense entry in Workday Expense v1. Workday enforces a 32 MB maximum file size; the file content is sent base64-encoded in ``attachmentContent``. Use this when an LLM workflow needs to attach evidence (a scanned receipt, a PDF invoice) to a previously created Quick Expense.

Creates a new expense report in Workday Expense v1. A report acts as the container for one or more expense report lines (which can in turn be backed by Quick Expenses, credit card transactions, or travel booking records). Use this as the first step in a "build → fill → submit" expense workflow. Use Create Expense Report Line to populate lines, then Submit Expense Report to send it for approval.

Creates an expense report line on an existing expense report in Workday Expense v1. Lines can be created directly with date / expense item / amount, or by referencing an existing Quick Expense, credit card transaction, or travel booking record to inherit its values. Use this after Create Expense Report to populate the report's lines before submitting it for approval.

Creates a new address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Home Address, Self-Service: Home Address. Scope: Contact Information.

Creates a new email address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Home Email, Self-Service: Home Email. Scope: Contact Information.

Creates a new instant messenger staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Home Instant Messenger, Self-Service: Home Instant Messenger. Scope: Contact Information.

Creates a new phone number staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Home Phone, Self-Service: Home Phone. Scope: Contact Information.

Creates a new web address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Home Web Address, Self-Service: Home Web Address. Scope: Contact Information.

Creates a job change instance for a worker in Workday with specified data. Use when initiating organizational, supervisory, or job assignments changes for employees. The job change requires a valid effective date and optionally accepts job change reason, supervisory organization, job, location, and template references.

Creates a mentorship for the current processing worker, who is set as the mentee. Use when a worker wants to self-create a mentorship with a chosen mentor and type.

Creates a new mentorship between two workers. Use when a manager or admin needs to set up a mentor / mentee relationship; if Manage Mentorship has an approval step, the mentorship is not created until the mentorship event is approved.

Creates a new message template. Use when configuring a new notification template (e.g. a hiring email or push notification) that other Workday processes will reference by ID. Workday returns the newly created template including its assigned ID.

Creates a new change organization assignment event for a specific filled or unfilled position. Returns a new change organization assignment ID that must be supplied in subsequent requests (sub-resource GETs / PATCHes, and POST /submit) that update or fetch information about this event. Use this action to initiate an organization assignment change (move a worker between business units, companies, cost centers, regions, etc.) before submitting it.

Secured by: Worker Data: Organization Goals Scope: Performance Enablement. Use when you need to create this Workday resource via the Performance Enablement REST API. The spec's request body schema for this op resolves to no documented properties; pass a free-form JSON object via the `body` field matching Workday's public field names.

Creates a single payroll input instance with the specified data. At minimum, specify worker, payComponent, and startDate. If a position-based payComponent is used, position is required. If ongoing is false, endDate is required. If inputDetails is specified, the type field is required for each detail.

Create one Workday Recruiting prospect with a validated name and either an email address or complete phone details. Name components beyond this action's minimum depend on the tenant's Recruiting Name Components configuration. Referral attribution is optional; setting referredBy requires source to identify the tenant's configured Referral source. This creates the prospect record only and does not initiate the Refer a Candidate business process.

Creates an education entry for the specified prospect. Adds a single education (candidateEducationDetails) instance under the prospect. Workday requires `schoolName` at minimum. Scope: Recruiting. Secured by: Create External Prospects.

Creates a work experience entry for the specified prospect. Adds a single experience (prospectExperienceDetails) instance under the prospect. Workday requires `companyName`, `title`, and `startYear` at minimum. Scope: Recruiting. Secured by: Create External Prospects.

Creates a skill entry for the specified prospect. Adds a single skill (candidateSkillItemDetails) instance under the prospect. Workday requires `name` at minimum. Scope: Recruiting. Secured by: Create External Prospects.

Initiate Workday Human_Resources v46.2 Create_Reference_Letter_for_Worker for a tenant-enabled worker and reference-letter template. Uses the single Reference Letter Request business process with configured approvals intact.

Creates a new request with the given data. Required fields depend on the request type — use the 'Create Requests' task in Workday or GET /types/{ID} to discover them. Secured by the processing person's Initiate access. Note: the Workday spec advertises multipart/form-data, but this action sends JSON because the schema body's required parts are simple JSON. Use a separate multipart upload action for attachment use cases.

Creates a new Scorecard Result instance on Workday's Compensation v3 API. Use this when initiating an evaluation cycle against an existing Compensation Scorecard — for example, kicking off merit-and-bonus scoring for an employee or team. Secured by: Set Up: Merit and Bonus. Required body fields: compensationScorecard / scorecardID (the scorecard ID returned by Get Compensation Scorecards) and evaluationDate.

Creates a new succession plan instance for a position. Specify a valid position ID; the position must not already have an active succession plan.

Creates a single company SUI (State Unemployment Insurance) rate. At a minimum, specify companyInstance, stateInstance, startDate, and taxCode; supply applicableRate to override the default authority rate or exempt to mark the company as exempt.

Create a worker check-in, check-out, meal, or break event. Requires the Workday Time Tracking scope and access to the Process: Time Clock Event REST API's security domain. timeEntryCode, project, and projectPlanTask are optional but mutually exclusive. Create any required worker time attestations first, then pass their IDs in workerTimeAttestations.

Creates a time off request for the specified worker and initiates the business process. Use Get Worker Time Off Details to find valid time off type IDs (e.g., Vacation, Sick Leave) from the worker's existing time off entries, and Get Current User to get the authenticated worker's ID. Note: This endpoint works with time off types, not Leave of Absence types.

Creates a new address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Work Address, Self-Service: Work Address. Scope: Contact Information.

Creates a new email address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Work Email, Self-Service: Work Email. Scope: Contact Information.

Creates a new instant messenger staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Work Instant Messenger, Self-Service: Work Instant Messenger. Scope: Contact Information.

Creates a new phone number staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Work Phone, Self-Service: Work Phone. Scope: Contact Information.

Creates a new web address staged by the parent business process event. Use this action when integrating Workday's person v4 API and you need to post this specific resource. Secured by: Person Data: Work Web Address, Self-Service: Work Web Address. Scope: Contact Information.

Creates a single feedback given event instance about the specified worker. Use when you need to create this Workday resource via the Performance Enablement REST API. The spec's request body schema for this op resolves to no documented properties; pass a free-form JSON object via the `body` field matching Workday's public field names.

Saves the skills a worker has, creating explicit-skill usage instances. Secured by: Self-Service: Skills Scope: Worker Profile and Skills

Creates a single self-requested feedback event instance for the specified worker. Use when you need to create this Workday resource via the Performance Enablement REST API. The spec's request body schema for this op resolves to no documented properties; pass a free-form JSON object via the `body` field matching Workday's public field names.

Creates a single requested feedback event instance for the specified worker. Use when you need to create this Workday resource via the Performance Enablement REST API. The spec's request body schema for this op resolves to no documented properties; pass a free-form JSON object via the `body` field matching Workday's public field names.

Creates skill items in bulk for the specified worker. Secured by: Person Data: Skills, Self-Service: Skills Scope: Worker Profile and Skills

Create one persistent Workday Time Tracking Worked Time block. In/out entries require Workday time-zone references from LIST_WORKED_TIME_OPTIONS; scalar IANA time-zone strings are not accepted by Workday. Reference-based in/out entries default to v5 for compatibility; set api_version=v6 to use v6. The toolkit does not expose a compatible v6 delete action, so obtain explicit confirmation and plan manual tenant cleanup before creating it. For hourly time, provide calendarDate and a positive reportedQuantity. For flat in/out time, provide inTime, outTime, inTimeZone, and outTimeZone; calendarDate is optional. Exactly one timeEntryCode, project, or projectPlanTask is required. Use LIST_WORKED_TIME_OPTIONS to discover eligible references. Requires the Time Tracking scope and Process: Time Block REST APIs security domain.

Creates a time review event for the specified worker. Typically used by managers / admins to submit time on behalf of workers, or by workers to submit their own time for approval. The date determines whether time is submitted for the pay period or week.

Deletes a Compensation Scorecard with the specified ID from Workday's Compensation v3 API. Use when retiring an obsolete scorecard template or cleaning up duplicates. Workday rejects the call (HTTP 400) if the scorecard is referenced by existing Scorecard Results. Secured by: Set Up: Merit and Bonus. Workday returns no body on success, so the action surfaces a boolean confirmation plus the deleted ID.

Deletes a custom object instance. Specify either the extended Workday object ID or the custom object's own ID. The same endpoint serves both single-instance and multi-instance custom object definitions.

Removes a condition rule from a custom object definition. Use this when a previously attached visibility or business-logic rule is no longer needed on the custom object.

Removes a validation from a custom object definition. Use this when a previously attached data-quality check is no longer appropriate for the custom object (for example, when relaxing a required-field rule).

Deletes a Quick Expense entry from Workday Expense v1 by its Workday Identifier (WID). The entry is permanently removed and cannot be restored through the REST API. Use this only when an entry was created in error or is no longer needed; for entries already attached to a submitted report, deletion may be blocked by Workday's business rules.