---
title: "Inventory Every Workday Integration System, Schedule, and…"
description: "Build a list of every Workday integration system, its schedule, its security, and who gets told when it fails."
url: https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners
---

# Inventory Every Workday Integration System, Schedule, and Owner

Workday represents every integration as an integration system, with a schedule, a business process, an integration system user, and notifications. There is no single owner field. This is the inventory to take from those tasks.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   5 min read
-   Published November 16
-   By Kiweely

You cannot retire, move, or even explain an integration you cannot name. Workday already has the list. It does not have a column called Owner. [Integration systems](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/uxa1532597056528.html) are the rows. Security, notifications, and the integration system user are how you fill in the person.

Workday represents every integration, whatever built it, as an integration system. A Studio deploy registers a new integration system for every transport in that integration, so one Studio project can be several rows. Enterprise Interface Builder, connectors, and Studio all show up in the same shape: something you can launch, schedule, and find afterward in Process Monitor.

## The columns, and the task that fills each one

Open **View Integration System** for the row, then the related actions below. Do this in the tenant where the integration actually runs. Workday refreshes Sandbox and Sandbox Preview from Production every week, so the inventory of what runs for real belongs in Production. [What to recheck after that refresh](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes) is a separate pass.

| Column | Where Workday keeps it | What to write down |
| --- | --- | --- |
| Name | The integration system | The name people search. Studio can produce more than one system per assembly, one per transport. |
| How it starts | Triggers on the integration system | Manual, a subscription, an API, a schedule, or a business process. An integration business process can also start from View Integration System, from Launch / Schedule Integration, or as a step on another process, such as after Complete Form I-9. |
| Schedule | Launch / Schedule Integration | Frequency, time, time zone, priority, catch-up, and the end of the recurrence. Details below. |
| Who may launch it | Security on the integration system | The security that can launch it, and the rights it has while it runs. |
| Account it runs as | The integration system user on the service steps | Service steps run as that user. A security error in the event names the missing domain. |
| Who is told | Integration System > Configure Integration Notifications | A user-based security group, the inbox of the worker who launches it, and any email addresses configured on the notification. This is the closest Workday gets to an owner. |
| What it sends | Configure Integration Attributes, and the delivery or retrieval step | Attributes are tenanted values: a type of data, or a behavior such as whether prior values are included. Some require a value before launch. Delivery is a separate step. |
| File name | Configure Integration Sequence Generators | A sequence of date, time, sequence, and fixed text. If a sequence generator is configured, Workday ignores the static Output Filename attribute. |
| Last outcome | Process Monitor, integration event | Each launch has an integration event id. Status messages are written onto that event. |

There is no owner field on the pages Workday publishes for these tasks. Put a name in your inventory only after you have read the notification security group and agreed which person carries it. A security group with twelve members is not an owner until someone is.

## Schedules worth copying exactly

[Launch / Schedule Integration](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html) is not a single cron box. Record the option, not the word “daily.”

| Run frequency | What you must capture |
| --- | --- |
| Run Now | No recurrence. Someone launched it, or a process did. |
| Run Once in the Future | Start date, time, time zone. |
| Minute | Interval of 5, 15, 30, or 45 minutes, plus start and end time and the date range. The start has to be in the future when you set it. |
| Hourly | An interval from 1 to 12 hours, start and optional end time, time zone, date range. |
| Daily | Every weekday, or every n days. Start time, time zone, start date, end date. |
| Weekly | Every n weeks, which weekdays, time, time zone, dates. |
| Monthly | Which months, and either a day number, last day of the month, or a weekday such as first Monday. Time, time zone, dates. |
| Dependent | The other integration or alert, and the status it waits for, such as Completed or Completed with Warnings. |
| Custom | The explicit list of dates and times. |

Also copy priority (Critical, High, Normal, or Low) and Catch Up Behavior (None or Run Once). Catch-up is what happens when a maintenance window skips the slot. A partner who expected a file during that window needs this written down. See [overnight SFTP failures](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures).

One limit is easy to miss. On the range of recurrence, a scheduled integration runs for at most five scheduled instances after the end of the following calendar year. An end date that looks distant still stops.

## Business process, then the person

If the integration system has no business process of its own, it uses the default Integration Process Event: Initiation, then Service - Fire Integration. The file is not delivered unless someone added Service - Document Delivery. Retrieval is Service - Document Retrieval, and it has to come before Fire Integration. When an Integration step on that process fails, the parent process stops. That is documented behavior, so the inventory should say whether this system is chained from another.

Search `bp:` plus the integration name to find a definition that already exists. After a system-specific process exists, Workday says to create further versions only through Business Process > Create, Copy, or Link Definition.

Notifications on the business process fire from the final status. The connector course also warns that the default email template links to the event and its files, and that Workday does not recommend attaching the integration files to the email. If your inventory’s “owner” currently receives the full file by email, that is a finding, not a convenience.

## How to use the list

Sort it three ways. By schedule, so two payroll files are not five minutes apart on the same integration system user. By notification group, so you can see the integrations nobody is told about. By transport, so the SFTP endpoints, the Studio systems, and the ones with no delivery step are obvious.

That list is the input to a later decision: keep the integration in Workday, or rebuild it outside the tenant. [Kiweely Roots](https://kiweely.com/roots) (coming next) is aimed at the second. It is outside the tenant, it uses standard Workday APIs, and you describe the integration instead of maintaining the Studio archive. Register interest and attach the count of systems that have a schedule and no notification group. Roots is not a report inside View Integration System, and it is not available to run this inventory for you today.

## Sources checked

-   [Concept: Integration Systems and Events](https://doc.workday.com/admin-guide/en-us/workday-studio/studio-fundamentals/uxa1532597056528.html)
-   [Configuring Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/configuring-connectors.html)
-   [Integration Business Process Guidelines](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/business-processes-guidelines/integration-business-process-guidelines.html)
-   [Workday Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-connectors.html)

## Related guides

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

-   [### Workday SFTP File Contracts, PGP, and Overnight Failures Partners still collect a named file over SFTP. Workday’s delivery service, sequence generators, and PGP filename rules decide whether that file is the one they can decrypt at 2 a.m.](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [### Recover Workday Integration Attributes After a Sandbox Refresh Workday refreshes Sandbox and Sandbox Preview from Production every week. App attributes are per environment, refresh tokens are per tenant, and Workday does not publish a field list for classic integration attributes.](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)
-   [### Workday Cost Centers and Workers to NetSuite After a Reorg Workday effective-dates cost center membership through supervisory defaults, worker assignments, and related worktags. NetSuite departments and employees only change when your integration writes the REST records Oracle documents, organizations first.](https://kiweely.com/guides/workday-cost-centers-workers-to-netsuite)

### More guides on Integrations and APIs

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

-   [Sandbox Checklist Before AI Chat, Custom Screens, or Integration Platforms](https://kiweely.com/guides/sandbox-checklist-before-ai-chat-screens-or-integrations)
-   [Security Review Packet: Pass-Through UI, AI Chat, and Zero-Retention Integrations](https://kiweely.com/guides/security-review-packet-pass-through-ui-chat-and-integrations)
-   [What Is an EIB in Workday? How to Build, Template and Load One](https://kiweely.com/guides/what-is-an-eib-in-workday)
-   [How do you move an acquired company into the acquirer’s Workday tenant?](https://kiweely.com/guides/workday-move-acquired-company-into-acquirer-tenant)
-   [Who can launch a specific Workday integration, and what permissions does that user need?](https://kiweely.com/guides/workday-who-can-launch-integration)
-   [Write Your First Workday Studio AUnit Tests Before Changing the Assembly](https://kiweely.com/guides/write-first-workday-studio-aunit-tests)
-   [How a Workday Sandbox Refresh Affects Registered API Clients and Redirect URLs](https://kiweely.com/guides/workday-api-client-disabled-tenants-sandbox-refresh-impacts)
-   [Register API Client vs. Register API Client for Integrations in Workday](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)

### From the blog on Integrations and APIs

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

-   [Kiweely builds and runs a Workday Outbound EIB from one request](https://kiweely.com/blog/workday-outbound-eib-integration-built-and-run)
-   [How an admin sets up the Workday API client for Kiweely Bridge](https://kiweely.com/blog/kiweely-bridge-ai-admin-api-client-setup)
-   [AI-Maintained Benefits Feeds and Hand-Owned Cloud Connect Maps](https://kiweely.com/blog/maintained-benefits-feeds-versus-hand-owned-cloud-connect-maps)

## 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.
