• Custom n8n node
  • Web Automation
  • AI-agent tool

Playwright browser

Durable, multi-engine browser automation for n8n workflows, with a session that survives Wait nodes and worker restarts.

How it works in practice

Statements collected from portals with no integration

How we apply it

It is the engine behind our bank statement download robot: three banks and 70+ client companies, collected unattended twice a month.

This node automates web portals that have no API: log in, navigate, fill forms, click, wait, extract text and download reports. It covers Chromium, a stealth Chromium build (CloakBrowser) and Firefox for sites with bot protection, and it can attach to an already running Chrome over the DevTools protocol. Execute Custom Code is the escape hatch: your own Playwright code with the live page and the n8n context available.

The reason it exists is the session. A browser held in a single process is lost on a restart or when another worker picks the execution up, which makes long portal flows with Wait nodes or queue-mode workers fragile. Here one browser session is shared across the whole workflow, its state is persisted to disk and heartbeated, and it is recovered on another worker if needed. Sessions expire after 8 hours, or 4 hours of inactivity, and can be pinned or extended. Screenshots are available on nearly every activity and never fail the step, and downloads are captured properly even when they arrive as streams or blob URLs.

It is the node we use most by volume: 324 node instances across 21 production workflows, mostly click, wait for selector, fill, custom code and download. Typical jobs are logging in to a bank or utility portal, setting a date range and downloading the statement, or submitting data into a government or supplier form. Pair it with the Passbolt node so passwords never sit in the workflow.

Limits: the node installs no browser, so the host or container image must provide one. The heartbeat that detects finished executions needs an n8n API key, which is entered as a node parameter rather than an n8n credential.

For your technical team: it installs from npm as

n8n-nodes-kt-playwright

What it means for you

  • No more clicking through portals by hand

  • Works with sites that offer no integration

  • The month-end no longer depends on who is in the office

Want Playwright browser in your n8n?

Tell us what the workflow has to do and what it connects to. We will say whether this node covers it as it stands, what we would add, and when a different approach is the better one.