Skip to content
← Back to documentation
Technical Reference

Firecrawl

Extract structured data from websites using AI with natural language prompts

CategoryArtificial Intelligence
Authenticationcustom
Version0.4.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Firecrawl with Flows360

Extract structured data from websites using AI with natural language prompts

Use the Firecrawl connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 21 actions and no declared triggers.

Available actions

  • Scrape Website
  • Extract Structured Data
  • Crawl
  • Crawl Results
  • Map Websites
  • Scrape URL
  • Crawl Website
  • Get Crawl Results
  • Plus 13 additional declared actions.

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Firecrawl
  • Package: @activepieces/piece-firecrawl@0.4.0
  • Exact artifact digest: sha256:bc52afe422c8a93d43c08f6a1c10352eec6ccebbc3a764ed5fd046aeeed0f8cd
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Scrape Website (scrape), Scrape a website by performing a series of actions like clicking, typing, taking screenshots, and extracting data. Classification: read.
  • Extract Structured Data (extract), Extract structured data from multiple URLs using AI. Classification: read.
  • Crawl (crawl), Crawl multiple pages from a website based on specified rules and patterns. Classification: read.
  • Crawl Results (crawlResults), Get the results of a crawl job. Classification: read.
  • Map Websites (map), Input a website and get all the urls on the website. Classification: read.
  • Scrape URL (scrape_url), Fetch the content of a single web page in a chosen format. Classification: read.
  • Crawl Website (crawl_website), Crawl a website starting from a base URL and return the content of many pages. Classification: read.
  • Get Crawl Results (get_crawl_results), Get the status and accumulated page results of a crawl job by its ID. Classification: read.
  • Map Website (map_website), Discover and return the list of URLs reachable from a website. Classification: read.
  • Extract Data (extract_data), Extract structured data from one or more known URLs using AI. Classification: read.
  • Batch Scrape (batch_scrape), Start a batch job that scrapes a list of known URLs and returns a job ID. Classification: read.
  • Get Batch Scrape Results (get_batch_scrape_results), Get the status and accumulated page results of a batch scrape job by its ID. Classification: read.
  • Get Batch Scrape Errors (get_batch_scrape_errors), List the URLs that failed in a batch scrape job. Classification: read.
  • Cancel Batch Scrape (cancel_batch_scrape), Cancel an in-flight batch scrape job by its ID. Classification: read.
  • Get Crawl Errors (get_crawl_errors), List the URLs that failed or were blocked in a crawl job. Classification: read.
  • Cancel Crawl (cancel_crawl), Cancel an in-flight crawl job by its ID. Classification: read.
  • List Active Crawls (list_active_crawls), List the account's in-flight crawl jobs. Classification: read.
  • Search Web (search_web), Search the web for a keyword query and return matching result URLs. Classification: read.
  • Start Agent (start_agent), Start an autonomous Firecrawl (FIRE-1) agent job from a natural-language prompt. Classification: read.
  • Get Agent Status (get_agent_status), Get the status and result of a Firecrawl (FIRE-1) agent job by its ID. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects21
Supported actionsNot published
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Scrape Website Yes No Scrape a website by performing a series of actions like clicking, typing, taking screenshots, and extracting data.
Extract Structured Data Yes No Extract structured data from multiple URLs using AI.
Crawl Yes No Crawl multiple pages from a website based on specified rules and patterns.
Crawl Results Yes No Get the results of a crawl job.
Map Websites Yes No Input a website and get all the urls on the website.
Scrape URL Yes No Fetch the content of a single web page in a chosen format.
Crawl Website Yes No Crawl a website starting from a base URL and return the content of many pages.
Get Crawl Results Yes No Get the status and accumulated page results of a crawl job by its ID.
Map Website Yes No Discover and return the list of URLs reachable from a website.
Extract Data Yes No Extract structured data from one or more known URLs using AI.
Batch Scrape Yes No Start a batch job that scrapes a list of known URLs and returns a job ID.
Get Batch Scrape Results Yes No Get the status and accumulated page results of a batch scrape job by its ID.
Get Batch Scrape Errors Yes No List the URLs that failed in a batch scrape job.
Cancel Batch Scrape Yes No Cancel an in-flight batch scrape job by its ID.
Get Crawl Errors Yes No List the URLs that failed or were blocked in a crawl job.
Cancel Crawl Yes No Cancel an in-flight crawl job by its ID.
List Active Crawls Yes No List the account's in-flight crawl jobs.
Search Web Yes No Search the web for a keyword query and return matching result URLs.
Start Agent Yes No Start an autonomous Firecrawl (FIRE-1) agent job from a natural-language prompt.
Get Agent Status Yes No Get the status and result of a Firecrawl (FIRE-1) agent job by its ID.
Custom API Call Yes No Make a custom API call to a specific endpoint

Setup

Setup

  1. Add the Firecrawl connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-firecrawl@0.4.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 21 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Firecrawl connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-firecrawl@0.4.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.