Managing workflows

What the Workflows page is for

The Workflows page lists every workflow in the selected store. From here you create, import, duplicate, publish, configure and delete them, and install ready-made ones from the template gallery. Open a workflow to build it in the editor.

Select a store from the header first. Without one the page asks you to choose.

Finding and opening workflows

• Search workflows… filters by name or description.
• Switch between list (a table) and grid (cards) with the toggle beside the search box.
• The list shows each workflow's name and description, its slug, how many routes it has and when it was created. Select a row to open the editor.
• In the grid, a card also shows a short workflow ID. Select it to copy the full ID.

Selecting several workflows at once, for export, delete or publishing, is only available in the list view.

Creating a workflow

Select Create workflow, name it, and the editor opens. If your plan's workflow limit is reached you are told so instead.

To start from something ready-made, use Browse templates (see Installing a template).

Duplicating a workflow

Hover a row and select the copy icon. Confirming creates a copy named "<name> (Copy)" with all its routes and their steps. The original isn't changed. The copy's slug gets a -copy suffix, or -copy-2 and so on if that is taken.

Importing workflows

Select Import and choose a source.

Source	Use it for
Exported Workflows	A file exported from this page (a JSON array of workflows)
Postman Collection	Turning a Postman collection into workflows (JSON)
OpenAPI Specification	Turning an OpenAPI 3.0 spec into workflows (JSON or YAML)

Importing exported workflows

1. Upload a .json file, or choose Or paste from clipboard and paste it into Workflow JSON (Array Format).
2. Decide how to treat clashes. Workflows are matched by slug: an existing workflow with the same slug is skipped unless you tick Overwrite existing workflows with same slug, in which case it is updated. Tick Skip workflows with missing dependencies to leave out any that rely on workflows you aren't importing.
3. Select Validate & Select Workflows.
4. Choose which workflows to import. Show Dependency Graph shows how they refer to each other (through proxy routing, the Workflow connector or workflow references), so you can bring along what a workflow needs.
5. Select Import N workflow(s).

The result lists each workflow as created, updated, skipped or errored, with any warnings and errors.

Importing from Postman or OpenAPI

1. Upload or paste the collection or spec. For OpenAPI, choose YAML or JSON.
2. Optionally set a Base URL to override the one in the file. For OpenAPI you can also tick Forward all headers, so each HTTP step passes the incoming request's headers on to the upstream API, which suits a pass-through proxy.
3. Select Validate & Preview.
4. Choose how to organise the routes: one workflow for everything, or one per tag (OpenAPI) or folder (Postman). Rename workflows if you like, and set routes to Public or Private, with per-route overrides.
5. Select Import.

Exporting workflows

Select Export. With nothing selected it exports every workflow currently shown by your search. With rows selected the button reads Export N and exports just those.

The dialog lists what will be exported and lets you change the Filename (it defaults to workflow_export_<timestamp>.json). The file is a JSON array that Import → Exported Workflows accepts, which is how you move workflows between stores or keep a backup.

Publishing a workflow

Publishing takes a snapshot of the workflow as a new version that you can then configure and launch. See Publishing for what a version contains.

1. In the editor, select Publish. It is disabled when there is nothing new since the last version, and the header shows unpublished changes when there are some. If validation finds problems, fix them first; the editor tells you what they are.
2. In the Publish Workflow dialog, leave Generate AI Release Notes ticked to have release notes written by comparing with the previous version. Untick it to get a short overview you can edit later.
3. Select Publish, or Publish & Configure to carry straight on to launching it.

Publishing and configuring several workflows

Tick the workflows in the list, then select Publish & configure N. This publishes and sets up many workflows in one environment in one go.

1. Setup. Choose whether to Publish the latest changes first (and whether to write release notes with AI), and choose the Environment to configure them in, either an existing one or + New. Each workflow shows its state: Never published, Changes since vX or Published vX. A workflow that has never been published is skipped unless you publish first.
2. Variables. Set the variables for that environment once for every workflow that uses them. A variable shared by several workflows appears once, with a note of how many use it. Connections are chosen from your existing connections of the right type. Secure strings left blank keep each workflow's current value. Values already set in that environment are filled in for you.
3. Run. Workflows are processed one after another, each showing Publishing…, Configuring… and then its result. If one fails the rest carry on, and you can fix the failed ones and run again for just them.

Configuring a workflow

Configure (or Publish & Configure) opens the launch dialog for one workflow. It has three steps:

1. Variables: pick the Environment (+ New creates one), then set each variable's value for it. Connection variables use a connection picker, with Revert to default if you want the workflow's own default back.
2. Route Authentication: how callers authenticate to each route.
3. Review: confirms whether this deploys a new live instance in that environment or reconfigures the existing one.

Select Launch (or Save Changes when reconfiguring). Go to Launchpad opens the workflow's Launchpad, where you manage its versions and instances. Deployed instances are listed under Live Workflows. See Environments and Variables.

Installing a template

Select Browse templates to open the gallery.

1. Narrow the list with Filter by tag (it has its own tag search) and Filter by type: API, Webhook, Batch Job, Scheduler or File Event.
2. Open a template to read its Overview, Features, required Configuration and the workflows it contains. A template can also bring in search indexes, data tables, MCP servers and assistants; the page lists them.
3. Select Install and confirm. Workflows are added as drafts and nothing is published.
4. If your store already has resources with the same names, a dialog lists them. Checked items are overwritten with the template's version; untick any you want to keep, and the template then uses yours.

After installing, one new workflow opens in the editor, and several take you back to the list. Set the connections and variables it needs, then publish and configure it as above. Some templates have a route that runs once as soon as you finish configuring; the template page says which.

Installation can fail if the template depends on workflows or connections your store doesn't have, or if your plan's workflow limit is reached.

Deleting workflows

One workflow: hover its row and select the trash icon. The dialog warns that the workflow and its routes are removed permanently, and if it has published versions or a live instance it adds that those are deleted too.

Several: tick them and select Delete N. Everything for each selected workflow, including routes, steps and published versions, is removed permanently. They are deleted one by one, and if any fail you are told how many couldn't be deleted. Refresh to see what is left.