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/secrets.ts Workspace secrets store, the counterpart of the /secrets endpoints. Secrets are scoped by namespace: llm_provider keys are used by agents and scraping, function_env values are injected into function runs.
​
NotteClient
required

​
Usage

  • list: List secret metadata (never the values), optionally filtered by namespace.
  • store: Store (or overwrite) a secret and return its metadata.
  • get: Read the value of a secret by name within a namespace.
  • delete: Delete a secret by id (the id field of SecretMetadata).