Firecrawl

Overview

The Firecrawl node is designed to interact with the Firecrawl API, specifically to retrieve the status of a crawl job. This functionality is particularly useful for users who need to monitor the progress or results of web crawling tasks. Common scenarios include checking if a specific crawl has completed, understanding its current state, or troubleshooting issues related to web data extraction processes. For example, a user might want to verify whether a crawl identified by a specific ID has finished successfully or is still in progress.

Properties

Output

The output of this node will typically be a JSON object containing the status of the specified crawl job. The structure may include fields such as the crawl's current state, any error messages, and additional metadata related to the crawl process. If the node can output binary data, it would represent files or resources associated with the crawl.

Dependencies

This node requires an API key credential for authentication with the Firecrawl API. Additionally, it expects the base URL for the API to be configured, which defaults to http://localhost:3002/v1 unless specified otherwise in the credentials.

Troubleshooting

Common issues users might encounter include:

• Invalid Crawl ID: If the provided crawl ID does not exist or is incorrectly formatted, the node may return an error indicating that the crawl could not be found. To resolve this, ensure that the crawl ID is correct and exists in the system.
• Authentication Errors: If the API key credential is missing or incorrect, users may receive an authentication error. Verify that the correct API key is set up in the n8n credentials.
• Network Issues: If there are connectivity problems with the Firecrawl API, users may see timeout errors. Check network settings and ensure that the API endpoint is reachable.

Links and References

• Firecrawl API Documentation (replace with actual documentation link)
• n8n Documentation