Actions7
- Content Actions
- Navigation Actions
Overview
The node enables interaction with websites through a cloud-based browser instance. Specifically, the "Click on Page Element" operation under the "Navigation" resource allows users to programmatically click on a webpage element identified by a CSS selector. This is useful for automating web interactions such as clicking buttons, links, or other interactive elements on a page.
Common scenarios include:
- Automating form submissions by clicking submit buttons.
- Navigating through multi-step web processes that require user clicks.
- Triggering dynamic content loading by clicking specific page elements.
Example: After opening a browser and navigating to a webpage, you can use this node to click a "Load More" button to fetch additional content dynamically.
Properties
| Name | Meaning |
|---|---|
| WebSocket Address | The browser WebSocket address returned from the Open Browser operation; used to connect to the active browser session. |
| CSS Selector | The CSS selector string identifying the page element to click on. |
Output
The output JSON contains information about the page after the click action:
title: The title of the current page.url: The URL of the current page.content: The full HTML content of the page after the click.status: A message indicating success, e.g., "Click operation successful".clickedSelector: The CSS selector of the element that was clicked.
No binary data is output for this operation.
Dependencies
- Requires an API token credential for the cloud browser service to open and control browser instances.
- Uses Puppeteer library to connect to the browser via the provided WebSocket address.
- The node expects a valid WebSocket address obtained from a prior "Open Browser" operation.
Troubleshooting
- No page found in the browser: This error occurs if the browser instance has no open pages. 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, the node will wait indefinitely or until timeout. Verify the correctness of the CSS selector.
- Invalid WebSocket address: Make sure the WebSocket address is correctly copied from the "Open Browser" operation output.
- Browser connection issues: Network problems or expired sessions may cause failure to connect to the browser. Reopen the browser instance if needed.