PlaywrightInstall

Overview

This node allows direct control of a Chromium browser instance using the Playwright library connected via a Chrome DevTools Protocol (CDP) URL. It supports various browser automation operations such as navigating to URLs, clicking elements, filling inputs, taking screenshots, waiting for page events, and more.

The Get Executable Path operation specifically returns the file system path of the Chromium executable used by Playwright. This can be useful for debugging, environment setup verification, or when you need to launch Chromium manually outside of Playwright.

Practical examples:

• Retrieving the Chromium executable path to confirm which browser binary is being used in your automation environment.
• Using this path to configure other tools that require the Chromium binary location.
• Verifying Playwright installation and environment consistency across different machines.

Properties

Note: For the Get Executable Path operation, only the CDP URL property is relevant but it is hidden in the UI because this operation does not require connecting to a running browser instance.

Output

The output JSON contains two fields:

• operation: The name of the executed operation, here always "executablePath".
• result: A string representing the full file system path to the Chromium executable used by Playwright.

Example output JSON:

{
  "operation": "executablePath",
  "result": "/path/to/chromium"
}

No binary data is produced by this operation.

Dependencies

• Requires the Playwright Node.js library to be installed.
• Requires access to the Chromium browser executable bundled with Playwright.
• No external API keys or credentials are needed for this operation.
• The node expects a valid CDP WebSocket URL if other operations are used, but for Get Executable Path, no active connection is required.

Troubleshooting

• Common issues:

  • If the Playwright package is missing or improperly installed, the node will fail to retrieve the executable path.
  • Running in an environment where Playwright cannot find its bundled Chromium may cause errors or return incorrect paths.

• Error messages:

  • Unsupported operation: ... — indicates an invalid operation was selected; ensure "Get Executable Path" is chosen exactly.
  • Errors related to Playwright initialization usually indicate installation or environment problems.

• Resolution tips:

  • Ensure Playwright is correctly installed and compatible with your Node.js version.
  • Verify that the environment has permissions to access the Playwright Chromium executable.
  • Use the latest stable version of Playwright to avoid bugs.

Links and References

• Playwright Official Documentation
• Chromium Executable Path in Playwright
• Chrome DevTools Protocol