Actions10
Overview
The node provides an interface to interact with browser sessions using the Playwright API. Specifically, for the "Session" resource and the "Type Text" operation, it types specified text into a web page element identified by a CSS selector within an existing browser session.
This node is useful in automation workflows where you need to simulate user input on web pages, such as filling out forms, entering search queries, or interacting with input fields during web scraping or testing scenarios.
Example use case:
You have a browser session open on a login page and want to programmatically type a username or password into the respective input fields.
Properties
| Name | Meaning |
|---|---|
| Session ID | The unique identifier of the browser session where the text will be typed. |
| Selector | (Optional) A CSS selector string to locate the element on the page where text is typed. |
| Text | The actual text string to type into the targeted element. |
Output
The node outputs JSON data representing the result of the typing action. Typically, this might include confirmation of success or details about the typed text. The exact structure depends on the underlying Playwright API response but generally confirms that the text was entered into the specified element.
No binary data output is associated with this operation.
Dependencies
- Requires a valid connection to the Playwright API via an API key credential configured in n8n.
- The node depends on active browser sessions managed through the Playwright API.
- Proper session management (creation and maintenance) is necessary before performing the "Type Text" operation.
Troubleshooting
Common issues:
- Invalid or expired Session ID: Ensure the session ID corresponds to an active browser session.
- Incorrect or missing CSS selector: If the selector does not match any element, the typing action will fail.
- Empty or invalid text input: The "Text" property must be provided and non-empty.
Error messages:
"The operation "typeText" is not supported!"— This indicates an unsupported operation was requested; verify the operation name.- Errors related to element not found or session not found typically indicate issues with the selector or session ID.
Resolution tips:
- Verify the session is active and accessible.
- Double-check the CSS selector syntax and ensure it matches an element on the current page.
- Confirm that the text to type is correctly set and not empty.