# Generate link

Generate Link helps the user to construct a link which can be used to execute a workflow. This is supported for both User Workflows and Machine Workflows. Generate Link is located in the context menu in the server content panel.

### User Workflows

User workflow links point to the web client and provide a direct link to a workflow execution. 

<div align="left"><figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FlSjvBoa6dZydd1AWGUYp%2FGenerate%20web%20link.png?alt=media&#x26;token=2f5d7922-4fd8-4ffe-9cac-46aba19dd5a2" alt=""><figcaption></figcaption></figure></div>

* **Web Client Url** this field should contain the url to the web client.&#x20;
  * If the link is for the new web client, the URL will always be the same
  * If the link is for the legacy web client, the URL will differ per server
* **Server Url**
  * If the link is for the legacy web client, leave this field empty
  * If the link is for the new web client, add the URL to the server
* **Execute Only** locks the user to the execution view and prohibits the user from quitting 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.

Click **Copy** to copy the link for the legacy web client.&#x20;

Click **Copy (NG)** to copy the link for the new web client.

### **Mobile Link**

<div align="left"><img src="https://529897662-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&#x26;token=5cf9b757-92ac-421e-bae7-2f7818423909" alt="Configuration example"></div>

User workflow links point 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 requests are made directly to the flow server. The workflow is executed by a machine user and authentication is made by basic authentication.&#x20;

<div align="left"><img src="https://529897662-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&#x26;token=2d74fa91-98a6-488a-beb0-e051e2578ed5" alt=""></div>

* **Method** supported methods are POST and GET, POST supports complex structures as input and GET only supports simple variables fetched 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 provide 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.

{% hint style="info" %}
The default execution timeout is **10 minutes** for calls to the rpc/json2 endpoint. \
To increase this timeout, add the *workflowTimeout* query parameter with the timeout value in *milliseconds*, like:\
<http://x.com/Novacura.Server/rpc/json2/pEjzkmFwq0O&#x67;**?workflowTimeout=3600000**\\>
\
For long-running workflows, the above needs to be taken into consideration in addition to the executionTimeout in the server web.config file as well as timeout settings for any proxies in between the client and the Flow Server.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://help.novacuraflow.com/development/flow-studio/applications/server-content/generate-link.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.