ZennoPoster integration with ZennoBrowser

ZennoPoster integration with ZennoBrowser

ZennoPoster7 introduces new capabilities for automating web tasks due to integration with ZennoBrowser — a special anti-detect browser for working with multiple profiles. This integration allows ZennoPoster7 users to take advantage of all ZennoBrowser benefits including fingerprint customization, proxy management, and the ability to create isolated browser environment. This guide describes the main features of this integration, such as loading and managing profiles, running browser instances, creating and deleting profiles, as well as other special aspects of work with the new browser type in ZennoPoster7 space. The integration provides seamless interaction between two products, preserving the familiar ZennoPoster7 interface and connecting powerful ZennoBrowser features for professional automation of web processes.

1. Loading profiles from ZennoBrowser 

The action “Get ZennoBrowser profiles” is intended to extract information about existing browser profiles from the ZennoBrowser system.

How it works

This action makes a request to ZennoBrowser and returns full information about all available profiles as structured data.

Result output

The result of execution is a JSON array with objects, where each object contains detailed information about a separate profile:

 

  • Profile ID

  • Profile name

  • Browser settings

  • Profile status

  • Proxy data

  • Other metadata

Result processing

To work correctly with received data, it is recommended to use the “Parsing JSON” action, which will allow to: 

  • Extract specific profile parameters

  • Filter profiles by specified criteria

  • Convert data into a convenient format for work

 

Errors processing

In case of problems when connecting to ZennoBrowser (service unavailability, incorrect connection settings), the action will return an error which should be processed in a project logic.

Saving result

The resulting JSON response can be saved to a variable selected in the “Put in variable” field for further use in a project.

2. Running ZennoBrowser instance

The action “Start ZennoBrowser instance”. 

This action is intended to run the ZennoBrowser instance with the certain profile selected by ID.

How it works

The action takes ID of ZennoBrowser profile and starts browser instance with connected profile settings including the following parameters:

 

  • Browser fingerprint

  • Proxy settings

  • User data

  • Extensions and configuration


Configuring profile

Manual ID input:

 

  • Set profile ID into related field

 

Select from list: 

  1. Select the folder with profiles from the dropdown list.

  2. Select the certain profile from this folder.

Updating profile list

Use the “Refresh” button in action properties to get the actual list of available profiles from ZennoBrowser.

 

3. Creating ZennoBrowser profiles

The action “Create ZennoBrowser profiles” allows to create new browser profiles in two ways:

  • Create profile by default

When selecting “Default” mode, profiles are created with optimized settings.
The following parameters should be specified:

 

  • Profiles count — required number of profiles to create

  • Proxy settings — proxy server parameters for profiles

  • Create profile basing on sample profile

When selecting “Use profile data” mode, all profiles are created with the settings from the sample profile.

  • specify ID of a sample profile or select the profile from list

  • copy fingerprint settings, extension and other configuration parameters

 

NOTE: This option copies only fingerprint settings, not full fingerprints. New profiles will be created with unique fingerprints based on sample settings. 

 


Proxy settings

Integration allows to easily handle proxy servers to work with profiles:
 

  • Select proxy list — select proxy list from ProxyManager in ZennoBrowser

 

  • Set Maximum number of profiles per one proxy — limit profiles for proxy to avoid overload

  • Exclude repeats — each proxy is used only once when creating profiles

Saving results

The Data from created profiles can be saved for further usage:

 

  • To list — when working with multiple profiles

  • To variable — to store information from single profile

 

4. Deleting profiles

The action Delete profile is intended to permanently delete profiles from ZennoBrowser application.

 

Manual ID input:

 

  • Set profile ID into related field

 

Select from list: 

  1. Select the folder with profiles from the dropdown list.

  2. Select the certain profile from this folder.

Updating profile list

Use the “Refresh” button in action properties to get the actual list of available profiles from ZennoBrowser.

5. ZennoBrowser Integration specifics

Work with browser

  1. ZennoPoster7 operates with the integrated browser in the same way as with other browsers. 

  2. If ZennoBrowser is not installed, the action to start browser instance will offer to apply for the new product test, so that it could be installed.

Connecting and running

  1. It is not necessary to run ZennoBrowser application as the browser can be started directly from ZennoPoster7 software. However, if ZennoBrowser is active, operations with profiles will be performed faster. 

  2. When starting the browser in ZennoPoster7, profile status with the Stop button is displayed in the ZennoBrowser application. The browser can be stopped anytime, and the related profile will be released. But, this can cause an error in project execution in ZennoPoster7.

  3. In case ZennoPoster7 fails to connect to ZennoBrowser, actions with the browser will return an error. Also, ZennoPoster7 may cancel starting the browser for some reasons, for example, if the profile is already taken. This will also lead to an error. 

Differences in ProjectMaker and ZennoPoster

  1. When working the new browser in ProjectMaker, it is natively integrated into the UI and all available tools can be used for it. At the same time, GPU is disabled as well as for the Chromium browser. When running the browser in ZennoPoster, GPU is used for the new browser in the alternative rendering mode.

Working with profiles

The integrated browser ignores profile settings and emulations from ZennoPoster7 and loads the settings and emulations from ZennoBrowser. Related actions are executed without errors, but not making any changes. All operations which can affect the browser profile are also ignored.

Handling browser window

ZennoPoster7 displays the real browser in Show instance preview. It is not recommended to use minimize/close operations as in a standard browser window since it may cause unexpected behavior from the browser instance. Due to this, the context menu functions have been extended in the instance preview for more convenient work with the new browser. Operations with the browser window will be re-worked in future versions of ZennoPoster7. 

New context menu in the instance preview

The context menu functions have been extended in the instance preview for more convenient work with the new browser.

Added menu items:

Show — display browser window
Hide — hide browser window not closing browser actually

Continue — continue execution when user action is required

Benefits

The extended context menu allows to handle main ZennoPoster functions directly from the instance preview interface providing full control over ZennoBrowser instances without switching between different application windows.