> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/library/action-nodes/open-url.md). # Open URL The Open URL Action Node can be used to * Opening external URLs / links * Opening another App / internal URL * Downloading files ### Open external URLs / links Apply the URL in setting **URL**. Optionally, you may add parameters to the URL using the **Query Parameters**. Normally, you would also tick the option **Open in new window** when opening external URLs. ### Open another App In this case, you may refer to the App URL without a full hostname in the URL. For example, when opening another app with a readable ID `company-administration`, you may simply set the **URL** setting to `/company-administration`. The normal case for such navigation is to open in the same window, in other words, do **not** tick the **Open in new window**. ### Download files In this case, you have a Data Source containing a file (document or image) you want to download. All File Object Classes in Appfarm have a built-in property **File Content**. As you may have noticed, the **Data Type** of this property is an **Internet URL**. In the Open URL action node, you may simply data-bind to **File Content** property of your Data Source to the **URL** setting. You would typically tick the **Open in new window**, but in most browsers, it will just download the file regardless of this setting. ### Login with custom authentication Open URL may also be used when you want to log in with an external identify provider. Having a [Custom Auth Provider](/reference/configuration/login/custom-auth-providers.md) added in Appfarm Create, and you may use the URL found in the blue dot of the Hide Login Button setting. This is explained [here](/reference/configuration/login.md#custom-auth). --- # 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.appfarm.io/library/action-nodes/open-url.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.