Start free
ActionFirecrawlUpdated June 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.

FieldTypeRequiredDescription
Crawl ID
crawl_id
stringRequiredThe 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.

Gmail → Firecrawl
1 Gmail triggers
Slack → Firecrawl
13 Slack triggers
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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Get Crawl Status support batch operations?
Yes. Run Get Crawl Status inside a Loop node to process arrays. TinyCommand handles Firecrawl's rate limits automatically so you don't have to throttle manually.
More actions

Other Firecrawl actions.

Action
Crawl Site
Starting from a URL, Firecrawl follows links and fetches every page within scope. Returns markdown-formatted content of each. For "ingest a docs site into a RAG index" or "build a knowledge base from a brand's blog" workflows.
Action
Extract Structured Data
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.
Action
Get Firecrawl Agent Result
Polls an agent task for completion and returns the result. For Firecrawl's agentic-scraping workflows that perform multi-step browse tasks.
Action
Map Site URLs
Returns the URL list of a site without fetching content — the fast preflight before deciding what to crawl. Useful for "find all pages under /blog" or "count pages on this competitor's site" inventory workflows.
Action
Run Firecrawl Agent
Runs an agentic browse task — Firecrawl's agent navigates the site and performs the configured extraction goal. For complex scraping that requires sequential page navigation or form interaction.
Action
Scrape URL
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.
Get Crawl Status in Firecrawl — start free