> For the complete documentation index, see [llms.txt](https://docs.novacura.com/extensibility-and-integration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/extensibility-and-integration/products/studio/applications/workflow/how-to-guides/publishing-workflows.md). # Publishing Workflows If you have imported several workflows from a wap file you can publish all of them in one step. Within the Server Contents Window right click on the folder and select “Publish”. This process can take a few minutes but once complete, a Publish Successful message will be displayed. ![](/files/-MlJTmSsUD0xmnynKyDc) If you receive any errors during the publication of the workflow. Please review the error detail and consult your support contact with the relevant information. The workflows will now be available to execute on your chosen Flow client. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.novacura.com/extensibility-and-integration/products/studio/applications/workflow/how-to-guides/publishing-workflows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.