Skip to main content
firecrawl.crawlWebsite starts a Firecrawl crawl and continues in a correlated child context after Firecrawl reports completion through a callback. It doesn’t hold an action invocation open while the crawl runs. Use it for related pages on one site. Use firecrawl.scrapeUrl for a single page. Inputs accept literal values or compatible signals. An optional second argument { account } selects the Firecrawl binding.

Example

automations/crawl-help-center.automation.ts
firecrawl.crawlWebsite introduces a protected callback trigger and therefore another possible root. Scope literal crawl inputs to the trigger that should start them, as shown above. Passing a signal in the crawl input also anchors the starter action to that signal’s context boundary.

Inputs

Output

Returns Firecrawl’s crawl job as { id, status, total, completed, creditsUsed?, expiresAt?, next?, data }. expiresAt is a Date. data contains Firecrawl documents in the same shape returned by firecrawl.scrapeUrl. Automate.ax supplies Firecrawl with a signed callback URL. The terminal delivery starts an independent root context, and correlation joins its crawl ID with the action that started the job. The callback capability authorizes access to the exact endpoint. It doesn’t create causal inheritance. A failed crawl fails the correlated action path. Use firecrawl.startWebsiteCrawl instead when you want the job ID immediately or need to provide your own webhook.