Describe a workflow and let Bizomate build it

Describe it turns a sentence such as When a Razorpay payment comes in, create the invoice and email it to the customer into a workflow. Bizomate shows you a plan first — the trigger, each step, the connections they need and any questions — and builds nothing until you select Build it. What it builds is a draft: nothing runs or publishes until you do.

Who can do this

Workspace Admins and Editors, on every plan, Free included. Viewers do not see + New workflow, and an empty canvas shows them no Describe it box.

Each plan has a number of plans a day for the whole company — see Good to know.

Steps

Start from the Workflows page

1. Select Workflows in the bar at the top of the page.

2. Optional: to put the new workflow into a project, choose that project in the project filter first.

3. Select + New workflow at the top right. The New workflow window opens on its first tab, Describe it: Say what should happen, in your own words. Bizomate plans the workflow; you check it before anything is built.

4. In the box (Describe what this workflow should do…), type what should happen — what starts it, then what should be done. For example: When a new Shopify order comes in, post it in the #orders channel on Slack. Up to 2,000 characters.

   • Or select one of the examples under the box to fill it in: New Razorpay payment → Zoho Books invoice, Form entry → Sheet row + WhatsApp, Every Monday, email last week’s sales, New Shopify order → Slack #orders. Change the words as you need.

5. Check the meter under the box, for example 27 of 30 left today · Starter.

6. Select Plan it. The button reads Planning, and a line says Planning… — reading your words and your connections. It usually takes several seconds.

   When it is done, The plan replaces the box.

Start from an empty canvas

A workflow with no trigger yet shows How should this workflow start? in the designer. The first choice is Describe it — Bizomate plans it, you check it — with the same box, the meter and Plan it, without the examples. The rest works as below, except that Build it builds into the workflow you have open.

Check the plan

The plan lists the trigger and every step in order, with a summary such as 4 steps · 1 needs a connection · 1 question. Each row shows the step's name — Create the invoice — and under it the app and one line on how.

7. Look at the right of each row:
   • ✓ and a connection's name — the workspace has exactly one connection for that app, and the step will use it.
   • Connect and the app, for example Connect Slack — the workspace has no connection for that app (or more than one; see Good to know). Select it: Connections opens in a new tab with that app ready to add. See Connecting a service, and what we keep.
   • HTTP Request to fill in — Bizomate does not connect to that app yet. See An app Bizomate does not have below.
8. If you added a connection in the other tab, come back and select Connected it? Check again. The rows that now have one show ✓ and its name.
9. If the plan has One question (or 2 questions…), answer each:
   • A question with set answers — Which Slack channel? — is a list: pick one from Choose….
   • Otherwise, type the answer. Where the answer is something you pick from the app, the box says Or choose it on the step after Build it.
   • You can leave a question unanswered. That field is then marked Check this on the step. See Check a drafted workflow.
10. Under Ready when you are — Building makes a draft on the canvas. Nothing runs or publishes until you do. — choose:
    • Change the plan — back to the box, with your words still in it. Change them and select Plan it again. This counts as another plan.
    • Build it — the button reads Building.

What Build it does

• From New workflow: a new workflow is made, named by the plan (New Shopify order to Slack, for example), in the project you were looking at. The designer opens on it.
• From an empty canvas: the steps are placed in the workflow you have open. If it was still called Untitled workflow, it takes the plan's name.

A toast says Drafted “New Shopify order to Slack” — Every step it made says Drafted — check it until you open it. Check each one, then test and publish.

An app Bizomate does not have

If your words name an app Bizomate does not connect to, the plan still includes that step, as an HTTP Request for you to fill in, and a banner says: One app isn’t here yet. Bizomate doesn’t connect to Busy Accounting yet. That step is an HTTP Request for you to fill in — or ask for the app. Select Ask for Busy Accounting to tell us you want it — see Ask for an app Bizomate does not have. After Build it, set up the HTTP Request with the app's own web address — see Call a web address with HTTP Request.

What happens next

• The workflow is a draft. It saves as you go, shows as NEVER PUBLISHED on the Workflows list, and nothing runs until you publish it and switch it on.
• Every step it made carries Drafted — check it, and every setting Bizomate guessed is marked Check this. Publishing reminds you of any left, but does not stop you. See Check a drafted workflow.
• Settings are filled in where your words said them, often with values from earlier steps, such as the customer's email from the trigger.
• Connections: a step uses the workspace's connection for its app when there is exactly one. Otherwise you choose one on the step.
• To change it in words later, use Ask for a change in the designer's ⋯ menu. See Change a draft by asking.

What the AI sees

Under the box: Sent to the AI: your words, your connections’ names and the apps’ fields. Never run data or keys.

• Sent: your description; the name and app of each working connection in this workspace (Consulace Slack · slack); and the list of steps Bizomate has, with their settings' names.
• Never sent: anything a run has handled, pinned output, keys, passwords, tokens, or the contents of your lists.
• Planning uses Claude, an AI model from Anthropic, through Bizomate's own account — not through any connection of yours.
• Bizomate checks every answer against the steps it really has before you see it. A step type that does not exist becomes an HTTP Request, a setting the step does not have is dropped, and a workflow has exactly one trigger.

Good to know

• Plans a day, shared by everyone in the company across all its workspaces:

  Plan	Plans a day	The meter reads
  Free	5	5 of 5 left today · Free
  Starter	30	30 of 30 left today · Starter
  Pro	100	100 of 100 left today · Pro
  Enterprise	Fair use	Fair use · Enterprise

  The day starts again at midnight in the time zone on your profile — see Edit your profile: name, photo and time zone.

• What counts: every Plan it that gets an answer — a plan, Too much at once or Not a workflow yet — and every Change the draft in Ask for a change. Planning isn’t available just now does not count. Build it does not count.

• One workflow at a time. Describe one trigger and what follows it. Two separate jobs need two workflows.

• Straight through. A described workflow runs one step after another. For paths (IF, Switch), loops or merges, add them on the canvas afterwards.

• Steps per workflow. The plan never has more steps than your plan allows in one workflow (20 on Free, 250 on Starter); any beyond that are left off.

• More than one connection for the same app. The plan shows Connect for that app even though you have connections. Build it anyway, then choose the connection on the step.

• The description is not kept with the workflow. Bizomate keeps a count of plans for the allowance, not your words.

If something goes wrong

Related

• Check a drafted workflow
• Change a draft by asking
• Ask for an app Bizomate does not have
• Create a workflow
• Publish a workflow