> 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-guides/navigation/url-changed.md).

# Wait URL Changed

Wait URL Changed is an action that instructs the script to pause and continuously monitor the browser's address bar until the current URL changes to a new address, or the system will automatically skip when the specified timeout expires.

#### Configuration Parameters:

* Timeout (s): The maximum waiting time (in seconds) for the system to wait for the URL to change. If the URL remains unchanged after this time, the script will automatically proceed to the next action.

#### Real-world Example: Waiting for Payment Gateway Processing or Successful Redirect Authentication

This action is extremely useful when you set up third-party login flows (like clicking *Continue with Google* on Pinterest), or when you press the "Pay/Buy Now" button on e-commerce sites:

* How to configure: Immediately after the action of clicking the redirect activation button, you insert the Wait URL Changed action with a Timeout of `30` (30 seconds).
* Operational logic: Instead of having to use a fixed command like Delay 5-10 seconds arbitrarily (which wastes time if the network is strong, or causes missed clicks if the network is weak), the system will actively observe the address bar. As soon as Pinterest successfully redirects from the login page to the homepage (`pinterest.com/home`), the script will immediately continue executing the subsequent interaction steps without waiting for the full 30 seconds.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gpmautomate.com/automate-en/action-guides/navigation/url-changed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.