> This page is for Glide Classic.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://www.glideapps.com/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://www.glideapps.com/docs/_mcp/server.

# Go to Tab

> Navigate the user to any tab in your app.

The **Go to Tab** action allows you to move the user to a specific tab in your app.

This is different from the [Show New Screen](/docs/automation/actions/show-new-screen) action which allows you to link to a sheet and customize that screen however you like. With **Go to Tab**, you have to already have created a Tab so the action can move the user there.

The **Go to Tab** action can be used as an action in the components of your app (like [Buttons](/docs/essentials/components/button), [Collections](/docs/essentials/components/collections), and much more), or it can be triggered along with other actions as part of a [Workflow](/docs/getting-started/introduction-to-workflows).

## **Setting up the Go to Tab Action**

#### Layout Editor

#### Go to Tab Action layout Arcade

Click on the plus (+) sign in the **Components** panel and select the **Component** you want to trigger the action.

In the **General** tab on the right side of the Layout Editor, navigate to the **Actions** section and select **Go to Tab**.

Select the icon and descriptive text to use in your app, and then choose the Tab you the user to go to.

You can optionally add **Conditions** for certain criteria to be met before a user can trigger this action.

#### Workflow Editor

#### Go to Tab Action editor arcade

Select the **+ New Workflow** button.

Select the **data source** for your action.

Configure your first action by clicking the first step in the workflow. You can also add conditions to your actions, if needed.

To add new actions to the flow, hover just underneath a step and click the plus button. In this way you can add the Go to Tab action as just one step in a larger workflow.

Check the [Introduction to Actions](/docs/automation/actions) page for a full list of components that can be used to trigger actions.