Your HRIS team has already built, audited, and reconciled the custom Workday reports that define how your company counts headcount, attrition, open requisitions, and budget variance. Instead of recreating years of Workday calculated fields from scratch for AI assistants, enabling selected advanced reports as Reports as a Service (RaaS) under user-delegated OAuth turns them into live, governed tools inside Claude, ChatGPT, and Gemini.
Why Raw REST Endpoints Alone Miss Your Real Business Definitions
Out-of-the-box Workday REST endpoints (/staffing/v7, /common/v1) return raw Workday objects, not your company’s agreed operational definitions. Ask two executives “What is our active billable headcount in North America?” and the real answer in your tenant almost certainly depends on custom report logic your HRIS and Finance teams aligned on years ago:
- Excluding contingent workers in specific vendor types, interns, and workers on long-term unpaid leave via custom Filter and Subfilter rules.
- Resolving multi-level cost-center rollups through
Lookup Hierarchy RolluporLookup Related Valuecalculated fields. - Pulling contextual constants from a Global business object or computing percentile bands—two capabilities Workday supports in RaaS custom reports that WQL explicitly does not support.
- Maintaining a persisted, audited report definition in Workday so Finance knows nobody silently rewrote the headcount formula inside an AI prompt.
When an AI connector can only call preset self-service skills or generic REST endpoints, every answer diverges slightly from the numbers on the CFO’s Monday dashboard. Exposing the exact custom report as a governed RaaS tool guarantees identical numbers.
WQL vs. RaaS for AI Tool Calls: Choosing the Right Tool per Prompt
As Workday’s Reference: WQL and RaaS Comparisons documents, WQL and RaaS complement each other rather than competing:
| Capability | Live Workday WQL | Custom Report via RaaS (?format=json) |
|---|---|---|
CapabilityAd-hoc GROUP BY dimensions |
Live Workday WQLYes (SELECT location, count(worker) ... GROUP BY) |
Custom Report via RaaS ( ?format=json )Not supported dynamically (requires matrix/summary report definition) |
CapabilityResult pagination (LIMIT / OFFSET) |
Live Workday WQLYes (paginate up to 10,000 rows per page) | Custom Report via RaaS ( ?format=json )Not supported (returns full filtered extract; narrow via prompts) |
| CapabilityGlobal business object fields & percentiles | Live Workday WQLNot supported | Custom Report via RaaS ( ?format=json )Supported natively |
| CapabilityWorkday report definition audit trail | Live Workday WQLQuery string lives outside Workday | Custom Report via RaaS ( ?format=json )Persisted and audited inside Workday’s audit framework |
| CapabilityTenant-to-tenant portability | Live Workday WQLWorks across tenants without migrating a report | Custom Report via RaaS ( ?format=json )Report must exist (or be migrated via Object Transporter) in target tenant |
| CapabilityIssuing-user security enforcement | Live Workday WQLHonors object and data-level security of token owner | Custom Report via RaaS ( ?format=json )Honors report sharing + constrained org/field security of token owner |
The best AI architecture uses both: WQL for flexible ad-hoc exploration and pagination, and RaaS for curated, calculation-heavy institutional reports.
How to Prepare a Custom Report for Safe User-Delegated AI Access
Turning an existing Workday advanced or search report into an AI-ready RaaS endpoint takes five deliberate checks in Edit Custom Report (secured by the Custom Report Creation or Manage: All Custom Reports domains in the System functional area):
1. Enable Web Service Output on the Advanced Tab
Open the report in Edit Custom Report, switch to the Advanced tab, and scroll to Web Services Options:
- Check Enable As Web Service.
- Review the generated Namespace and keep it stable (changing a RaaS Namespace later breaks callers until refreshed).
- Keep Optimized for Performance checked on indexed data sources wherever non-indexed fields are unnecessary so interactive AI prompts return in milliseconds.
2. Add Targeted Prompts to Bound Payload Size
Because RaaS does not paginate with LIMIT and OFFSET, never expose an unprompted 50,000-row transaction dump to an LLM context window. On the Prompts tab, expose clean filter parameters—such as Supervisory_Organization, Effective_Date, Location, or Include_Subordinate_Organizations—and verify each Label for Prompt XML Alias.
When invoked as REST JSON, Workday binds single-instance WIDs using %21WID= (!WID=):
GET /ccx/service/customreport2/{tenant}/{owner}/Organization_Headcount?Organization%21WID=cb550da820584750aae8f807882fa79a&Include_Subordinate_Organizations=1&format=json HTTP/1.1
Authorization: Bearer <user_delegated_oauth_token>3. Share the Report with Authorized Constrained Security Groups
Custom reports are private to their owner by default. On the Share tab, select Share with specific authorized groups and users (for example, Manager, HR Partner, and Cost Center Manager).
Remember Workday’s report-sharing rule from Security for Administrators: a security group can only be selected on the Share tab if that group holds domain permissions for both the report’s Data Source and Data Source Filter.
4. Never Call Employee-Facing RaaS Tools Through an ISU
In outbound EIBs or batch data-warehouse pipelines, teams run RaaS URLs under an Integration System User (ISU). If you wire an AI assistant to an ISU, a line manager asking a question could receive rows from every department unless you reinvent Workday’s entire security model outside Workday.
Instead, authenticate the MCP connector via Register API Client using Authorization Code Grant with PKCE. Look at what Workday does automatically when two different employees run the exact same RaaS report with their own OAuth tokens:
- Constrained
Managerpersona: Workday returns only the rows inside their assigned Supervisory Organization (for example, 8 direct reports) and omits columns whose security domains the manager lacks (such asNational_IDorEmergency_Contacts) or restricts self-only constrained fields. - Unconstrained
HR PartnerorControllerpersona: Workday returns all 450 authorized organization rows—while your MCP governance layer can still strip sensitive PII fields in RAM before passing the JSON summary to Claude or ChatGPT.
5. Watch Filter-Field Security Errors
One classic Workday RaaS pitfall catches teams during rollout: if a custom report’s Filter or Subfilter tab evaluates a report field that a Manager security group has zero domain access to, Workday throws a field-access error when that manager runs the report—even if that field is not on the Columns tab! Always test shared RaaS reports across real constrained roles before publishing them to your workforce.
Publishing RaaS Reports to Claude, ChatGPT, and Gemini with Kiweely Bridge
Kiweely Bridge, which is coming next, turns your existing web-service-enabled Workday custom reports into first-class MCP tools alongside Workday REST, live WQL, and SOAP reads:
- Zero code wrappers: Admins pick which RaaS reports to publish in the Bridge policy; the AI admin agent inspects prompt XML aliases, data source permissions, and output columns in Sandbox automatically.
- Per-employee OAuth + RAM field redaction: Every RaaS execution runs under the signed-in employee’s sealed AES-256-GCM Workday token, strips admin-blocked columns in memory, and writes zero report rows to disk or logs (see Bridge security).
- Role-boundary verification before go-live: Test how each RaaS tool responds as an Employee, Manager, and HR Partner in Sandbox—catching missing data source filter permissions or filter-field errors before any employee asks in Claude, ChatGPT, or Gemini.
- Flat company pricing: Included with unlimited calls across Production and all Sandbox tenants ($499/mo up to 1,000 employees, $1,499/mo for 1,001–5,000, $3,999/mo for 5,001–20,000, or free for one person on a personal Workday developer tenant). And if you want those same RaaS reports rendered as clean visual dashboards or mobile portals rather than chat answers, Kiweely Leaf (coming next) builds pass-through screens on them without a Workday Extend license.
Frequently asked questions
Does enabling a Workday custom report as a web service (RaaS) make it public?
No. Workday restricts external RaaS links strictly to authenticated tenant users who hold both report sharing access and domain permissions for the underlying data source, data source filter, and report fields.
When should an AI connector call a RaaS report instead of WQL?
Use RaaS when the answer depends on Global business object fields, percentile aggregations, audited persisted report definitions, or multi-layered calculated fields and subfilters your HRIS team has already validated with Finance and HR.
Why shouldn't RaaS reports for AI chat run under an Integration System User?
Running RaaS as an Integration System User returns unconstrained company-wide rows. Calling RaaS with each employee's user-delegated OAuth token ensures a constrained Manager sees only their own Supervisory Organization's rows and permitted columns.