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/files.ts Upload a file to the session. A string is read as a local path and its basename becomes the uploaded filename unless uploadFileName is set.

​
Parameters

​
UploadableFile
required
Local file path, Blob, File, or buffer to upload.
​
string
Optional stored filename. Local paths default to their basename; File objects keep their name.

​
Returns

Metadata for the uploaded file, including its ID, name, and size.

​
Raises

  • NotteAPIError if the storage API request fails.
  • InvalidRequestError if storage has not been bound to a session.
  • InvalidRequestError if a supplied local path is not a file.

​
Example