Wait For Element

Pause the workflow until something appears, becomes visible, disappears or shows a given text on the active tab.

What it does

Wait For Element checks the first element matching DOM Selector again and again (every Polling interval, 100 ms by default) until its Condition is met or Timeout runs out (5,000 ms by default).

Conditions:

• Exists: the element is on the page, even if hidden.
• Visible: it is on the page and shown (not hidden, not transparent, not zero size).
• Hidden: it is hidden or gone. Useful to wait for a loading spinner to disappear.
• Contains Text: its text includes Text (case-sensitive).

When time runs out, the node does not fail: it passes the item on with timedOut: true. Check that with an IF node when the next steps depend on the element.

When to use it

• After a click, a form submit or opening a page, wait for the result before reading it.
• Wait for a loading spinner to go away (Hidden) before taking a screenshot.
• Wait until a status shows “Completed” (Contains Text).
• When no element tells you the page is ready, a fixed pause with Wait is the fallback.

Inputs and settings

Réglage	Type	Ce que cela fait
DOM Selector OBLIG.(obligatoire)	Page element	The selector of the DOM element to interact with.
Condition OBLIG.(obligatoire)	Choice	Choose what condition to wait for. Options: Exists, Visible, Hidden, Contains Text. Par défaut : Exists
Text	Text	Text required for the Contains Text condition.
Timeout	Number	Maximum time to wait in milliseconds. Par défaut : 5000
Polling interval	Number	How often to check in milliseconds. Par défaut : 100

• DOM Selector: click the crosshair button in the field and click the element on the page, or type a CSS selector. For an element that is not there yet, type its selector (for example .results-list).
• Timeout and Polling interval are in milliseconds: 10000 is 10 seconds.

Outputs

• Output

Each output item has these fields:

Field	Type	What it holds
waitResult	Object

Shape of an output item

{
  "waitResult": {}
}

The incoming item passes through unchanged, with a waitResult field added:

• satisfied: true when the condition was met. timedOut: true when time ran out first.
• found: whether the element was on the page at the last check.
• elapsedMs: how long the node waited.
• selector and condition: what was checked.

Dependencies and credentials

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

Example workflow

1. UI Automation types a search term and clicks Search on a site.
2. Wait For Element with DOM Selector = .results-list, Condition = Visible and Timeout = 10000.
3. IF checks that {{ $input.waitResult.satisfied }} is true.
4. On the true branch, Get Structured Data reads the results.

Common issues

• timedOut is true every time. The selector never matches, or the condition is never met in time. Check the selector with Ping once the element is on screen, and raise Timeout for slow pages.
• The next node runs although the element never appeared. That is expected: a timeout does not stop the workflow. Branch on {{ $input.waitResult.satisfied }} with IF, or stop with Stop and Error.
• Contains Text never matches. The check is case-sensitive and uses the element’s full text. Pick the element that holds the text, and match the exact capitalization.
• 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: pause for a fixed time.
• Get Element Data: read the element once it is there.
• UI Automation: also has a Wait For Element step inside a list of actions.
• Tab Control: wait for a whole page to load.