ActionFirecrawlUpdated September 2026
How do I retrieve a Firecrawl agent result?
Short answer: You can get firecrawl agent result in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Get Firecrawl Agent Result 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.
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 |
|---|---|---|---|
Agent Job ID agent_id | string | Required | The agent job id returned by Run Agent (the `id` field of that op's response). |
Sample request
{"agent_id": "e.g. 019e216a-e71f-753c-b876-7230fa0a6cd4"}
Returns
{"data": {"title": "I Moved My Digital Stack to Europe"},"model": "spark-1-pro","status": "completed","success": true,"expiresAt": "2026-05-14T12:58:46.741Z","creditsUsed": 0}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Get Firecrawl Agent Result.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Get Firecrawl Agent Result.
What does the Get Firecrawl Agent Result action do in Firecrawl?
Polls an agent task for completion and returns the result. For Firecrawl's agentic-scraping workflows that perform multi-step browse tasks.
What inputs does Get Firecrawl Agent Result require?
Required: Agent Job 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 Firecrawl Agent Result support batch operations?
Run Get Firecrawl Agent Result 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
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.
ActionExtract 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.
ActionGet Crawl Status
Returns the current status of a running crawl — pages crawled, pages discovered, completion percentage. Poll until status=completed before consuming results.
ActionMap 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.
ActionRun 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.
ActionScrape 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.