Actions7
Overview
The Firecrawl node is designed to interact with the Firecrawl API, allowing users to retrieve data efficiently. This node is particularly beneficial for scenarios where users need to extract web crawling data or perform automated tasks related to web scraping. For example, a user might utilize this node to gather information from various websites for analysis or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Use Custom Body | Whether to use a custom body (true/false) |
Output
The output of the Firecrawl node will be structured in JSON format, containing the data retrieved from the Firecrawl API. The exact structure of the output will depend on the specific data returned by the API based on the request made. If the node can also output binary data, it would typically represent files or images fetched from the API.
Dependencies
- An API key credential is required to authenticate requests to the Firecrawl API.
- The base URL for the API can be configured, defaulting to
http://localhost:3002/v1if not specified.
Troubleshooting
Common issues users might encounter include:
- Authentication Errors: If the API key is missing or incorrect, users may receive authentication failure messages. Ensure that the correct API key is provided in the credentials.
- Network Issues: Users may face connectivity problems if the base URL is incorrect or the server is down. Verify the base URL and check server status.
- Invalid Input: If the input properties are not set correctly, the node may throw errors indicating invalid parameters. Double-check the property settings, especially the "Use Custom Body" option.
Links and References
- Firecrawl API Documentation (replace with actual documentation link)
- n8n Documentation for general usage and troubleshooting tips.