Skip to content
KiweelyKiweelyKiweely

Embedding Live Workday Time Off, Pay, and Approvals Inside DingTalk, Feishu, and Lark

Global enterprises embed live Workday self-service in DingTalk, Feishu, and Lark via HTML5 mini-apps that exchange super-app SSO for per-worker Workday OAuth 2.0 tokens—rendering balances, payslips, and approvals with zero HR data stored outside Workday.

  • By Kiweely
  • 6 min read
On this page

Global Workday customers embed live time off, payslip summaries, and manager approvals inside DingTalk, Feishu, and Lark by publishing a lightweight HTML5 workplace application on the super-app’s Workbench and wiring it directly to Workday’s OAuth 2.0 Authorization Code Grant (Register API Client). Every screen read and submission runs live under the signed-in employee’s own Workday security groups, keeping zero HR records, compensation rows, or National IDs stored outside the Workday tenant.

Multinational companies standardized on Workday from North American or European headquarters routinely hit an operating wall across Greater China, Singapore, Japan, and Southeast Asia. Corporate IT deploys Workday expecting employees to bookmark a browser URL or install the standalone Workday mobile app, while regional teams run their entire workday—chat, calendar, attendance check-ins, expense receipts, and procurement sign-offs—inside DingTalk, Feishu, or Lark. Because Workday Everywhere targets Microsoft Teams and Slack rather than Asian workplace super-apps, HRIS teams are left choosing between low employee adoption, manual HR helpdesk entry, or risky local middleware databases.

Three Ways Enterprises Connect DingTalk, Feishu, and Lark to Workday

When regional IT teams ask to put Workday actions on the DingTalk or Feishu Workbench, most integration proposals fall into one of three architectures. Only one preserves Workday’s security model and avoids creating a shadow HR database under local data-residency scrutiny.

Architecture Pattern How Authentication Works Where HR Data Lives Security & Maintenance Reality
Architecture Pattern1. Synced Local Middleware + ISU How Authentication WorksSuper-app user_id checked against a synced SQL table; calls Workday via one Integration System User (Register API Client for Integrations). Where HR Data LivesReplicated worker profiles, org hierarchies, and leave balances stored in a regional cloud database. Security & Maintenance RealityHigh risk. Rebuilds Workday constrained security in custom code; creates cross-border PII storage audits and sync lag.
Architecture Pattern2. Deep Links Out to Workday Browser How Authentication WorksTile on Lark/DingTalk Workbench opens the mobile system browser to Workday’s standard web UI. Where HR Data LivesInside Workday only. Security & Maintenance RealityPoor adoption. Forces full SAML re-login loops on mobile webviews and drops workers into dense desktop-style menus.
Architecture Pattern3. Stateless Pass-Through Web App + User OAuth How Authentication WorksSuper-app container completes corporate IdP SSO into Workday OAuth 2.0 Authorization Code + PKCE (Register API Client). Where HR Data LivesZero HR data at rest. Responses stream through memory for the active request only. Security & Maintenance RealityProduction grade. Enforces each worker’s exact Workday domains (Self-Service: Time Off, Self-Service: Pay) with native mobile UX.

How the Super-App SSO to Workday OAuth Handshake Works

DingTalk, Feishu, and Lark all provide an enterprise Workbench (Workplace) container capable of rendering HTTPS web applications and passing single sign-on context. To bind that session to Workday without ever sharing an integration password or storing Workday credentials:

  1. Workbench Launch: The employee taps the company’s Time Off & Pay tile inside Feishu, Lark, or DingTalk on iOS, Android, or desktop.
  2. Corporate IdP Federation: If the worker does not yet hold an active sealed OAuth session, the container initiates an OAuth 2.0 Authorization Code + PKCE redirect to Workday’s authorize endpoint (/authorize).
  3. Silent SAML/OIDC SSO: Workday delegates authentication to the enterprise Identity Provider (Okta, Microsoft Entra ID, Ping, or an enterprise IdP federated with Feishu/DingTalk). If Edit Tenant Setup - Security has the corporate IdP configured with matching Authentication Policy rules, the employee completes SSO without typing a separate Workday password. (Watch out for SAML redirect loops on external OAuth endpoints when mobile user-agent policies differ from desktop browser policies.)
  4. Per-Worker Bearer Token: Workday issues an authorization code that exchanges for a user-delegated access token scoped strictly to the API client’s Functional Areas (for example, Absence, Pay, Staffing, and Tenant Non-Configurable) intersected with that specific employee’s Workday security groups.
http
GET /ccx/api/absenceManagement/v5/{tenant}/balances?worker=3aa5550b7fe348b98d7b5741afc65534&effective=2026-12-31 HTTP/1.1
Authorization: Bearer <employee_delegated_access_token>
Accept: application/json

Because the bearer token belongs to the signed-in worker—not an Integration System User—an employee in Shanghai or Singapore cannot view another worker’s balance or payslip even if someone tampers with query parameters in a proxy debugger. Workday’s own security engine rejects unauthorized object IDs with 403 Forbidden.

Designing High-Frequency Screens for Super-App Webviews

Putting every Workday worklet inside a chat app defeats the point. In regional rollouts, three self-service workflows account for the vast majority of daily employee and manager touches:

1. Localized Time-Off Balances and Requests

In Workday’s standard UI, requesting statutory annual leave, sick leave, marriage leave, or childcare leave often requires navigating Absence -> Request Absence, selecting date ranges on a calendar grid, picking among similarly named Time Off types, and checking Balances in a separate pane to understand projected balances as of a future date.

Inside a Feishu or DingTalk screen, a single mobile view combines:

  • Live Plan Cards: Calling GET /absenceManagement/v5/balances for today and the selected request end date so workers immediately see hours vs. days (critical in APAC countries where statutory leave tracks in Days while shift Plans track in Hours).
  • Attachment Support for Medical Certificates: Statutory sick leave in China, Singapore, and Malaysia frequently requires uploading a clinic note (Maintain Attachments for Business Process) before Request Time Off routes to the manager or local HR Partner.
  • Native Language Labels: Presenting localized plan explanations in Simplified Chinese, Japanese, or Korean without forcing a tenant-wide rename of underlying Workday reference IDs.

2. Mobile Payslip Summaries Behind Re-Authentication

Employees in mobile-first markets expect to check monthly net pay, social insurance contributions, housing fund deductions, and tax withholdings from their phone on payday. Rather than emailing encrypted PDFs—which linger forever on personal devices—an embedded pass-through screen queries Workday Payroll read endpoints or a worker-scoped RaaS/WQL summary under the Self-Service: Pay domain.

Nothing is cached by the web host. The breakdown renders over TLS in memory, and closing the DingTalk or Lark webview clears the DOM state completely.

3. Inline Manager Approvals Without Email Clutter

Managers operating inside Lark or Feishu rarely monitor traditional email inboxes for Approval by Manager alerts. When a direct report submits leave, an overtime request, or an expense report:

  • A webhook or lightweight polling notification posts an actionable card into the manager’s Lark/Feishu bot thread without exposing sensitive leave reasons in the chat preview.
  • Tapping Review opens the embedded approval sheet, calls Workday’s inboxTasks and businessProcess/v1/eventSteps endpoints alongside team absence context, and posts /eventSteps/{ID}/approve or /deny with required comments directly back to Workday.

Cross-Border Privacy Compliance (PIPL, PDPA, APPI) Without a Regional HR Database

Data privacy officers reviewing APAC HR tools—under China’s Personal Information Protection Law (PIPL), Singapore’s PDPA, or Japan’s APPI—focus immediately on data processors that persist employee records. Traditional employee portals and enterprise chatbots copy worker directories, reporting lines, and historical requests into a vendor database, triggering cross-border transfer assessments, encryption-at-rest audits, and retention-purge workflows.

A stateless pass-through layer changes that security conversation completely:

  • Workday remains the sole database. If your company has already completed its regulatory filings and security controls for Workday itself, the UI layer adds zero persistent PII tables.
  • No static integration keys. Revoking a terminated worker’s corporate SSO and running MaintainWorkday Account / token revocation immediately cuts off access through DingTalk, Feishu, and Lark.

How Kiweely Leaf Delivers Super-App Workday Screens

Building and maintaining custom OAuth PKCE plumbing, token refresh handling, WQL pagination, and twice-yearly Workday API release updates for DingTalk, Feishu, and Lark usually requires a dedicated full-stack engineering squad.

Kiweely Leaf (coming next) lets HRIS administrators build and publish custom employee portals, manager views, and chat approval screens in plain English—without writing frontend code and without buying a Workday Extend license. AI agents inspect your live Workday tenant’s absence plans, business processes, and security domains, wire the exact Workday REST, WQL, RaaS, and SOAP calls, and host the resulting experience as a stateless pass-through layer with zero employee HR data stored at rest. Screens built in Kiweely Leaf open directly inside DingTalk, Feishu, Lark, Microsoft Teams, or Slack, in any browser at your company’s own web address, or inside the Kiweely Leaf iOS and Android app.

Frequently asked questions

Does Workday ship a native connector for DingTalk, Feishu, or Lark?

No. Workday delivers packaged Workday Everywhere apps for Microsoft Teams and Slack, not for DingTalk, Feishu, or Lark. Global companies serve those workplace platforms by hosting HTML5 web views or mini-apps backed by standard Workday REST, WQL, RaaS, and SOAP APIs.

Can employees submit time off and view payslips in Feishu or DingTalk without storing PII in a local middleware database?

Yes. A stateless pass-through web app authenticates each employee against Workday OAuth 2.0 Authorization Code Grant with PKCE, fetches live balances or pay statements into memory to render the screen, and discards the response immediately without persisting worker records to disk.

Do we need a Workday Extend license to embed custom Workday screens inside Lark or DingTalk?

No. Workday Extend renders pages inside the Workday tenant shell, whereas DingTalk, Feishu, and Lark workbench apps host external web views that call standard Workday APIs via a user-delegated API client registered with Register API Client.

How does language localization work when embedding Workday screens inside super-apps?

The embedded UI layer reads either the super-app client locale (Simplified Chinese, Traditional Chinese, Japanese, English, Bahasa, or Thai) or the worker's Workday locale preference and translates labels, date formats, and absence unit displays accordingly.

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.