Get Element Data

Read everything about one element on the active tab: its text, value, link, attributes, position and whether it is visible.

What it does

Get Element Data finds the first element that matches DOM Selector on the active tab and returns a description of it. The most useful fields:

• found: true when the element exists. When it is false, the other fields are left out.
• text: the element’s visible text. html: the HTML inside it.
• value: what is typed or chosen in a form field. A checkbox gives true or false; a multi-select list gives a list of the chosen values.
• href for links, src for images, video and audio.
• attributes: every attribute on the element, such as data-price or aria-expanded.
• visible: whether the element is shown on screen. boundingBox: its position and size.
• name: a readable name taken from its label, title or text.

When the element is not on the page, the node does not fail: it returns found: false, so you can branch on it.

When to use it

• Read one value precisely: a price, a status badge, the text in a search box.
• Check a state before acting: is the “Next” button visible, is the checkbox ticked?
• To read many similar elements (rows, cards), use Get Structured Data or Get All HTML with HTML Extract.

Inputs and settings

Setting	Type	What it does
DOM Selector REQ(required)	Page element	The selector of the DOM element to interact with.
Output field name	Text	Wrap the element data under this field name. Leave empty to return the object directly.

• DOM Selector: click the crosshair button in the field, then click the element on the page, or type a CSS selector such as #price. The Ping button flashes what it matches.
• Output field name: set it (for example price) to get { "price": { … } }, which keeps things tidy when you read several elements in a row.

Outputs

• Output

With Output field name empty, read the fields directly, for example {{ $input.text }} or {{ $input.attributes['data-sku'] }}. With it set to price, use {{ $input.price.text }}.

Dependencies and credentials

None. This node needs no connection and has no slots for other nodes.

Example workflow

1. A Schedule trigger runs every hour.
2. Tab Control, Operation = Open, opens the product page with Wait For Load on.
3. Get Element Data with DOM Selector = the price element and Output field name = price.
4. IF checks that {{ $input.price.found }} is true. On the true branch, a Browser Notification shows {{ $input.price.text }}.

Common issues

• found is false. The selector matched nothing at the moment the node ran. Check it with Ping, and add Wait For Element before this node if the element appears late. A selector picked on one page may not exist on another.
• text is empty but you can see text. The text may be drawn inside an embedded frame, or in a child element; try selecting the inner element.
• value is missing. Only form fields (inputs, text areas, lists) have a value. For other elements read text.
• The node fails outside the extension. This node runs in the browser extension; install it or run the workflow from the extension.

Related nodes

• Wait For Element: wait until the element is there.
• Get Accessibility Tree: all buttons, links and fields at once.
• Get Structured Data: many rows from a table or list.
• IF: branch on what you read.