> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/product/accounts/edit-an-existing-workflow.md).

# Edit an existing workflow

## Create a new draft

Workflows are versioned. To edit an existing workflow, click **Make new version** at the top of the workflow page. A draft workflow will load. You can edit this workflow and when you are ready to save it or promote it to live, click **Lock this version and make active**.

## Previous versions

You can access previous versions of workflows by selecting **View another version...** at the top of the page and selecting a previous version. Versions that are locked can be edited by clicking **Make new version**.

<figure><img src="https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2FmRcdCB8iUFbUPbk8KPkj%2FScreenshot%202024-11-11%20at%204.51.13%E2%80%AFPM.png?alt=media&amp;token=49216409-8fa5-403d-b7fe-19f6f47c888c" alt=""><figcaption><p>Previous versions of workflows can be accessed via the "View another version..." dropdown</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/product/accounts/edit-an-existing-workflow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.