Actions10
Click
AI-generatedOverview
This node allows direct control of a Chromium browser instance using the Playwright library connected via a Chrome DevTools Protocol (CDP) URL. It enables automation of browser actions such as clicking elements, filling inputs, navigating to URLs, taking screenshots, and waiting for page events or selectors.
Common scenarios include:
- Automating web UI testing by simulating user interactions.
- Scraping or extracting data from dynamic web pages.
- Capturing screenshots of web pages for monitoring or reporting.
- Waiting for specific page states or elements before proceeding in a workflow.
For example, you can use this node to navigate to a login page, fill in credentials, click the submit button, wait for navigation to complete, and then take a screenshot of the logged-in dashboard.
Properties
| Name | Meaning |
|---|---|
| CDP URL | Chrome DevTools Protocol URL to connect to the browser (e.g., ws://localhost:9222/...) |
| Selector | Playwright selector of the element to interact with (CSS selector or other supported syntax) |
Note: The above properties are relevant for the Click operation.
Output
The node outputs an array of items corresponding to each input item processed. Each output item contains a json field with at least the following structure:
{
"operation": "click"
}
This indicates the operation performed. For the Click operation, no additional data is returned in the output JSON.
No binary data is output for the Click operation.
Dependencies
- Requires a running Chromium-based browser instance exposing a Chrome DevTools Protocol WebSocket URL.
- The node uses the Playwright library to connect over CDP and perform browser automation.
- The user must provide a valid CDP URL to connect to the browser.
- No additional API keys or external services are required beyond access to the browser instance.
Troubleshooting
- Connection issues: If the node cannot connect to the provided CDP URL, ensure the browser is running with remote debugging enabled and the URL is correct.
- Selector not found: If the specified selector does not match any element, the click action will fail. Verify the selector syntax and that the element exists on the page.
- Unsupported operation error: This node only supports predefined operations; specifying an unsupported operation will throw an error.
- Timeouts: Operations may fail if the browser or page is slow to respond. Adjust timeouts or ensure the page is fully loaded before interacting.