ActionFirecrawlUpdated September 2026

How do I check Firecrawl crawl progress?

Short answer: You can get crawl status in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Get Crawl Status action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Crawl Status in Firecrawl — start free All 8 Firecrawl actions

Get Crawl Status 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
Crawl ID crawl_id	string	Required	The crawl job id returned by Crawl Site (the `id` field of that op's response).

Sample request

{
  "crawl_id": "e.g. 1a2b3c4d-1234-5678-9abc-def012345678"
}

Returns

{
  "data": [
    {
      "markdown": "...",
      "metadata": {
        "url": "..."
      }
    }
  ],
  "next": null,
  "total": 50,
  "status": "completed",
  "completed": 50,
  "expiresAt": "2026-05-16T12:00:00.000Z",
  "creditsUsed": 50
}

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

Triggered by

Apps that pair well as the trigger for Get Crawl Status.

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 Get Crawl Status.

What does the Get Crawl Status action do in Firecrawl?

Returns the current status of a running crawl — pages crawled, pages discovered, completion percentage. Poll until status=completed before consuming results.

What inputs does Get Crawl Status require?

Required: Crawl ID. 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 Get Crawl Status support batch operations?

Run Get Crawl Status 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