CloudBrowser

Overview

The node enables interaction with websites through a cloud-based browser instance. Specifically, the "Click on Page Element" operation allows users to programmatically click on a webpage element identified by a CSS selector within an existing browser session connected via a WebSocket address.

This is useful in automation workflows where you need to simulate user interactions on web pages, such as clicking buttons, links, or other interactive elements to trigger navigation, form submissions, or dynamic content loading.

Practical example:

• Automate clicking a "Load More" button on a product listing page to fetch additional items before scraping data.
• Simulate clicking a login button after filling credentials on a webpage.

Properties

Output

The output JSON object includes:

• title: The title of the current page after the click action.
• url: The URL of the current page after the click action.
• content: The full HTML content of the page after the click action.
• status: A message indicating success of the click operation ("Click operation successful").
• clickedSelector: The CSS selector that was clicked.

No binary data is output for this operation.

Dependencies

• Requires an active cloud browser service accessible via API with an API token credential.
• Uses Puppeteer library to connect to the browser instance over the provided WebSocket address.
• The node expects the WebSocket address from a previously opened browser session (via "Open Browser" operation).
• Proper API authentication token must be configured in the node credentials.

Troubleshooting

• Error: No page found in the browser
  This occurs if the browser session has no open pages/tabs. Ensure the browser is properly opened and a page is loaded before attempting to click.
• Timeout waiting for selector
  If the CSS selector does not match any element or the element takes too long to appear, the node will error. Verify the correctness of the CSS selector and that the page is fully loaded.
• Invalid WebSocket address
  If the WebSocket address is incorrect or expired, connection to the browser will fail. Confirm the WebSocket address is valid and corresponds to an active browser session.
• API authentication errors
  Ensure the API token credential is valid and has permissions to control the cloud browser service.

Links and References

• Puppeteer Documentation – For understanding browser automation concepts used internally.
• CSS Selectors Reference – To craft correct selectors for page elements.
• Cloud browser service API documentation (not publicly linked here) for details on opening and managing browser sessions.