---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: Configure Custom Agent Action Orchestrations
layout: subsection
---

### Prerequisites

Create an Extend app.

Agent actions use the same authentication method as the Orchestrate Launch API. If you've already configured API client authentication for launching orchestrations, you can use the same Bearer token for MCP requests.

If not, follow these steps to obtain a new bearer token:

1.  [Create Your API Client](/wcp_docs/zwx1518028675482.html). Save the Client ID and Client Secret.
2.  Register the API Client for Integrations in your Workday tenant. Select the appropriate scopes for your orchestrations.
3.  [Request a New Access Token with a Refresh Token](/wcp_docs/cqa1553122177664.html) to obtain a Bearer token for MCP requests.


Note: Access tokens expire after approximately 1 hour. MCP clients must refresh tokens before expiry to maintain connectivity.

### Context

You can create an orchestration with a template type that makes it discoverable and invokable by a Model Context Protocol-compatible AI agent using natural language queries.

### Steps

1.  Create an orchestration based on the <b>Custom Agent Action</b> template. The name can be a maximum of 30 characters long.
2.  On the orchestration's <b>Start</b> step, click <b>Configure Request</b>.
3.  On the <b>Custom Agent Actions</b> tab provide an <b>Action Display Name</b> and an<b>Action Description</b>. The description describes the orchestration's functionality to the AI agent. It should explain not just what the tool does but also when it should be used. Example: 'Makes an ad-hoc percentage adjustment to an employee's base pay. Use this action when there is a request to increase or decrease an employee's base compensation by a percentage.'
4.  In the <b>Action Annotations</b> section, select an effect level for the orchestration so the AI agent can understand its potential impact.

    The options are as follows:

    -   <i>Destructive</i>: Indicates that the action can modify or delete data. AI agents may prompt the user for confirmation before executing.
    -   <i>Idempotent</i>: Indicates that the action can be safely retried without unintended effects. Calling it multiple times produces the same result as calling it once.
    -   <i>Read-Only</i>: Indicates that the action can read data but can't modify or delete it. AI agents can call this action without user confirmation.
    -   <i>Open World</i>: Indicates that an action may interact with an open set of entities not fully known in advance.

    Note: Workday agents ask the user to approve every call to an action that isn't Read-Only. If your action only reads data, always select <i>Read-Only</i> to avoid unnecessary approval requests.

5.  In the <b>Request Properties</b> section, Orchestration Builder lists any input parameters defined on the <b>Start</b> step's <b>Request</b> tab. Provide a description for each parameter, including the expected format and a sample value. Every property must have a description. Example: 'The percentage changes as a decimal string. A 10% increase is 0.1, a 5% decrease is -0.05.' If a property lacks a default, a value must be supplied by the agent.
6.  In the <b>Headers</b> section, define any custom HTTP headers to be forwarded to the orchestration at runtime. These allow AI clients to pass contextual metadata alongside the tool arguments. Header names can be up to 64 characters. Use letters, numbers, hyphens, and underscores only.
7.  In the <b>Query Parameters</b> section, define any query parameters to be forwarded to the orchestration at runtime. Remove any unused query parameter rows before saving. Empty rows can produce invalid tool schemas that prevent MCP clients from loading tools.
8.  On the orchestration's <b>End</b>step, click <b>Configure Response</b>. On the <b>Custom Agent Actions</b> tab, Orchestration Builder lists any output parameters defined on the <b>End</b> step's <b>Body</b> tab. Provide a description for each output parameter so the AI agent can interpret the response.
9.  Save and deploy the app.


### Result

After you add the Custom Agent Action to an agent in the Agent System of Record, the agent can discover and call it through the Agent Gateway.

### Related Information

[Create Your API Client](/wcp_docs/zwx1518028675482.html)

[Get a Refresh Token for WCPISU Authentication](/wcp_docs/bby1527491420006.html)

