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.
n8n is a workflow automation tool. The n8n-nodes-notte community node adds Notte as a step in any workflow, so a browser agent can run between your triggers, branches and downstream integrations without writing code.

​
Install the node

In your n8n instance, go to Settings → Community Nodes → Install and enter:
Self-hosted instances can install it directly instead:

​
Add your credentials

Create a Notte API credential with an API key from console.notte.cc. The credential also takes a base URL, which you only need to change if you are pointed at a non-default Notte deployment.

​
Nodes

​
Notte Agent Browser

The main node runs in one of three modes: Agent mode is the one to reach for when the task needs judgement - logging in, navigating a flow, reacting to what is on the page. Scrape mode is faster and cheaper when you only need data off a known URL. Function mode is for work you have already made repeatable: author the function once, then call it from as many workflows as you like.

​
Notte Trigger

The trigger node starts a workflow when a persona receives a new email or SMS. This is what closes the loop on signup and verification flows: an agent creates an account, the confirmation email lands in the persona’s inbox, and the trigger fires the next branch of your workflow.

​
Next steps

Browser Agents

What an agent can do with a task prompt

Functions

Turn a working run into a callable function

Personas

Identities with their own inbox and phone number

Fetch

Pull structured data out of a page