Actions6
Overview
The FireCrawl node integrates with the FireCrawl API, allowing users to interact with its endpoints from within n8n workflows. This node is designed for scenarios where you need to send data to or retrieve data from the FireCrawl service, such as crawling web pages, extracting information, or automating content analysis tasks.
Practical examples:
- Automate website crawling and extract structured data.
- Integrate FireCrawl's capabilities into larger automation pipelines (e.g., after scraping a site, process the results further).
- Use in conjunction with other nodes to enrich or analyze web content.
Properties
| Display Name | Type | Meaning |
|---|---|---|
| Use Custom Body | Boolean | Whether to use a custom body in the request payload. |
- Use Custom Body: If enabled, allows you to define a custom request body when interacting with the FireCrawl API. This provides flexibility for advanced use cases where the default request structure does not suffice.
Output
- The node outputs a
jsonfield containing the response from the FireCrawl API. The exact structure of this output depends on the specific resource and operation invoked, but it will generally reflect the data returned by the FireCrawl endpoint you are using. - No binary data is produced by this node.
Dependencies
- External Service: Requires access to the FireCrawl API.
- API Key/Credentials: You must configure the "FireCrawl API" credentials in n8n, including the base URL (
baseUrl) and any required authentication details. - n8n Configuration: Ensure that the FireCrawl API credentials are set up in your n8n instance.
Troubleshooting
Common Issues:
- Invalid Credentials: If the API key or base URL is incorrect, requests will fail. Double-check your credential setup in n8n.
- Missing Required Fields: If required fields are not provided, the API may return an error. Ensure all necessary properties are filled out.
- Custom Body Errors: If "Use Custom Body" is enabled but the body format is invalid, the API may reject the request. Validate your custom body against the FireCrawl API documentation.
Error Messages:
- 401 Unauthorized: Indicates issues with API credentials. Re-enter your API key and base URL.
- 400 Bad Request: Usually due to malformed input or missing required parameters. Review your input fields and custom body.
- 404 Not Found: The requested resource or endpoint does not exist. Check the resource and operation settings.