Actions7
Overview
The node "Firecrawl" is designed to interact with the Firecrawl API, specifically to retrieve the status of an extract job. This operation is useful when you have initiated a data extraction process via Firecrawl and want to monitor or check the current status of that extraction. Typical use cases include tracking progress, verifying completion, or handling errors in automated data workflows.
For example, after starting a data extract job, you can use this node to periodically poll the extract status by providing the Extract ID, enabling automation systems to react accordingly (e.g., proceed with further processing once extraction is complete).
Properties
| Name | Meaning |
|---|---|
| Extract ID | The unique identifier of the extract job whose status you want to retrieve. |
| Use Custom Body | A boolean flag indicating whether to send a custom request body instead of the default. |
- Extract ID is required and should be provided as a string matching the extract job's ID.
- Use Custom Body allows advanced users to override the default request body if needed.
Output
The node outputs JSON data representing the status of the specified extract job. This typically includes fields such as the current state of the extract (e.g., pending, running, completed), timestamps, any error messages, and possibly metadata about the extracted data.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Firecrawl API.
- The base URL defaults to
https://api.firecrawl.dev/v2but can be overridden via credentials configuration. - The node sends requests with headers specifying JSON content type and expects JSON responses.
Troubleshooting
Common issues:
- Providing an invalid or expired Extract ID will likely result in an error or empty response.
- Missing or incorrect API authentication will cause authorization failures.
- Network connectivity problems may prevent reaching the Firecrawl API endpoint.
Error messages:
- Authorization errors indicate issues with the API key; verify the credential setup.
- Not found or invalid extract ID errors suggest checking the correctness of the Extract ID.
- Timeout or connection errors require network troubleshooting or retry logic.
Links and References
- Firecrawl API Documentation (assumed official docs for more details on extract jobs and statuses)
- n8n documentation on creating custom nodes for further customization guidance