nodes / extension / ui
Delete UI Elements
Delete selected UI elements from the opened web page
Remove elements you pick (banners, pop-ups, ads, sidebars) from the page open in the active tab.
What it does
Section titled “What it does”Delete UI Elements removes from the active tab every element that matches each selector in Elements, not just the first one. The change is only on your screen: reloading the page brings everything back, and the website itself is not changed.
The incoming item is passed on unchanged, so the workflow can continue.
When to use it
Section titled “When to use it”- Clear cookie banners, newsletter pop-ups or chat bubbles before taking a screenshot or reading the page.
- Remove ads, menus and sidebars so Get All Text reads only the article.
- Clean up a page for reading, on every visit, with a Page Load trigger.
- To hide something without removing it, set
displaytononewith Set Element Attribute Style.
Inputs and settings
Section titled “Inputs and settings”| Setting | Type | What it does |
|---|---|---|
| Elements (required) | List | List of DOM elements to delete from the opened web page. |
Add one entry per thing to remove. In each Target Element, click the crosshair button and click the element on the page, or type a CSS selector. A selector that matches many elements, such as .ad-slot, removes them all.
Outputs
Section titled “Outputs”-
Output
The incoming item, unchanged.
Dependencies and credentials
Section titled “Dependencies and credentials”None. This node needs no connection and has no slots for other nodes.
Example workflow
Section titled “Example workflow”- A Page Load trigger with URL Patterns =
https://news.example.com/*. - Delete UI Elements with two entries in Elements: the cookie banner and
.newsletter-popup. - Screenshot Page with Mode = Full Page captures the clean page.
Common issues
Section titled “Common issues”- The element is still there. The selector matched nothing at the moment the node ran, often because the pop-up appears a few seconds later. Add Wait For Element with Condition = Exists before this node, and check the selector with Ping.
- The element comes back. Some sites add it again after a while or on scroll, and reloading always restores the page. Run the node again, or hide it with Set Element Attribute Style.
- Too much was removed. A broad selector (such as
div) matches many elements. Pick a more specific one. - The node fails outside the extension. This node runs in the browser extension; install it or run the workflow from the extension.
Related nodes
Section titled “Related nodes”- Set Element Attribute Style: hide or restyle instead of removing.
- Highlight Elements: check what a selector matches before deleting.
- Screenshot Page: capture the cleaned-up page.