What can the Firecrawl integration do in StackOS?

The current catalog includes 4 Firecrawl actions across Web Retrieval. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Firecrawl?

No. Firecrawl remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.

Utilities plugin

Firecrawl

Web crawling and scraping provider.

4 supported actions1 capability groups

Supported work

What StackOS can do with Firecrawl.

The catalog reflects the actions currently available through the Utilities plugin. A workflow still decides which actions belong in the job and where approval is required.

Search Firecrawl actions

4 matching actions

Web RetrievalUses a paid service

Crawl Website

Start a bounded Firecrawl crawl for an agent-selected site.

Web RetrievalUses a paid service

Extract Web Data

Deferred Firecrawl structured extraction contract; execution needs async status polling before this action can be enabled.

Web RetrievalUses a paid service

Map Website URLs

Discover URLs from an agent-selected site.

Web RetrievalReads data

Scrape Web Page

Fetch and normalize a web page.

Direct answer

How does the Firecrawl integration work?

People continue using Firecrawl as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

Firecrawl

What StackOS can do with Firecrawl.

Crawl Website

Extract Web Data

Map Website URLs

Scrape Web Page

How does the Firecrawl integration work?

Related integrations.

Alibaba Wan

BytePlus ModelArk

Google Gemini Image