ActionFirecrawlUpdated September 2026

How do I extract structured data from a page?

Short answer: You can extract structured data in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Extract Structured Data action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Extract Structured Data in Firecrawl — start free All 8 Firecrawl actions

Extract Structured Data in Firecrawl — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
URL url	string	Required	Fully-qualified URL of the page to extract from.
Extraction Prompt prompt	string	Optional	Optional natural-language description of what to extract. Either Prompt or Schema (or both) must be set — Prompt alone lets the model pick the shape; Schema alone gives strict structure; together is most reliable.
Output Schema schema	json_schema	Optional	Optional JSON Schema describing the desired output shape. Define properties + types row-by-row. Either Schema or Prompt (or both) must be set.
Only Main Content only_main_content	boolean	Optional	Strip navigation/footer/sidebar boilerplate before extraction. Almost always true — cleaner extraction, fewer tokens, lower cost.

Sample request

{
  "url": "e.g. https://news.ycombinator.com",
  "prompt": "e.g. Extract the product name, price (number), and short description.",
  "schema": "{{trigger.schema}}",
  "only_main_content": "{{trigger.only_main_content}}"
}

Returns

{
  "data": {
    "json": {
      "title": "I Moved My Digital Stack to Europe",
      "points": 271
    },
    "metadata": {
      "sourceURL": "https://news.ycombinator.com"
    }
  },
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Extract Structured Data.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Firecrawl

2 Google Sheets triggers

HubSpot → Firecrawl

18 HubSpot triggers

FAQ

Questions about Extract Structured Data.

What does the Extract Structured Data action do in Firecrawl?

Pass a URL and a schema; Firecrawl extracts matching fields. For "scrape product details from this page into our DB" workflows where you want typed JSON rather than raw HTML.

What inputs does Extract Structured Data require?

Required: URL. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Firecrawl returns an error?

The run history shows the failed step with its input and the error message Firecrawl returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Extract Structured Data support batch operations?

Run Extract Structured Data inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Firecrawl's rate limits.

More actions