Import workflows from a file

Importing brings workflows in from a file exported from Bizomate — from another workspace, another company, or a backup. They always arrive as drafts, so nothing runs until someone publishes them. Along the way you match the connections, lists and variables they use to this workspace's own.

Who can do this

Workspace Admins and Editors, on Pro and Enterprise. On other plans the Import dialog says Importing workflows comes with Pro. Exporting works on every plan, so nothing you make here is ever locked in.

Creating a list or a global variable as part of an import needs a workspace Admin. An Editor can still import; those steps arrive needing setup.

Before you start

• Have the .json file exported from Bizomate, up to 1 MB and up to 50 workflows.
• Add the connections the workflows need in Connections first, if you can — then you can choose them during the import.

Steps

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

2. Select Import at the top right. (On an empty workspace: Import from a file.)

   Import workflows opens: From a file exported from Bizomate. They come in as drafts; nothing runs until someone publishes it.

3. Select Choose a workflow file and pick the file. It reads Reading the file for a moment.

   You see 3 workflows in consulace.bizomate.json, each with its steps, its trigger and the project it was in — 4 steps · On a schedule · was in Finance.

4. Under Connections, for each service the file uses — Microsoft 365 · “Rohan's Outlook” · 3 steps — choose one of this workspace's connections, or Choose later, in the designer. Where there is a likely match it is chosen for you.

5. Read Left out of the file, if shown: values that looked like passwords or keys, and steps that could never run. You put those back in the designer.

6. If the workspace has projects, choose one in Into project, or Ungrouped.

7. Select Import workflow (or Import 3 workflows). If the file uses lists or variables, the button is Next: lists or Next: variables instead, and the top says Step 1 of 3.

Lists

Lists in this import — Their names and columns came with the file. Their rows did not. For each list:

• Already here — choose Use this workspace's list of that name (its rows stay exactly as they are) or Create an empty one beside it.
• Does not fit — a column holds a different kind of value here, or the unique column differs. Use is off; create an empty one beside it.
• Not in this workspace — choose Create empty list ‘…’ (3 columns, no rows. Ready for the first run.) or Point the steps at another list, then pick it under List. Only lists whose columns fit are offered.

A note under the lists says how creating them counts against your plan — Creating a list counts against your plan — this import takes you to 4 of 10.

Select Next: variables, or Import.

Variables

Variables in this import — Text variables travel with their values. A Connection variable travels as its provider and name — the connection itself stays here.

Under Needs setting up, for each variable this workspace does not have:

• A Text variable: select Create … to create it with the values the file carries. Undo takes that back.
• A Connection variable: select Choose connections, then pick one for Production and one for Development (or Same as Production). Don't set now leaves it.

Missing variables do not stop an import. The workflows arrive as drafts with Needs setup on every step that reads one, which is the same state as a missing connection.

Select Import workflow. Back returns to the step before; All of them, or none. — either every workflow comes in, or none does.

What happens next

• One workflow opens in the designer. The toast says Imported “…” — It is a draft. Publish when you are ready., or 2 steps need setting up before publishing — the designer marks them.
• Several are added to the Workflows list: Imported 3 workflows — They are drafts. …
• Lists and variables you chose to create are made, and the toast says so — 1 empty list was created.
• Steps whose connection you left for later, and anything left out of the file, show Needs setup. See Fix steps marked Needs setup.
• Steps of a kind this Bizomate does not have arrive as they are, to replace. See Replace a step that no longer exists.

Good to know

• Imported workflows do not count towards the plan's limit of workflows switched on — they are drafts.
• The plan's step limit does apply. A workflow with more steps than the plan allows stops the import.
• A global variable already here is used as it is: Global · already in this workspace — its values are used, not the file's.
• Nothing is overwritten. Importing never changes a workflow, list or variable already in the workspace, except adding missing columns to a list you chose to use — and only an Admin can do that.

If something goes wrong

Related

• Export workflows to a file
• Fix steps marked Needs setup
• Manage a workflow's own variables
• What a list is not for