Firecrawl icon

Firecrawl

Get data from Firecrawl API

Actions7

Overview

The Firecrawl node enables users to perform search queries and optionally scrape search results using the Firecrawl API. It is designed to retrieve structured data from web searches, making it useful for scenarios such as market research, competitive analysis, content aggregation, or any workflow requiring automated extraction of search engine results.

Typical use cases include:

  • Automating the collection of search result data based on specific queries.
  • Filtering search results by language, country, or time range.
  • Limiting the number of results returned to control data volume.
  • Using custom request bodies for advanced or specialized search requests.

Properties

Name Meaning
Query The search query string to be sent to the Firecrawl API.
Limit Maximum number of search results to return (minimum 1).
Time Based Search Optional parameter to filter search results based on a time range (e.g., past hour/day).
Language Language code to specify the language of the search results (default: "en").
Country Country code to specify the geographic region of the search results (default: "us").
Use Custom Body Boolean flag indicating whether to send a custom request body instead of standard fields.

Output

The node outputs JSON data representing the search results retrieved from the Firecrawl API. The structure typically includes an array of search result items with details such as titles, URLs, snippets, and possibly metadata depending on the API response.

If scraping is enabled or supported, the output may also contain additional extracted content beyond basic search metadata.

No binary data output is indicated in the source code.

Dependencies

  • Requires an API key credential for authenticating with the Firecrawl API.
  • The base URL defaults to https://api.firecrawl.dev/v1 but can be overridden via credentials configuration.
  • The node sends requests with JSON bodies and expects JSON responses.

Troubleshooting

  • Invalid or missing API key: Ensure that the API key credential is correctly configured and active.
  • Empty or malformed query: The "Query" property is required; providing an empty string will likely cause errors.
  • Exceeding limits: Setting the "Limit" property too high might lead to API rate limiting or performance issues.
  • Unsupported language or country codes: Verify that the language and country codes conform to expected standards (e.g., ISO codes).
  • Custom body usage: When "Use Custom Body" is enabled, ensure the custom body format matches the API requirements to avoid request failures.

Common error messages would relate to authentication failures, invalid parameters, or network connectivity issues. Checking the API documentation and ensuring correct property values usually resolves these.

Links and References

Discussion