Help Centre › Building Processes
This article describes the RPA Browser functionality to wait for a network request matching a URL pattern.
For a full list of available functions, please read BROWSER functions.
Description
The BROWSER Wait for network request function pauses execution until a network request matching the specified regex URL pattern completes, or the timeout is reached. This is useful for waiting on API calls or resource loads before proceeding with the next step.
Setting it up
To use the BROWSER Wait for network request function, follow these instructions:
{{popups:rpas/add:action=browser-wait-for-request}}
Once on a process map:
- Navigate to the process where you would like to add the BROWSER Wait for network request function
- Click on the green button's drop-down (right side of the green button labelled "Process")
- On the menu that appears, click on the "+ Activity" item
- From here you can select the BROWSER Wait for network request option
- Click "Add" once you are done
Input parameters
| Parameter | Required | Type | Default | Description |
|---|---|---|---|---|
| URL pattern | Yes | Text | – | Regex pattern to match against request URLs. |
| Variable | No | Text | matched_request | Variable name to store the matched request. |
Output variables
| Variable | Type | Description |
|---|---|---|
| {matched_request} | Object | Object with url, method, status, and timestamp of the matched request (null if timed out). |
Errors
| Error | Description |
|---|---|
| Browser not open | No browser session is active. |
| Timeout | No matching request was detected within the timeout period. |
Tips
- Use this instead of fixed waits to make your automation more reliable and faster.
- Place this action before the step that triggers the request, or use it alongside Capture network requests.
- Check if the variable is null to handle timeout cases gracefully.