Download

The whole Extend job. You approve.

Describe the app. kiweely designs it, builds it, has Workday check it, deploys it, tests it as each person and promotes it. Every step that touches Workday waits for you.

Start for free Download

Your own developer tenant, with kiweely in it.

Workday’s Open Developer Program gives one developer one Workday account and a Development tenant, with no company subscription. kiweely works in it the way it works in a company’s tenants. Workday’s announcement · Getting started with a personal developer account

  • Connect it the way Workday asks

    Choose your Workday Digital ID on Workday’s own sign-in page, the same sign-in you use for Workday Community. There is nothing to set up first.

  • The whole loop in your tenant

    It designs the app, has Workday check every version, deploys it once you approve and tests it as each person who will use it.

  • Development is where it lives

    A developer account has one Development tenant, so the app is built, deployed and tested there. Implementation, Sandbox and Production belong to a company’s Workday.

Build an agent. Workday runs it.

Describe what the agent should do and who may use it. On Mac, kiweely writes the agent and its skills, has Workday check them, deploys it once you approve, makes it available to the people you named and tries it in Workday’s own chat.

  • A project, like any app

    Start a new agent, or open one already in Workday. It keeps its files, Testing, Monitor and earlier versions.

  • Active and tested, never assumed

    It reports what Workday says: deployed, active, who can use it, and what each test in Workday’s chat really did.

  • Built in Development

    Agents are built and deployed in a Development tenant, your own Open Developer tenant included. Running one uses your Workday AI allowance.

New project for Meridian Health: Workday custom agent chosen as the kind of work, starting from a new agent, named Team helper.
kiweely's answer: Team helper is deployed to Development Tenant, active for the Manager security group, and answered two test questions in Workday's chat as Marcus.

The work that eats an Extend developer’s week.

Each story replays a real request on the real screens: what you asked, what kiweely did, and the answer.

The request: test the disclosure flow as three people and fix anything that breaks.

Scroll sideways to see the whole screen.

It deploys the fix and tests all three people again, in a browser you can watch.

How far it takes your app.

  1. Development

    It deploys each version once you approve it.

    Deployed

  2. Implementation

    It promotes the version, naming every model change first.

    Promoted

  3. Sandbox

    It promotes it again, and can test it there as the people who will use it.

    Promoted

  4. Production

    For safety, kiweely never promotes an app to Production.

    You move it there yourself, in Workday’s Developer Site.

Doing a step yourself? The guides cover each check:Build your first Workday custom agentExtend validation errorsAn app that validates but won’t deployTesting an Extend app before promotion

Orchestrations get the same loop.

In Orchestration for Integration, when a run fails, it reads Workday’s own run history and logs, fixes the cause and runs it again. What Orchestrate’s errors mean

Is yours built in Workday Studio?

Studio integrations, new and inherited, get a loop of their own: built and tested in the Workday Studio on your computer, with no Workday Extend needed.

The Studio page

Apps kiweely built, start to finish.

Each was asked for in plain words, checked by Workday and tested in a Workday tenant, on camera. Watch the build, then start your own project from it.

Newest first · 3 apps

You keep the decisions. kiweely does the hands‑on work.

The brief, the approvals and Production stay with you. The building, checking, deploying, testing, fixing and promoting go to kiweely.

Start for free See pricing