When you describe a workflow that needs an app Bizomate does not connect to yet, the plan says so, keeps that step as an HTTP Request for you to fill in, and offers Ask for that app. Asking tells us you want it; the step still works today if the app has a web API.
Who can do this
Workspace Admins and Editors, on every plan — anyone who can use Describe it.
Before you start
You have a plan on screen from Describe it that names an app Bizomate does not have. See Describe a workflow and let Bizomate build it.
Steps
- In The plan, find the row for the missing app. Its subtitle names the app, and on the right it says HTTP Request to fill in.
- Under the plan, read the banner: 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. There is one banner for each missing app.
- Select Ask for Busy Accounting. A toast says Asked for Busy Accounting — We count every request. The button can no longer be selected.
- Carry on with the plan: answer any questions, then select Build it.
- On the canvas, open the HTTP Request step — it has the name from the plan, such as Create the voucher — and set it up with the app's own web address, method and body. See Call a web address with HTTP Request. If the app needs a key, see Connect an API key for HTTP Request.
What happens next
- Your request is recorded with the app's name as the plan wrote it, your name and your company. It goes into the count Bizomate uses to decide which apps to add next.
- Nobody replies to the request itself, and nothing changes in your workflow. The HTTP Request step stays as you set it up.
- Asking does not count against the company's plans for the day.
Good to know
- One request per person per app. Asking again for the same app — in another plan, another day, or with different capitals — is fine, and still counts once. Someone else in your company asking for the same app counts separately.
- The HTTP Request step has no settings filled in. Bizomate does not guess another app's web address. Until you give it at least an Address, publishing stops at needs setup.
- The canvas does not name the missing app. Only the step's name tells you what it was for, so set it up before you lose track — or rename it to say, for example, Busy Accounting: create the voucher.
- An app you can already reach another way — for example through its email address or a Google Sheet it exports to — may not need an HTTP Request at all. Use Change the plan and describe it that way.
If something goes wrong
| What you see | Why | What to do |
|---|---|---|
| Not asked — Something went wrong. Try again. | The request could not be saved. | Select Ask for … again. |
| Ask for … cannot be selected | You have already asked for this app from this plan. | Nothing to do — your request is counted. |
| 1 step needs setup when you publish | The HTTP Request has no Address yet. | Select Go to step and fill it in. See Fix steps marked Needs setup. |