> For the complete documentation index, see [llms.txt](https://docs.gpmautomate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gpmautomate.com/automate-en/action-guide/navigation/get-url.md).

# Get URL

Get URL is an action used to extract the entire address (URL) of the currently opened webpage in the browser and save it into a variable.

🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM).

#### Configuration parameters:

* Output variable: The name of the variable you assign to store the webpage address string after successful extraction.

#### Practical example: Check the redirect status after successful login

When you create an automated login script to a platform (for example, Pinterest or Facebook). After filling in the information and clicking the login button, you want to check whether the account has successfully reached the homepage or has been redirected to an error page/identity verification page (Checkpoint):

* Configuration method:
  * Wait a few seconds after clicking the login button, then call the Get URL action.
  * Output variable: Name the variable `currentLink`.
  * Combine with an If conditional block afterwards to check the data of the variable `$currentLink`:
    * *Case 1*: If the variable `$currentLink` contains the phrase `checkpoint` or `login_error` ➔ The script identifies an account error and processes to stop the flow.
    * *Case 2*: If the variable `$currentLink` contains the phrase `home` or the data switches to the personal page ➔ The script identifies a successful login and continues to run the account nurturing tasks.


---

# 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.gpmautomate.com/automate-en/action-guide/navigation/get-url.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.