ActionFirecrawlUpdated September 2026

How do I scrape a single URL with Firecrawl?

Short answer: You can scrape url in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Scrape URL action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Scrape URL in Firecrawl — start free All 8 Firecrawl actions

Scrape URL 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 to scrape.
Formats formats	array	Optional	Output formats. Any combination of: markdown, html, rawHtml, links, screenshot, json.
Only Main Content only_main_content	boolean	Optional	Strip nav/footer/sidebar boilerplate so the markdown is just the article. Set false if you need the full page.
Wait For (ms) wait_for	number	Optional	Milliseconds to wait after page load before scraping. Useful for JS-rendered pages.
Timeout (ms) timeout	number	Optional	Hard cap on the scrape duration. Default ~30 seconds; raise for slow pages.
Mobile Viewport mobile	boolean	Optional	Render the page as a mobile browser. Useful for sites with mobile-only content or different mobile layouts.
Proxy proxy	options	Optional	Proxy strategy. Use 'stealth' for sites that return 403/blocked with the default.

Sample request

{
  "url": "https://example.com",
  "formats": "{{trigger.formats}}",
  "only_main_content": "{{trigger.only_main_content}}",
  "wait_for": 2000,
  "timeout": 30000
}

Returns

{
  "data": {
    "html": "<html>...</html>",
    "links": [
      "https://example.com/about",
      "https://example.com/contact"
    ],
    "actions": [],
    "markdown": "# Example\n...",
    "metadata": {
      "title": "Example",
      "sourceURL": "https://example.com",
      "description": "..."
    }
  },
  "success": true
}

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

Triggered by

Apps that pair well as the trigger for Scrape URL.

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 Scrape URL.

What does the Scrape URL action do in Firecrawl?

Fetches and returns cleaned markdown for a single URL. Handles JavaScript rendering and bot evasion. The right tool for "extract content from this one URL for LLM consumption" workflows.

What inputs does Scrape URL 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 Scrape URL support batch operations?

Run Scrape URL 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