---
title: "When the Answer Is Chat, a Screen, or a Running Integration"
description: "Use Bridge for chat, Leaf for a screen, and Roots for an integration that keeps running. All three are coming next."
url: https://kiweely.com/blog/when-the-workday-job-is-chat-a-screen-or-an-integration
---

# When the Answer Is Chat, a Screen, or a Running Integration

A Workday question in Claude, ChatGPT, or Gemini points to Bridge. A branded page or phone action points to Leaf. A file or API that runs on a schedule points to Roots. Each product is coming next.

-   By Kiweely
-   November 16
-   8 min read

If someone needs a Workday answer while they are already talking to Claude, ChatGPT, or Gemini, the product is [Kiweely Bridge](https://kiweely.com/bridge). If they need a page, a phone action, or an approval card in the tools they already use, the product is [Kiweely Leaf](https://kiweely.com/leaf). If Workday has to send or receive a file or an API call when nobody is in the conversation, the product is [Kiweely Roots](https://kiweely.com/roots). All three are coming next. None of them is a way to build business processes, reports, or Extend apps inside the tenant. That work is [Kiweely Vine](https://kiweely.com/vine), which is live today, or [Kiweely Nest](https://kiweely.com/nest), which is coming next for the in-house team.

The mistake is to pick the surface you like and then force the job into it. A nightly 834 file is not a chat. A three-button time-off screen is not an integration. A headcount question is not a new portal.

## Match the job, not the vendor category

| What the person is trying to do | Product | Status on its page | What you register or open |
| --- | --- | --- | --- |
| Ask about their own balance, team, pay, or a report they can already open | Bridge | Kiweely Bridge is coming next |  [Register interest](https://kiweely.com/bridge) |
| Open a branded page, approve in chat, or tap one of three actions on a phone | Leaf | Coming next |  [Register interest](https://kiweely.com/leaf) |
| Move changes to payroll, a carrier, identity, finance, or an SFTP partner on a schedule | Roots | Coming next |  [Register interest](https://kiweely.com/roots) |
| Change the tenant itself: a business process, security, a report, an EIB, Studio, or an Extend app | Vine, or Nest for the in-house team | Vine is live today. Nest is coming next |  [Vine](https://kiweely.com/vine), or a [Nest demo](https://kiweely.com/nest) |

Bridge, Leaf, and Roots each say they work without a Workday Extend license, using standard Workday APIs from outside the tenant. Vine is the product that builds Extend apps inside Workday.

## Chat: Bridge

Bridge is for a person who is present and asking. The page’s promise is Workday inside Claude, ChatGPT, and Gemini, for every employee, governed by the Workday and IT team. One MCP connector, no desktop install, on Mac, Windows, the browser, and the phone.

The employee signs in on Workday. Calls use that worker’s own security groups and domains, through a user-delegated API client, not a shared integration system user. Reach on the page is REST, live WQL discovery, SOAP reads, custom RaaS reports, and tasks an admin has turned on. The tenant starts read-only. A write, once enabled, stops for a browser card that shows now and after, outside the chat. Payloads are not stored. The page describes sealed grants and logs that keep time, tenant, tool, status, and latency.

Use Bridge when the useful result is an answer or a confirmed change for that person. A manager asking who is out, an employee asking what their balance will be, an HR partner asking a question their role already allows: that is chat.

Do not use Bridge as the payroll interface. Chat is the wrong place for a file that must leave every night, with carrier rules and a rerun of the rows that failed. That is Roots. Do not use Bridge when the workforce needs a layout: a calendar, three buttons, or a form in their language. That is Leaf.

Company pricing is published even though Bridge is coming next: $499, $1,499, or $3,999 a month by employee band, a quote above 20,000 employees, unlimited calls, Production and non-production tenants included. One person on a personal Workday developer tenant is free. A company still registers interest. The product is not a live rollout.

## A screen: Leaf

Leaf is for a layout. The page’s line is any employee experience, in your design, on live Workday data, in the browser, in Teams, and on the phone. You connect the tenant once with one Workday API client and describe the screen. Leaf reads the tenant’s processes, plans, and security before it designs. You publish. Nothing reaches employees until you say so.

The screens the page names:

-   Employee portals that put pay, time off, benefits, and onboarding on one page.
-   Leave, expense, and timecard approvals in Teams, Slack, DingTalk, or Lark.
-   Manager views for headcount, open roles, and who is out.
-   Frontline apps with three large actions on a phone, in the worker’s language.

Employees install the Kiweely Leaf phone app once from the App Store or Google Play. That app is not the live Kiweely phone app that follows Vine and Nest. They sign in with Workday, then a face or a fingerprint, and land in your company’s space. A web app your developers host can be a tile beside the screens Leaf builds. Workday calls for those tiles still run as the signed-in employee.

Data on the page: read on demand, gone when the request ends. Kiweely stores layouts, branding, and connection settings, not worker records, compensation, or payroll. There is no price and no date on the Leaf page. The interest form asks which channel you need first: browser, DingTalk or Feishu or Lark, Teams or Slack, the Leaf phone app, several, or not sure yet.

Use Leaf when someone must see and tap. A warehouse worker will not paste a question into a desktop chat. A manager who never opens Workday still needs a headcount card. Use Bridge instead when the same person is already in Claude, ChatGPT, or Gemini and the answer is a sentence. Use Roots when the outcome is a file or an API call to another company, not a screen.

## A running integration: Roots

Roots is for the systems around Workday. The page’s line is a new integration platform outside the tenant. Agents design, build, test, and maintain every integration with you. You describe what goes where and when. Roots reads your business processes and fields and the other system’s rules, builds the integration, and tests it on Sandbox before Production. You switch it on.

The destinations the page names: ADP, UKG, and in-country payroll; 834 files and carrier APIs; Okta, Microsoft Entra ID, and ServiceNow, joined on day one and closed on the last; NetSuite, Snowflake, and SFTP files partners still want. Both directions.

The run is code that was tested. Agents are not in the path of each night’s rows. They design, build, test, and fix that code. You pick the repair rule per integration. Payroll, benefits, and tax wait for your approval after the fix is proved on Sandbox with the rows that failed. Directory and reporting feeds can be fixed, tested, and turned back on, with a note to the owner. Every change shows before and after and goes back in one step.

Nothing is kept after a run except times, counts, and outcomes. Each integration has its own API client, scoped to what it reads. Hosting is Kiweely’s cloud or yours: AWS, Azure, or Google Cloud. Claude, ChatGPT, and Gemini can reach Roots over MCP, as the person asking, to check a run, start one, or ask for a change. That is a question about the integration. It is not a substitute for Bridge, which is how employees ask about their own Workday data.

Roots is not EIB or Studio inside the tenant. Vine, live today, still builds Studio integrations in your own Studio when that is where the integration should live. Nest, coming next, has a technical specialist who covers integrations, Studio, and Extend as part of the in-house team. Roots is the outside platform that runs the integration and drops the records when the run ends. Its page has no price and no date. Register interest and name the integrations that cost the most.

## Three failures

**The nightly file stuffed into chat.** Someone exports a spreadsheet because a carrier or a payroll vendor is waiting. Bridge can answer from live data for a person who is signed in. It is not the schedule, the 834, or the rerun of rejected rows. That job is Roots, still coming next, or the integration you already run in Studio or an iPaaS until Roots exists.

**The portal built so people can ask one question.** A full employee site is the wrong tool for “how much PTO will I have in December?” Bridge is the chat-shaped answer, and it stays inside the employee’s own Workday access. Build a Leaf screen when the task is a form, a calendar, or a button.

**The integration used as the employee’s front door.** An integration system user, or a client scoped to one feed, is the wrong identity for a manager’s headcount question. Leaf and Bridge both say every workforce call runs as the signed-in person. Roots says each integration has its own API client scoped to what that integration reads. Keep those identities apart.

## If the job is inside the tenant

Chat, screens, and running integrations all assume Workday already has the fields, reports, and processes they read. Creating those is Vine: ask in plain words, watch the work, approve the write. Nest is the coming-next version of that for an in-house director who wants eleven specialists, tickets, routines, and a recorded approval before Production. Do not register for Bridge, Leaf, or Roots expecting them to redesign a business process.

## Frequently asked questions

### Can one company register for more than one?

Yes. The products do not require each other. Bridge’s page says it needs neither Vine nor Nest. A company can want chat for the office, a phone screen for the floor, and a payroll file at night. Register interest on each page that matches a job you actually have. Vine is the one you can use now.

### What if we already have Studio integrations?

Keep them if they are the system of record for that feed. Vine is the live product that builds and tests Studio integrations in your own Studio. Roots, coming next, is a different place for the integration to live: outside the tenant, tested on Sandbox, with nothing kept after the run. Moving a feed is a choice, not a step these pages require.

### Which one has a price today?

Bridge publishes company bands and a free personal developer tenant. Leaf and Roots publish no price. All three are coming next, so the company step on each page is interest, not an order button.

## Read next

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

-   [November 15 ### Personal AI Plus Shared ISU Credentials: The Compound Workday Failure Mode](https://kiweely.com/blog/personal-ai-plus-shared-isu-compound-failure)
-   [November 15 ### BYO API Keys on a Workday Consultant Laptop: Who Is the Controller?](https://kiweely.com/blog/byo-api-key-workday-consultant-laptop)
-   [November 15 ### Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)

### More guides on Integrations and APIs

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

-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)
-   [Which Object Transporter migration paths does Workday support?](https://kiweely.com/guides/workday-object-transporter-migration-paths)
-   [Sandbox to Production Object Transporter checklist](https://kiweely.com/guides/workday-object-transporter-sandbox-to-prod-checklist)
-   [SOAP vs RaaS Basic Auth vs OAuth: which Workday credentials do I use?](https://kiweely.com/guides/workday-soap-vs-raas-vs-oauth-authentication)
-   [How do I set an Integration System Security Group for an Integration System User?](https://kiweely.com/guides/workday-issg-for-integration-system-users)
-   [Why does Object Transporter block single-instance migration from Production?](https://kiweely.com/guides/workday-ox-production-single-instance-limits)
-   [Object Transporter or Configuration Change Tracker: which moves Workday config?](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)

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

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

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