---
title: "Workday integration inventory report: data source and fields"
description: "Build a Workday integration inventory with the All Integration Systems (Audited) data source: template, schedule, last run and owner fields, proved with WQL."
url: https://kiweely.com/guides/workday-integration-inventory-report-wql
---

# How do I build a Workday integration inventory report with every integration system, its template, schedule, last run and owner?

Use the All Integration Systems (Audited) data source, alias allIntegrationSystemsAudited: one row per integration system, with template, schedule, last run and account fields. A suggested field can be missing because it is a tenant-specific calculated field.

-   **Checked** against Workday on November 16
-   Applies to **Workday WQL, integration systems**
-   6 min read
-   Published November 16
-   By Kiweely

The data source for an integration inventory is All Integration Systems (Audited), WQL alias `allIntegrationSystemsAudited`. It returns one row per integration system, and the fields you want are `systemName`, `integrationTemplate`, `workdayAccount`, `scheduledFutureProcess` and `mostRecentIntegrationEvent`. A field from someone else’s example may be missing in your tenant because it is a calculated field that only their tenant has.

Every call on this page was a read-only WQL metadata or data request against a Development tenant.

## Which data source lists every integration system?

Workday represents every integration as an integration system, whatever built it, and an integration event is created each time one launches. So the inventory is a query over integration systems, with the latest event hanging off each one.

Confirm the alias in your own tenant first. `GET /dataSources/{ID}` for this source returned:

| Property | Value |
| --- | --- |
| Descriptor | All Integration Systems (Audited) |
| Alias | `allIntegrationSystemsAudited` |
| Primary business object | Integration System |
| Built-in prompts | None |
| Supports effective and entry date | Yes |

The description says it “returns one row per integration system”, includes all of them and does not include integration systems that have been deleted. `SELECT COUNT() FROM allIntegrationSystemsAudited` returned 190 in the Development tenant.

A second source, `allIntegrationEvents`, has one row per run instead (48,491 in the same tenant). Use it for run history, not for the inventory itself.

## Which fields answer template, schedule, last run and owner?

`GET /dataSources/{ID}/fields` returned 43 fields. These cover the five columns of the inventory:

| Column | Field alias | Type | What it returns |
| --- | --- | --- | --- |
| Integration system | `systemName` | Text | The system’s name |
| Template | `integrationTemplate` | Single instance | The integration template, such as Cloud Integration Template |
| Type | `integrationType` | Text | Set on only 7 of 190 systems here, so do not rely on it |
| Schedule | `scheduledFutureProcess` | Multi-instance | The scheduled future processes, empty if none |
| Last run | `mostRecentIntegrationEvent` | Single instance | The latest integration event, with its own fields |
| Last completed run | `asOfEntryDateTimeOfLastCompletedIntegrationEvent` | Date | When the latest completed event was entered |
| Account it runs as | `workdayAccount` | Single instance | The Workday account tied to the system |
| Contacts | `contacts` | Multi-instance | Integration System Contact records |
| Created | `createdMoment` | Date | When the system was created |
| Last changed | `lastFunctionallyUpdated` | Date | When it was last functionally updated |

The related fields come back as `{descriptor, id}` objects. To get a status and a time instead of a descriptor string, use braces on `mostRecentIntegrationEvent`.

## What does the inventory query look like?

sql

```
SELECT systemName,
       integrationTemplate,
       workdayAccount,
       scheduledFutureProcess,
       mostRecentIntegrationEvent{status, actualStartDateAndTime},
       createdMoment
FROM allIntegrationSystemsAudited
ORDER BY systemName
```

The response is one object per integration system. A field with no value is left out of the object rather than returned as null. A system that never ran has no `mostRecentIntegrationEvent`, and a system with no schedule has no `scheduledFutureProcess`. Handle a missing key as “empty” when you load the result into a spreadsheet.

A row with a last run looked like this (the system name is replaced):

json

```
{
  "systemName": "Example Outbound Integration",
  "mostRecentIntegrationEvent": {
    "status": {"descriptor": "Completed"},
    "actualStartDateAndTime": "2024-09-09T23:00:00.000Z"
  }
}
```

### How many integrations have each piece of data?

Counts such as these show how complete the inventory will be before you build it. Each is a `COUNT()` with a `WHERE <field> is not empty` filter on the same data source:

| Filter | Systems |
| --- | --- |
| All integration systems | 190 |
| `integrationTemplate` set | 189 |
| `mostRecentIntegrationEvent` set (has run) | 63 |
| `scheduledFutureProcess` set (scheduled) | 14 |
| `workdayAccount` set | 24 |
| `integrationType` set | 7 |
| `contacts` set | 0 |

The one system without a template is the delivered “Workday” system. Grouping by template gave `Cloud Integration Template` for 26 systems and one-off templates for others.

## Why is a suggested field missing in my tenant?

Pasting a field from an example or an AI answer into a query is the usual way to meet “Enter a valid report field. This field is invalid”. For this data source we can show it.

Workday’s published field list for the data source includes a calculated field with the alias `cf_IntegrationSystemTag`. The tenant’s own field list does not. Selecting it returned HTTP 400:

json

```
{"error":"invalid request: WQL error.","errors":[{"error":"Enter a valid report field. This field is invalid: cf_IntegrationSystemTag.","field":"cf_IntegrationSystemTag","severity":"Critical","location":"Invalid SELECT clause"}]}
```

The comparison also ran the other way. The tenant’s list has six fields that were not in the published list, including `referenceIDValue` and `effectivePrimaryReferenceID`, so a list copied from a document can be behind the tenant too.

The reasons, in the order to check them:

1.  **It is a calculated field.** Workday creates a `cf_` alias for every calculated field, delivered or not, and the WQL aliases reference says you can edit the alias. A `cf_` field exists only in tenants that have it.
2.  **The alias is not exact.** Aliases are case-sensitive. `FullName` fails on `allWorkers` where `fullName` works.
3.  **The user cannot reach the field.** A query can only use fields the processing account has permission to access, per Workday’s FROM reference.
4.  **The data source differs.** There are look-alike sources, such as `integrationEvents` and `allIntegrationEvents`, and the field you need may live on the one you did not choose.

The fix is the same each time. Call the fields endpoint for the data source in your tenant, copy the alias from the response, and do not take it from a document.

## Where is the owner of an integration?

There is no field called owner. Two fields stand closest:

-   `contacts` is a multi-instance field of Integration System Contact records. In the Development tenant none of the 190 systems had one, so we could not verify the names of the fields inside it. If your team maintains contacts, `contacts` is the field to select; check its related object’s fields in your own tenant first.
-   `workdayAccount` is the account the integration system runs as. It is set on 24 of 190 systems, and it names a system user rather than a person.

If neither is filled in, the owner is not recorded in the integration system at all. Record it with the contacts, or keep it in a column outside Workday.

## How do I get the schedule of each integration?

`scheduledFutureProcess` is a multi-instance field. Systems that return a value have a scheduled future process, and the braces form `scheduledFutureProcess{process}` returned the process name. In the Development tenant 14 of 190 systems have one. That tells you which integrations run on a schedule and which are launched by hand, by a business process or through an API.

The recurrence, such as daily at a set time, is set on the schedule. Workday’s reference for scheduled processes names the Launch / Schedule Integration task as one of the scheduler tasks where the Run Frequency is chosen. We did not find a field on this data source that returns the frequency, so check the schedule itself for it.

## How do I get the integration system user for each integration, and who can launch it?

Use `workdayAccount` for the account, as above. Who may launch an integration is configured on the integration system’s security; see [who can launch a specific integration](https://kiweely.com/guides/workday-who-can-launch-integration). Integration templates and business process templates are different things, covered in [integration system templates versus business process templates](https://kiweely.com/guides/workday-integration-system-vs-business-process-templates).

## How do I keep the inventory current?

Run the query on a schedule of your own, through the WQL REST API, and keep the result with the date. The `asOfEntryDateTimeOfLastCompletedIntegrationEvent` and `lastFunctionallyUpdated` fields let you spot systems that stopped running or were changed since the last snapshot. A result of a few hundred rows fits in one response, so the 10,000-row page limit does not matter for this report.

Kiweely Vine is an AI agent for Workday that can answer Workday questions and, with the user’s consent, read a connected tenant, which includes listing a data source’s fields and running a query like the one above.

## Frequently asked questions

### Which Workday data source lists every integration system?

All Integration Systems (Audited), WQL alias allIntegrationSystemsAudited. Its description says it returns one row per integration system, includes all of them, leaves out deleted ones and has no built-in prompts.

### Why is the field I was told to use missing from my tenant?

Common causes are a calculated field (a cf\_ alias) that exists only in the tenant that wrote the example, a typo or wrong capitalisation in the alias, or a user without access to that field. In our Development tenant cf\_IntegrationSystemTag is listed in Workday's published field list for this data source but returned 'Enter a valid report field'.

### Where do I find the integration system user for each integration?

The workdayAccount field holds the Workday account the integration system runs as. In our Development tenant 24 of 190 integration systems had one set. The rest have none.

### How do I get the last run of every integration?

Select mostRecentIntegrationEvent{status, actualStartDateAndTime}. It returns the status and start time of the latest integration event for each system, and the field is absent for systems that never ran.

### Can the inventory include the schedule?

It can show which systems have a scheduled future process, with scheduledFutureProcess. The recurrence itself, such as daily or weekly, is set on the schedule through the Launch / Schedule Integration task, so confirm it there.

## Sources checked

-   [Concept: Integration Systems and Events](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/uxa1532597056528.html)
-   [Reference: WQL Aliases](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/ktw1644956621314.html)
-   [Reference: WQL REST API](https://doc.workday.com/admin-guide/en-us/reporting-and-analytics/custom-reports-and-analytics/workday-query-language-wql-/srr1614364076622.html)
-   [Customize Recurrence for Scheduled Processes](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/background-processes/customize-recurrence-for-scheduled-processes.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Who can launch a specific Workday integration, and what permissions does that user need? To launch an integration, a user needs Modify on the Integration: Integration Event domain. To limit that to one integration, grant it through a segment-based security group whose segment holds only that integration. Integrations: EIBs, Integration Build and Integration Debug aren’t needed.](https://kiweely.com/guides/workday-who-can-launch-integration)
-   [### Integration System template vs Business Process template in Workday Orchestrate Use the Workday Integration System template when an integration system launches the work on a schedule or on demand and you need an integration event with messages and files. Use the Workday Business Process template when a step in one business process event should launch it with that event’s data.](https://kiweely.com/guides/workday-integration-system-vs-business-process-templates)
-   [### What is Workday Query Language (WQL), and how do you write and run a query? Workday Query Language (WQL) is Workday’s SQL-like language for reading data from data sources and fields instead of reports. You need the Workday Query Language domain in the System functional area; an external caller also needs an API client with System scope.](https://kiweely.com/guides/workday-wql)
-   [### Why does my Workday WQL query fail? The exact error messages and how to fix each one Workday has no WQL message worded ‘instance set invalid for prompt’. A rejected prompt value returns ‘Invalid Parameter Values for parameter’ or ‘does not meet the restrictions defined for this field’. This page quotes each common error as Workday returned it, with the fix.](https://kiweely.com/guides/wql-error-messages)

### More guides on WQL

[All 31 guides](https://kiweely.com/guides#wql)

-   [Retrieving Eligible Absence Plans and Live Balances for a Worker via Workday APIs](https://kiweely.com/guides/workday-absence-balances-api-eligible-plans-for-worker)
-   [Querying the Workday Worker Directory, Supervisory Hierarchy, and Cost Centers with WQL](https://kiweely.com/guides/workday-worker-directory-org-chart-search-fields-wql)
-   [Querying Open Job Requisitions and Supervisory Org Headcount via Workday Staffing APIs](https://kiweely.com/guides/workday-staffing-api-job-requisitions-open-positions-managers)
-   [Finding Unsubmitted Workday Time Blocks and Project Hours with WQL](https://kiweely.com/guides/workday-project-time-tracking-unsubmitted-hours-wql)
-   [Querying Pending Workday My Tasks and Inbox Approvals via API and WQL](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [Why fileLength on workerDocuments Returns 52 in WQL for Business Process Attachments](https://kiweely.com/guides/wql-workerdocuments-filelength-returns-52)
-   [Paging with POST /wql/v1/data in a PMD Grid When Queries Exceed URL Limits](https://kiweely.com/guides/wql-post-data-endpoint-grid-pagination-url-limit)
-   [Escaping Single Quotes for Multi-Value IN Clauses and Fixing Double URL-Encoded Unicode in PMD WQL](https://kiweely.com/guides/wql-pmd-single-quote-escaping-double-urlencoded-unicode)

### From the blog on WQL

[All posts](https://kiweely.com/blog)

-   [Build vs. Buy a Workday MCP Server: OAuth 2.1, SOAP, WQL, and Twice-Yearly Releases](https://kiweely.com/blog/build-vs-buy-workday-mcp-server-engineering-cost)
-   [What happens after ChatGPT writes your WQL query](https://kiweely.com/blog/after-chatgpt-writes-your-wql)
-   [Answering Executive Span-of-Control and Headcount Questions Live from Workday](https://kiweely.com/blog/executive-org-span-of-control-attrition-questions-live-workday)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
