Open a website on a new browser session. This Wrk Action will create a unique browser session that must be used in subsequent Web Process Automation Wrk Actions.
A browser session will be active for 15 minutes or until closed. If your Web Process Automation Wrkflow is taking longer than 15 minutes please try breaking it into smaller browser sessions. If unable to break it up further please contact support.
Always use the “Close browser session” Wrk Action when you are done with your website automation. It will significantly improve performance of your Wrkflow
Application
Web Process Automation
Inputs (what you have)
Name | Description | Data Type | Required? | Example |
Website link | Link to the website you want to open | URL | Yes | |
Browser cookies | Cookies to provide to the browser when opening the website. Refer to the documenation for more information | Text (Long) | No | See below for examples |
Proxy | The country the request should originate from. | Pre-defined choice list | No | See below for examples |
Block ads? | Use this mode to prevent ads from loading during your web automation session | True or False | No |
|
User agent | User agent to use on this page | Text (Long) | No | See below for examples |
Note: the value of inputs can either be a set value in the configuration of the Wrk Action within the Wrkflow, or a variable from the Data library section. These variables in the Data library section are the outputs of previous Wrk Actions in the Wrkflow.
Outputs (what you get)
Name | Description | Data Type | Required? | Example |
Browser session ID | If successful, the unique identifier of the browser session that was created and can be automated | Text(Short) | Yes | fb9bc380-146c-420e-9130-50ce93614e05 |
Outcomes
Name | Description |
Success | This status is selected in the event that the website was opened successfully |
Unsuccessful | This status is selected in the event of the following scenario:
|
Impossible to complete | This status is selected in the event of the following scenario:
|
Configuration Instructions
Browser Cookies:
By entering Browser cookies when opening a browser session you can start the session logged in to the application and not need to automate the log in page. This will save a lot of time and complexity when building your Wrkflow.
You can enter a list of browser cookies into this Wrk Action in the format
[
{
"domain": "domain1",
"name": "cookie1",
"value": "value1"
},
...
]
You can get your existing Browser Cookies in many ways. Two options are below:
Method 1
Navigate to the website you wish to find the cookies for in Chrome
Go to Chrome Dev Tools (F12, or right click the website and click "Inspect")
Go to "Application" in the Horizontal top menu
Go to Storage - > Cookies -> Click the website you are interested in
You will now have a list of cookies that are used for that website and can be added to your Wrk Action
Method 2
Download the Chrome Extension "Cookie-Editor" from this website: https://chromewebstore.google.com/detail/cookie-editor/hlkenndednhfkekhgcdicdfddnkalmdm
Navigate to the website you wish to find the cookies for in Chrome
Click the Cookie-Editor Chrome Extension
Allow the Extension for that site or for all sites.
You will now have a list of cookies that are used for that website and can be added to your Wrk Action
Proxy
We allow the use of residential proxies that allow our Wrk Actions to surf the web as a real user in that country. Select from either Canada or the United States to use our residential proxies while browsing.
User Agent
The User Agent is a string that provides information about the web browser, the software version, and the device operating system to the website you are visiting.
The reason for presenting the user agent string is so that the site knows how to display the information.
Our User Agent will default to:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/117.0.0.0 Safari/537.36
If you would like to change it then you can enter a new user agent in the optional input.