> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetgail.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetgail.com/_mcp/server.

# Web Extract

> Pulls specific fields off a web page, including pages that are only reachable through a search form.

The Web Extract node reads a web page and returns the exact fields you ask for.
You describe what you want in plain language, optionally point it at a starting
page, and it navigates the site, fills in search forms, clicks through to the
right page, and hands back the values it found. It is built for pages that hold
the data you need but offer no API to get at it.

## When to use it

* You need details from a public records site, such as a company's filing
  status or registered agent from a Secretary of State page.
* You want to read facts off a page that hides them behind a search box, where a
  plain link is not enough.
* You are pulling the same fields from many similar pages, like listing details
  across a set of property or product URLs.

## Inputs

| Field       | What it's for                                                                                                                                                                                                                            | Example                                                          |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Sources     | Up to ten starting pages to work from. Often a reference to results from an upstream [Web Search](/platform/workflows/node-reference/web-and-http/web-search). Leave it empty to let the extractor find the page from your prompt alone. | `https://search.sunbiz.org/Inquiry/CorporationSearch/ByName`     |
| Prompt      | Plain-language guidance describing what to find and any steps to get there, like typing a name into a search box and opening the first result.                                                                                           | "Search for Chen Insurance Group LLC and read its filing status" |
| JSON Schema | An optional structure that pins down the exact fields and shape of the result. Pairing it with a prompt gives the most reliable output.                                                                                                  | Fields for `fein`, `registered_agent`, and `status`              |

You must provide at least a prompt or a schema; providing both together works
best. When you give starting pages, the extractor stays within those sites and
does not wander off to unrelated ones.

## Outputs

| Field   | What you get back                                                      |
| ------- | ---------------------------------------------------------------------- |
| Results | The fields you asked for, filled in with the values found on the page. |

The names and types of the returned fields follow whatever you described in the
prompt or schema.

## Example

An agency needs to verify that Chen Insurance Group LLC is a real, active
business before quoting it. A Web Extract node starts on the state's corporation
search page, and its prompt tells the extractor to type the company name into
the search box, open the first matching result, and read the filing status,
registered agent, and federal tax ID off the detail page. A schema lists those
three fields so the result comes back in a predictable shape, ready for a
[Check](/platform/workflows/node-reference/logic-and-flow/check) step to confirm the
status is active.

![The Web Extract node configuration panel, showing sources, a prompt, and an optional JSON schema.](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/gail.docs.buildwithfern.com/677c08655e9a77423e2f5d3b6ab538d5ad70ba51cf4d32cb672e6fe8884a95aa/docs/pages/platform/workflows/assets/web-and-http-web-extract.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260823%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260823T232902Z&X-Amz-Expires=604800&X-Amz-Signature=38211a20228b7616e999042564024c1e487d36bc7f6a92fd2a533c6eb9fcada8&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

Extracting from a live site takes a little time, and empty results are a real
outcome: the page may load fine yet not contain what you asked for. Check that
the fields you need actually came back before a later step relies on them,
rather than assuming they are always present.

## Related nodes

#### [Web Search](/platform/workflows/node-reference/web-and-http/web-search)

Find the right pages first, then feed them into Web Extract.

#### [Agent](/platform/workflows/node-reference/ai/agent)

Reason over the extracted fields or turn them into a decision.

#### [Check](/platform/workflows/node-reference/logic-and-flow/check)

Turn an extracted value into a single labeled outcome.

#### [For Each](/platform/workflows/node-reference/logic-and-flow/for-each)

Extract from a whole list of pages, one at a time.