CONNECT APP
Build with Workday
Human Resources
- OAuth
MCP
Give your agent Workday tools
Every Workday action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Workday account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "workday",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Change Business Title:
const result = await mcp.callTool({
name: "workday-change-business-title",
arguments: {
workerId: "Worker ID",
proposedBusinessTitle: "Proposed Business Title",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "workday",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Change Business Title:
result = await session.call_tool("workday-change-business-title", {
"workerId": "Worker ID",
"proposedBusinessTitle": "Proposed Business Title",
})API PROXY
Call the Workday API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Workday API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Workday endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Workday actions from your backend
Connect a user's Workday account once, then run Change Business Title on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "workday-change-business-title",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
workday: { authProvisionId: "apn_xxxxxxx" },
workerId: "Worker ID",
proposedBusinessTitle: "Proposed Business Title",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="workday-change-business-title",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"workday": {"authProvisionId": "apn_xxxxxxx"},
"workerId": "Worker ID",
"proposedBusinessTitle": "Proposed Business Title",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "workday-change-business-title",
"configured_props": {
"workday": { "authProvisionId": "apn_xxxxxxx" },
"workerId": "Worker ID",
"proposedBusinessTitle": "Proposed Business Title"
}
}'TOOLS
Workday actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Change Business Title
actionChange the business title of a worker. See the documentationWritev0.0.3 -
Create Job Change
actionCreate a job change for a worker. See the documentationWritev0.0.3 -
Get Worker
actionGet a worker. See the documentationRead-onlyv0.0.3 -
List Job Change Reason ID Options
actionRetrieves available options for the Job Change Reason ID field.Read-onlyv0.0.1 -
List Organization Types
actionList organization types. See the documentationRead-onlyv0.0.3 -
List Supervisory Organization ID Options
actionRetrieves available options for the Supervisory Organization ID field.Read-onlyv0.0.1 -
List Supervisory Organizations
actionList supervisory organizations. See the documentationRead-onlyv0.0.3 -
List Worker ID Options
actionRetrieves available options for the Worker ID field.Read-onlyv0.0.1 -
List Worker Payslips
actionList the payslips for a worker. See the documentationRead-onlyv0.0.3 -
Search Workers
actionRetrieve a list of workers based on a search query. See the documentationRead-onlyv0.0.3
EVENTS
Workday triggers
Event sources your backend can deploy for users and receive through a webhook.
MULTI-APP
Use Workday with other popular apps
Most products don't stop at one integration. Pair Workday with the other apps your users rely on, and ship use cases that span both.
- App slug
- workday
- Authentication
- OAuth
- Categories
- Human Resources
- Actions
- 10
- Triggers
- 1
- API proxy
- Available