All agents
    Every appAvailable now

    Workflow builder

    Describe a process in plain words and get a company workflow built only from what the workflow engine can do, checked and saved switched off.

    How it works

    For admins who manage AI agents. Describe a process, for example “when an offer is accepted, start onboarding, ask IT for a laptop and tell the manager”. The agent maps it onto the workflow engine's own steps (leave, calendar, expense claims, insurance cover, family details, helpdesk tickets, onboarding), shows it as numbered steps with who does each and what they wait for, and lists plainly what the engine can't do yet or what is set in a module instead (such as expense approval chains). It checks the draft in code: how it starts, every step reachable, no loops, approvers the module can resolve and no permission you don't have. On your confirm it saves the workflow as a draft, switched off; switching it on is yours to do. It also explains existing workflows in plain words, such as “what happens when someone resigns?” from your People offboarding template.

    About 1 credit per drafted workflow; checking and explaining are free

    What it reads

    • The workflow engine's steps and your company's saved workflows
    • People onboarding and offboarding templates (if your role may view them)
    • Your own permissions and which agents your company hired

    When it starts

    • When an admin describes a process or asks how one works

    What it can do

    • Save a workflow as a switched-off draft (after you confirm)

    What it never does

    • Switch a workflow on, or run it

    Safe by design

    • One assistant, many agents. Ask the Employee assistant in the app or on WhatsApp; it calls the agents your company has hired that you may use.
    • Hired, not switched on. Your admin hires each agent from the catalogue and chooses who can use it.
    • Agents propose, people confirm. Anything that changes data, like a leave request, waits for a person to confirm it.
    • Same access as the user. An agent sees only what the person asking is allowed to see.
    • AI processing in India. Agents run on models hosted in India (AWS Mumbai).
    • Budgets and a hard stop. Set a monthly credit limit per agent; agents stop when credits run out.
    • Every run recorded. Admins see each run, the credits it used and what it did.

    Frequently asked questions

    What does the Workflow builder do?

    For admins who manage AI agents. Describe a process, for example “when an offer is accepted, start onboarding, ask IT for a laptop and tell the manager”. The agent maps it onto the workflow engine's own steps (leave, calendar, expense claims, insurance cover, family details, helpdesk tickets, onboarding), shows it as numbered steps with who does each and what they wait for, and lists plainly what the engine can't do yet or what is set in a module instead (such as expense approval chains). It checks the draft in code: how it starts, every step reachable, no loops, approvers the module can resolve and no permission you don't have. On your confirm it saves the workflow as a draft, switched off; switching it on is yours to do. It also explains existing workflows in plain words, such as “what happens when someone resigns?” from your People offboarding template.

    Can the Workflow builder change data on its own?

    No. It asks a person to confirm before it will: save a workflow as a switched-off draft. It never does the following: switch a workflow on, or run it.

    How much does the Workflow builder cost?

    About 1 credit per drafted workflow; checking and explaining are free. Credits are a paid add-on to any flowwork.ai plan at ₹100 (US$ 1.19) per 1,000 credits, and new companies get 500 free trial credits for 30 days.

    Where is the data processed?

    Agents run on AI models hosted in India and see only what the person using them is allowed to see. Admins see every run and the credits it used.

    Other agents