> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/applications/server-content/generate-link.md). # Generate link Generate link helps the user to construct a link to execute a workflow. This is supported for both User Workflows and Machine Workflows. Generate Link is located in the context menu in server content panel. ### User Workflows User workflow links points to the web client and provides a direct link to a workflow execution. ![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-otx17HfcJTiIC_n0U%2F-M-ovUibsB_wuDiLyBdS%2Fhelp_root_applications_server_content_generate_link_user.png?alt=media\&token=9a263167-5b3f-4636-85e7-93245def6b0d) * **Web Client Url** this field should contain the url to the web client. * **Execute Only** locks the user to the execution view and prehibit the user from quiting the workflow or returning to a menu after execution. * **Public User** this option configures a public user to run the execution, when a public user is selected no credential prompt will be displayed. * **Parameters** this sections show the input variables that are configured in the start event of the workflow. Only simple variables can be used in user workflows. ### **Mobile Link** ![Configuration example](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-otx17HfcJTiIC_n0U%2F-M-ovY16hyr7ZGiAsr7X%2Fhelp_root_applications_server_content_generate_link_user_mobile.png?alt=media\&token=5cf9b757-92ac-421e-bae7-2f7818423909) User workflow links points to the mobile client and provides a direct link to a workflow execution. * **Parameters** these sections show the input variables that are configured in the start event of the workflow. Only simple variables can be used in user workflows. ### Machine Workflows Machine workflows can be executed over http request. These request are made directly to the flow server. The workflow is executed by a machine user and authentication is made by basic authentication. ![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-otx17HfcJTiIC_n0U%2F-M-ova5bKWYs8zETmP7N%2Fhelp_root_applications_server_content_generate_link_machine.png?alt=media\&token=2d74fa91-98a6-488a-beb0-e051e2578ed5) * **Method** supported methods are POST and GET, POST supports complexe structures as input and GET only supports simple variables feetched as query string values. * **Server URL** url to server, must be accessible from where the request is made. * **Input** in this section all simple variables are shown and provides a help function for constructing the input parameters. In POST requests the input should be sent as JSON in body content and GET should send input variables as part of the url. --- # 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://help.novacuraflow.com/6.12/development/flow-studio/applications/server-content/generate-link.md?ask=&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.