> 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/navigate.md).

# Navigate

Use the **Navigate** action node to display different views in your app. Navigate will change the URL path based on the view selected. Navigate can also be used to update URL parameters, and to open another app in the solution.

**Tip:** Create an action with Navigate and an action param of data type View. Then, set the View property of Navigate to the value of the action param. This way, you can specify a View within the event handlers in your UI or from other actions, creating a dynamic action that can be used for navigation across your app.

{% hint style="info" %}
Showroom: [Navigate example](https://showroom.appfarm.app/action-nodes/navigate), with its setup in Appfarm Create ([register](https://showroom.appfarm.app/sign-up) for access).
{% endhint %}

## Properties

### Navigate back

Enable browser history navigation.

If Navigate back is enabled and the View property is set, the app will navigate to that view's path but instead of pushing a new path to the browser history, the given path will replace the current path.

If the View property is not set, the browser will navigate to the previous page in the browser history. Note that the previous page could be an external website outside of the app.

### App

Select another app in the solution to go to. Leave empty to stay in the current app.

Users who cannot open the selected app get an error, so check access before navigating.

You can bind **App** to a property of the built-in **App** enum, for example **App** in the built-in [Apps](https://docs.appfarm.io/reference/apps/data.md#apps) data source.

When an app is selected:

* **View** lists the views of that app. Leave **View** empty to open the app's default view.
* **Subview** is shown once a **View** is selected.
* **Navigate back**, **Navigate to root**, and **Transition** are hidden.

**App** is hidden when **Navigate back** or **Navigate to root** is selected.

### View

Select a view to navigate to.

### Sub view

Select a Sub View to display within a [view container](https://docs.appfarm.io/library/ui-components/view-container.md).

### Navigate to root

Navigate to the root URL of the app.

### Transition

Apply a visual transition when switching views. The options are:

* None (default)
* Fade
* Slide

### Keep URL params

If enabled, existing URL parameters will be preserved when navigating. Any new parameters specified will override the existing ones. Disable to clear all existing URL parameters.

### URL parameters

Set the value of any URL parameter you have added to your app. Learn more about URL Parameters [here](https://docs.appfarm.io/appcademy/appfarm-fundamentals/app-data-fundamentals/url-parameters.md).


---

# 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/navigate.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.
