Short answer: Drop the "Firecrawl → Get Crawl Status" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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). |
{"crawl_id": "e.g. 1a2b3c4d-1234-5678-9abc-def012345678"}
{"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.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.