Actions8
Overview
The node "Remote Playwright" allows users to interact with a remote Playwright instance through n8n workflows. Specifically, the CreateInstance operation under the Instance resource enables creating a new Playwright instance remotely. This is useful for automating browser tasks such as web scraping, testing, or any scenario where controlling a browser session programmatically is needed.
A practical example would be automating login flows on websites or capturing screenshots of pages by creating and managing browser instances remotely without running Playwright locally.
Properties
| Name | Meaning |
|---|---|
| Custom Instance ID | Insert the Playwright custom instance ID. If not provided, a random ID will be generated. |
Output
The node outputs JSON data representing the result of the interaction with the remote Playwright service. For the CreateInstance operation, this typically includes details about the newly created Playwright instance such as its ID and status.
If the node supports binary data output (not explicitly shown in the provided code), it would represent browser-related artifacts like screenshots or PDFs, but this is not evident from the current static analysis.
Dependencies
- Requires access to a remote Playwright API endpoint.
- Needs an API URL configured via credentials or environment variables (
instanceUrl). - Optionally uses an API key or token for authentication (referred generically as "an API key credential").
- The node depends on HTTP request capabilities to communicate with the remote Playwright service.
Troubleshooting
- Common issues:
- Missing or incorrect API URL configuration can cause connection failures.
- Providing an invalid or duplicate custom instance ID might lead to errors when creating instances.
- Network connectivity problems between n8n and the remote Playwright server.
- Error messages:
- Connection refused or timeout errors indicate unreachable remote service.
- Authentication errors suggest missing or invalid API credentials.
- Validation errors may occur if the custom instance ID format is incorrect.
To resolve these, verify the API URL, ensure valid credentials are set up, and confirm network accessibility.