Generate a workflow with AI

What this achieves

You describe the route you want in ordinary sentences and Humavera draws a draft of it. What comes back is a starting point in the designer, not a published route.

Required role: Administrator.

Steps

Go to Approvals → Workflows and select New Workflow.
Select Generate with AI.
Write the Description. Say who approves, in what order, how long each step has, and what should happen on a rejection.
Fill in Name, Trigger resource types, and Category if you already know them. All three are optional.
Select Generate and wait. Designing a route usually takes between ten and thirty seconds.
Review the result on the canvas, step by step.

You land in the designer on a generated draft version. Nothing is published, and no request can reach it.

Describe it the way you would to a colleague

The result follows the detail you give. Steps, approvers, deadlines, and conditions are what it can act on.

Example: “Promotion approval requiring the requester’s manager to sign off, then Finance, with 48 hours on each step. If the manager rejects, notify the employee. Escalate to the approver’s manager on a breach.” That produces a usable shape. “Promotion approval” produces a guess.

Say what should happen when someone does not act, not only what happens when they do. A route that only describes the happy path will come back without escalation.

What it costs

Generating a workflow uses AI credits, and the cost is shown on the screen before you generate. It is charged per generation, so a description worth writing carefully is cheaper than three vague ones.

Generated workflows are marked with an AI badge on the workflows list, so anyone reading the list later can see how the route came to exist.

Generating a new version of an existing route

The same tool is available from the Versions tab of an existing workflow, where it drafts a new version instead of a new workflow. There you describe the change rather than the whole route.

Example: “Add a compliance review step after Finance approval, with 72 hours on it.” The result is a new draft version, which you compare against the published one before publishing.

Check it before you publish

Treat the result as a first draft written by someone who has not read your policy.

Option	Description
Approvers	Confirm each step asks the person you meant. A route that names the wrong approver looks entirely plausible on a diagram.
Deadlines	Confirm each step’s time limit is one you would enforce.
Escalation	Confirm every step that matters has somewhere to go when its deadline passes.
Branches	Confirm each branch has a path, including a default for requests that match no condition.
Notifications	Confirm nobody is told something they should not see.

Then validate it and simulate it as you would any other route.

What happens next

The generated draft behaves like any other draft: edit it in the designer, validate, simulate, publish, and bind it. Nothing about having been generated shortens those steps, and the AI badge does not mark it as approved by anyone.