> 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/wait-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 if the specified timeout period is reached. 🎥 Watch the tutorial video: [Here](https://youtu.be/a9qNt96X1SM). #### Configuration parameters: * Timeout (s): The maximum timeout period (in seconds) for the system to wait for the URL to change. If the URL remains the same after this period, the script will automatically proceed to the next action. #### Practical 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 using 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 monitor 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 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 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/wait-url-changed.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.