Actions8
Overview
The node provides an operation to release a Playwright browser instance that was previously created and identified by an instance ID. This is useful in automation workflows where you manage multiple browser instances remotely and need to clean up or free resources after completing tasks such as navigation, clicking, filling inputs, or extracting data.
Typical use cases include:
- Closing a remote browser session after scraping or testing.
- Releasing resources to avoid memory leaks or unnecessary consumption.
- Managing lifecycle of browser instances in complex automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Instance ID | The unique identifier of the Playwright browser instance to be released. |
| Close Browser on error | Whether to automatically close the browser if an error occurs during the release action. |
Output
The node outputs JSON data representing the result of the release operation. Typically, this would confirm whether the instance was successfully released or if any errors occurred. There is no indication of binary data output for this operation.
Dependencies
- Requires access to a remote Playwright service endpoint configured via credentials (an API key or token) and base URL.
- The node expects the remote Playwright API to support instance management operations including releasing instances.
- Proper authentication credentials must be set up in n8n to communicate with the remote Playwright service.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Instance ID will likely cause the release operation to fail.
- Network or authentication errors when connecting to the remote Playwright API can prevent successful release.
- If "Close Browser on error" is enabled, the browser will be closed automatically on failure; otherwise, it may remain open causing resource leaks.
Error messages:
- Errors related to instance not found or already released indicate incorrect or stale Instance IDs.
- Authentication errors suggest missing or invalid API credentials.
- Timeout or connection errors imply network issues or misconfigured remote service URLs.
To resolve these:
- Verify the Instance ID is correct and corresponds to an active browser instance.
- Ensure API credentials and base URL are correctly configured.
- Check network connectivity to the remote Playwright service.
Links and References
- Playwright Official Documentation
- n8n Documentation on Credentials
- Remote Playwright API (if available) (replace with actual URL if known)