Playwright
Quickstart: Playwright
Connect Playwright to a Notte browser session, interact with a real website, and extract page content.
Run this template
Clone just this template, configure Notte, and start the run.
Before running
- Have
NOTTE_API_KEYready. Generate an API key.
Need help? Join the Notte Slack.
What this Playwright template does
- Creates a managed Notte cloud browser session and controls it with Playwright.
- Uses Playwright for deterministic navigation and interaction against a real website.
- Uses Notte structured scraping to return extracted page content in a typed shape.
- Shows the handoff between browser infrastructure and Playwright code in one small script.
When to use this template
- You already know Playwright and want to run the same style of script on cloud browsers.
- Your workflow needs managed sessions instead of a local Chromium process.
- You want a starting point for authenticated flows, dynamic pages, or production browser automation.
- You are evaluating Notte as the infrastructure layer around Playwright, not as a replacement for Playwright.
Requirements
- A Notte API key in .env as NOTTE_API_KEY.
- Python users should keep notte-sdk[playwright] in the inline uv script metadata.
- Node.js users should install the template dependencies before running npm start.
- A target website with selectors or page structure stable enough for deterministic Playwright actions.
How it connects to Notte
- Session: a Notte-hosted browser instance with managed lifecycle, isolation, and observability.
- CDP: Chrome DevTools Protocol, the wire protocol Playwright uses to control the remote browser.
- Playwright: the automation library for deterministic page interactions, locators, waits, and assertions.
- Structured scrape: a Notte extraction call that converts the page into data matching a Pydantic model.
Next steps
- Read the Notte for Playwright page at /playwright for the broader positioning and CDP examples.
- Read /what-is-notte for the platform overview and how sessions, agents, functions, profiles, and vaults fit together.
- Review the CDP glossary entry at /glossary/browser-automation/what-is-chrome-devtools-protocol-cdp.
- Use browser profiles when the Playwright workflow needs authenticated state across repeated runs.