Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -122,9 +122,11 @@ Community examples, open to everyone. This is the section external contributions
| [`employee-data-orchestration`](examples/employee-data-orchestration) | An orchestration that reads worker data from one tenant and creates matching records through the Workday REST API. | Orchestration |
| [`help-case-agent-skill`](examples/help-case-agent-skill) | A markdown skill for an agent that routes an HR question to the right help case type in Workday, prepares the case for approval, and prepares a comment on an existing case, with a clickable link when one is needed. | Agent Skill |
| [`inbox-decisions-agent-skill`](examples/inbox-decisions-agent-skill) | A markdown skill that teaches an agent to read a person's Workday inbox, explain what each step does and prepare an approve, deny or send back decision for approval. | Agent Skill |
| [`integration-health-agent-skill`](examples/integration-health-agent-skill) | A markdown skill for an agent that reports how Workday integrations are doing from real event counts and prepares launches and cancellations. | Agent Skill |
| [`learning-enrolment-agent-skill`](examples/learning-enrolment-agent-skill) | A markdown skill for an agent that finds learning content through read-only WQL and prepares enrolments for a person or their team, for approval. | Agent Skill |
| [`leave-of-absence-agent-skill`](examples/leave-of-absence-agent-skill) | A markdown skill for an agent that reads a worker's leaves of absence and prepares a leave request or a return from leave in Workday. | Agent Skill |
| [`org-design-agent-skill`](examples/org-design-agent-skill) | A markdown skill for an agent that moves workers between supervisory organizations and creates or closes positions in Workday. | Agent Skill |
| [`payroll-input-agent-skill`](examples/payroll-input-agent-skill) | A markdown skill for an agent that reads payroll inputs and payslip summaries and prepares payroll inputs or pay group assignments in Workday. | Agent Skill |
| [`peer-kudos-home-card`](examples/peer-kudos-home-card) | An Extend app with a Home page card, custom business object, and orchestration that lets employees celebrate peer contributions and notifies managers. | Extend App |
| [`promotion-nomination`](examples/promotion-nomination) | A manager nominates a direct report for promotion. Career data is prefilled from Workday, the nomination is saved to a business object, and a business process routes it for approval. | Extend App |
| [`pto-policy-agent-skill`](examples/pto-policy-agent-skill) | A markdown skill that teaches an agent to answer employee questions about PTO, leave accrual, rollover, and sick leave policy with clear escalation rules. | Agent Skill |
Expand Down
25 changes: 25 additions & 0 deletions examples/integration-health-agent-skill/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Integration health skill

## What it is

A markdown skill for an agent that reports how Workday integrations are doing from real event counts and prepares launches and cancellations. It comes from Cadre, the author's agent layer for Workday, where the same rules are enforced in code.

## What's inside

- `SKILL.md` is the skill: the Workday operations for integration events, systems and system load, the rule that health numbers are reported exactly as returned, and the output format.
- `example.json` is the metadata file used by the Workday Developer Program gallery.

## How to use it

1. Read `SKILL.md`.
2. Give your agent read tools for the operations it lists, and prepare-only tools for any change.
3. Put an approval step between the proposal and the Workday call.
4. Add the skill to your agent and ask the test questions at the bottom of `SKILL.md`.

## Before you deploy

- **Approval gate**: build the approval step before connecting write access. A launch runs a real integration and a cancel stops one mid-run.
- **Access**: the event and system reads need integration event and integration configuration access. System load needs the System Monitor Administrator or System Monitor Support domain. If the account lacks them, the skill reports a refusal.
- **Scope**: reading integration events and systems, system load, launching an integration with its saved settings and cancelling a running event. It does not pass launch parameters and does not cancel finished events.
- **Tool names**: map the operations in `SKILL.md` to your platform's tools.
- **Tested how**: on 22 November 2026 the author ran the reads on a Workday development tenant with an OAuth token for a signed-in user: SOAP Integrations v46.2 `Get_Integration_Systems` returned 168 integration systems, `Get_Integration_Events` returned 47,442 events (paged, 3 per page in the test), and REST systemMetrics/v1 `GET /systemMetricsOverview` returned the live session count. `Launch_Integration` and `Cancel_Integration_Event` follow Workday's published Integrations definitions and were not run, so try each one in a non-production tenant first.
39 changes: 39 additions & 0 deletions examples/integration-health-agent-skill/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
---
name: integration-health
description: Reports how Workday integrations are doing from real event counts and prepares launches and cancellations. Use when an administrator asks about integration failures or wants to launch or cancel an integration. Do not use to pass launch parameters, to call a pattern a trend, or to cancel a finished event.
---

# Integration health

Report the numbers exactly as returned, then prepare a launch or cancel if asked.

## Decision

| Request | Workday operation | Notes |
| --- | --- | --- |
| How are integrations doing | SOAP Integrations `Get_Integration_Events` | Counts by status and integration, recent failures |
| List events | SOAP Integrations `Get_Integration_Events` | Set status to failed for failures |
| Find an integration | SOAP Integrations `Get_Integration_Systems` | Workday ID by name |
| System load | REST systemMetrics/v1 `GET /systemMetricsOverview` | Live sessions and queued tasks |
| Launch | SOAP Integrations `Launch_Integration` | Runs with its saved settings |
| Cancel | SOAP Integrations `Cancel_Integration_Event` | Running events only |

## Hard rules

- Every change is a proposal. Say it is not done until a person approves it and Workday accepts it.
- Facts and figures come only from Workday reads in this conversation. If a read returned nothing, say it is not available.
- Report health numbers exactly as returned: events counted, counts by status, counts per integration, and the latest failures with Workday's own message text. Never add figures or call anything a trend.
- If the counts cover only part of Workday's events, say so. If Workday returns no message for a failure, say the message is not available.
- To launch, find the integration by name and confirm which one with the person. It runs with its saved settings; launch parameters cannot be passed.
- To cancel, find the running event first. Finished events cannot be cancelled.
- If system load is refused, the account is missing the System Monitor Administrator and System Monitor Support domains. Say which is missing. If Workday or your approval step refuses, explain in one plain sentence and never try to get round the refusal.

## Output format

The counts as a small table, the latest failures with Workday's message text, or a proposal card for the launch or cancel.

## Test questions

- "How are my integrations doing today?"
- "Launch the payroll export integration."
- "Is the failure rate going up this week?"
15 changes: 15 additions & 0 deletions examples/integration-health-agent-skill/example.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
{
"title": "Integration Health Agent Skill",
"description": "A markdown skill for an agent that reports how Workday integrations are doing from real event counts and prepares launches and cancellations.",
"type": "Agent Skill",
"components": [],
"products": [
"Workday SOAP API",
"Workday REST API"
],
"authors": [
"Daksh-Aneja-Projects"
],
"tutorial": "",
"source": "community"
}
25 changes: 25 additions & 0 deletions examples/payroll-input-agent-skill/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Payroll input skill

## What it is

A markdown skill for an agent that reads payroll inputs and payslip summaries and prepares payroll inputs or pay group assignments in Workday. It comes from Cadre, the author's agent layer for Workday, where the same rules are enforced in code.

## What's inside

- `SKILL.md` is the skill: the Workday payroll operations, the duplicate check before any input, the rule that an earning or deduction ID is looked up and never guessed, and the output format.
- `example.json` is the metadata file used by the Workday Developer Program gallery.

## How to use it

1. Read `SKILL.md`.
2. Give your agent read tools for the operations it lists, and prepare-only tools for any change.
3. Put an approval step between the proposal and the Workday call.
4. Add the skill to your agent and ask the test questions at the bottom of `SKILL.md`.

## Before you deploy

- **Approval gate**: build the approval step before connecting write access. A payroll input changes what a person is paid and cannot be undone from the skill.
- **Access**: reading and submitting inputs needs payroll input access for the workers involved. Payslips need the Self-Service: Payroll (My Payslips) and Worker Data: Payroll (Payslips) domains. If the account lacks them, the skill reports a refusal.
- **Scope**: reading existing payroll inputs and payslip summaries, looking up earning, deduction and pay group IDs, submitting one input and assigning a pay group. It never suggests an amount and never acts on the requester's own record.
- **Tool names**: map the operations in `SKILL.md` to your platform's tools.
- **Tested how**: on 22 November 2026 the author ran the reads on a Workday development tenant: SOAP Payroll v46.2 `Get_Submit_Payroll_Inputs` returned the tenant's one payroll input, and WQL found the lookups the skill needs (`allEarningsForPayroll` returned 209 earnings with their Workday IDs, `allPayGroups` returned 4 pay groups such as USA Weekly). On an earlier development tenant (12 November 2026) the author created one-time inputs through REST payroll/v2 `POST /payrollInputs` and deleted them again; that is the REST equivalent of `Submit_Payroll_Input`, which itself was not run. The payslip read was refused on this tenant for the test user, so it is untested here, and `Assign_Pay_Group` was not run. Try each write in a non-production tenant first.
41 changes: 41 additions & 0 deletions examples/payroll-input-agent-skill/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
---
name: payroll-input
description: Reads payroll inputs and payslip summaries and prepares payroll inputs or pay group assignments in Workday. Use when HR wants to submit an earning or deduction or assign a pay group. Do not use to suggest an amount, to change your own record, to show full payslip detail, or to undo payroll.
---

# Payroll input

Check for duplicates first, find the real earning or deduction code, then prepare one input.

## Decision

| Request | Workday operation | Notes |
| --- | --- | --- |
| Existing inputs | SOAP Payroll `Get_Submit_Payroll_Inputs` | HR only, same worker and period |
| Payslips | REST common/v1 `GET /workers/{ID}/paySlips` | Date, gross, net and status only |
| Find a code or pay group | WQL `dataSources`, then WQL `data` | Search earning, deduction or pay group |
| Submit an input | SOAP Payroll `Submit_Payroll_Input` | Earning or deduction, needs its Workday ID |
| Assign a pay group | SOAP Payroll `Assign_Pay_Group` | Needs the pay group ID and an effective date |

## Hard rules

- Every change is a proposal. Say it is not done until a person approves it and Workday accepts it.
- Facts and figures come only from Workday reads in this conversation. If a read returned nothing, say it is not available.
- Before submitting an input, read the existing inputs for the same worker and period and warn about anything that looks like a duplicate.
- A payroll input is an earning or a deduction, each identified by a Workday ID you must look up. Never guess an ID or a code.
- Ask for the start date, and the amount with its three letter currency or the hours. The person decides every amount. Never suggest one. Only an adjustment may be negative.
- A pay group assignment needs the pay group's Workday ID and an effective date. This skill cannot show a worker's current pay group; say so.
- Never propose payroll for the person's own record.
- Payslips show date, gross, net and status only. Another person's payslips are private and need organisation-wide reach.
- Payroll cannot be undone from this skill. Tell the person plainly before they approve.
- If a payslip read is refused, the account is missing the Self-Service: Payroll (My Payslips) and Worker Data: Payroll (Payslips) domains. If Workday or your approval step refuses, explain in one plain sentence and never try to get round the refusal.

## Output format

A duplicate check result, then a proposal card with the worker, code, amount and currency or hours, and dates.

## Test questions

- "Is there already a bonus input for Ravi this month?"
- "Submit a 500 USD earning for Ravi from the 1st."
- "Raise my own pay input."
16 changes: 16 additions & 0 deletions examples/payroll-input-agent-skill/example.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
{
"title": "Payroll Input Agent Skill",
"description": "A markdown skill for an agent that reads payroll inputs and payslip summaries and prepares payroll inputs or pay group assignments in Workday.",
"type": "Agent Skill",
"components": [],
"products": [
"Workday SOAP API",
"Workday REST API",
"Workday Payroll"
],
"authors": [
"Daksh-Aneja-Projects"
],
"tutorial": "",
"source": "community"
}
Loading