Skip to content
KiweelyKiweelyKiweely

Nothing Kept After a Run: Zero-Retention Workday Integrations

Kiweely Roots, coming next, reads Workday data, sends it, and deletes it inside the run. The record left behind is the time, the count, and the outcome, and each integration has its own Workday API client.

  • By Kiweely
  • 4 min read
On this page

Payroll files, benefit elections, and bank details are the records a security review asks about first. The usual integration stack keeps them anyway: the file on a server, the row in a log, the payload in a vendor ticket. Kiweely Roots (coming next) is built the other way. Workday data passes through and is gone when the run ends.

The published rule is short. Held only in flight: read, sent, and deleted inside the run. The record of the run is times, counts, and outcomes, never the records themselves. Each integration has its own Workday API client, scoped to what that integration reads.

What “nothing kept” has to mean

A zero-retention integration is a pipeline with no place to sit down. The worker row is in memory long enough to map and send. When the run ends, that row is not in a database, a bucket, or a debug archive belonging to the integration.

Question a review asks What the Roots page commits to
Question a review asksWhere do the records go? What the Roots page commits toThrough Roots and on to the system you named.
Question a review asksWhat is left afterward? What the Roots page commits toTimes, counts, and outcomes.
Question a review asksHow long is a row held? What the Roots page commits toFor the run. Read, sent, and deleted inside it.
Question a review asksHow much of Workday can the integration see? What the Roots page commits toIts own API client, scoped to what it reads.
Question a review asksDoes an agent touch the live file? What the Roots page commits toNo. The integration runs as tested code. Agents design, build, test, and fix that code. They do not sit in the path of the data.

That last line is the one teams mix up. “AI builds the integration” is not “the model reads payroll on every run.” The run is the code you already tested. The agent is how that code gets written and how a break gets a fix.

What you still have to design

Zero retention is not a reason to skip the controls around the run.

Scope the client. Least access is per integration. A headcount feed does not get the domains a payroll file needs. A benefits file does not get finance. The Roots page states the pattern: one API client, scoped to what that integration reads. The domains themselves are still your Workday security policy.

Decide who may fix a break. You choose, per integration, whether a fix ships on its own or waits. Payroll, benefits, and tax are the strict set: the fix is proven on Sandbox with the rows that failed, then it waits for your approval. Directory and reporting feeds can be fixed, tested, and turned back on, with a note to the owner afterward. You can move an integration between those two at any time.

Show the change before it lands. Every change shows what it does to the data, and goes back in one step. For a file that failed, that is the difference between the rows the partner rejected and the rows the fix would send. The proof runs on Sandbox. Production does not receive it until you say so, and a payroll change stays in the “wait for approval” set because it touches payroll.

Keep the run record useful. Times, counts, and outcomes are enough to answer “did last night’s file go, and how many rows.” They are not enough to reconstruct a worker. If a later audit needs the file itself, that copy has to live in the system you sent it to, or in a store you run on purpose. Roots does not become that store.

What the page does not specify

The Roots page does not name an encryption algorithm, a region list, a log schema, or a retention period in days. It does not say the Sandbox used for a fix is exempt from the same rule. It says the fix is proven there with the rows that failed, and that nothing is kept after a run. Treat the failed rows as part of that run and that Sandbox proof, not as a warehouse you can query next quarter.

Hosting follows the same line: Kiweely’s cloud, or your AWS, Azure, or Google Cloud. Which of those a review will accept is a separate choice. The retention sentence does not change with the host. The data is still gone when the run ends.

Register interest at Kiweely Roots and say which file you cannot keep a copy of. Roots is coming next. There is no order button and no price on the page.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.