Skip to main content
To get a workflow ready for production, do the following:

​
Run the draft from the builder

1

Click Run

The execution configuration modal opens.
2

Pick the version

The version selector sits in the top right of the modal. Choose the draft. This is how you test a change before anyone else sees it.
3

Choose a profile

Select an agent profile, or create one. The profile carries the credentials, the proxy, and the browser settings the execution needs.
4

Fill in the inputs

Give a value for every {{.variable}} your instructions reference. Attach any files the workflow must read.
5

Start the execution

The execution page opens and shows the workflow working.

​
Read what happened

Watch the execution and see if it worked.
  • The timeline shows every action in order.
  • The browser view shows the page the workflow saw at each step.
  • The reasoning shows why the workflow chose each action and each transition.
Debug your workflows covers how to work back from a bad outcome.

​
Make an update

See Improve your workflow to learn how to make your workflow better. See Write good instructions to learn how to write clearer instructions.

​
Run it against real cases

To start with, get the happy path working. Then, run the workflow against a variety of inputs that might occur in production.
  • Run it with different input values.
  • Run the edge cases: the missing record, the long name, the second page of results.
  • Run it more than once on the same input to ensure it works consistently.
  • Check the result matches the format you expect. See Inputs and outputs.

​
Publish

Publishing makes a version the one new executions use.
  • In the builder, click Publish.
  • From code, call agentWorkflowsPublish, or POST /agents/{agentId}/workflows/{workflowId}/publish.
  • From your coding agent over MCP, call workflowPublish.
An execution started from the API runs the published version. Editing the draft changes nothing for your callers. If your API runs ignore a change you made, check that you published it.

​
Versioning

To understand how Asteroid workflow versions work, please read our Versioning documentation.