Skip to main content
STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
Source: node-sdk/src/session.ts Evaluate JavaScript on the current page and return its result as a string. The result is stringified the way evaluate_js records it: objects and arrays as JSON, a JS null as the string "null". On failure the typed ActionExecutionError is thrown with the actual JavaScript error; pass raiseOnFailure: false to get the execution result envelope instead.

​
Parameters (overload 1)

​
string
required
​
{ raiseOnFailure?: true }

​
Returns (overload 1)

​
Parameters (overload 2)

​
string
required
​
{ raiseOnFailure: false }
required

​
Returns (overload 2)

​
Example