Skip to main content
Get started
Node ReferenceBrowse Web Node
Node Reference

Browse Web Node

Screenshot and extract content from web pages.

The Browse Web node is a planned utility node for fetching and extracting content from web pages so downstream nodes can use it. It is designed to pull a live page into the workflow, including its visible content and a screenshot.

Not yet available
The Browse Web node is part of the planned utility-node set. It appears in the node reference catalog with its intended purpose, but it is not wired into Builder Studio execution yet. There is no Browse Web node type, canvas node, executor, or schema definition in the current product, so it cannot be added to a canvas or run today. This page documents the intended behavior so the contract is clear before the node ships.

Intended purpose

Browse Web is meant to screenshot and extract content from web pages, fetching and extracting web content for downstream use. The output would be available to later nodes — for example, feeding extracted page text into a text-generation step. It belongs to the utility and integration group, alongside Webhook Call and HTML Viewer.

How outbound calls work today

Builder Studio already supports reaching out to the network during a run through the Webhook Call node, which runs as an external-call execution step that makes outbound HTTP requests to external services. A Browse Web node would extend that category from raw HTTP requests to rendered-page retrieval, returning extracted content and a screenshot rather than a plain HTTP response.

What to use instead for now
Until the Browse Web node ships, use the Webhook Call node to fetch data from an HTTP endpoint or an API. Webhook Call returns the response for downstream nodes, though it does not render pages or capture screenshots the way Browse Web is intended to.

Related pages

Was this page helpful?