Actions6
Overview
The node "Firecrawl" is designed to interact with the Firecrawl API, specifically to retrieve the status of an extract job. The "Get Extract Status" operation allows users to query the current state of a data extraction process by providing the unique Extract ID. This is useful in scenarios where you have initiated a data extraction job and want to monitor its progress or confirm its completion before proceeding with further automation steps.
Practical examples include:
- Monitoring long-running data extraction tasks to trigger subsequent workflows once data is ready.
- Checking the status of scheduled or on-demand extracts to handle errors or retries.
- Integrating Firecrawl data extraction status checks into broader ETL (Extract, Transform, Load) pipelines.
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 (not used for this operation). |
Output
The node outputs JSON data representing the status of the specified extract job. The exact structure depends on the Firecrawl API response but typically includes fields such as job status (e.g., pending, running, completed, failed), timestamps, and possibly error messages or metadata about the extract.
If the node supports binary data output, it would relate to any downloadable content from the extract, but based on the provided code and properties, this operation focuses solely on JSON status information.
Dependencies
- Requires an active connection to the Firecrawl API endpoint at
https://api.firecrawl.dev/v1. - Needs an API authentication token credential configured within n8n to authorize requests.
- The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
Common Issues:
- Invalid or missing Extract ID will result in errors or empty responses.
- Network connectivity problems or incorrect API credentials can cause authentication failures.
- If the extract job ID does not exist or has expired, the API may return a not found or similar error.
Error Messages:
- Authentication errors indicate issues with the API key/token; verify credentials are correctly set up.
- 404 Not Found suggests the Extract ID is incorrect or the job no longer exists.
- Timeout or network errors require checking internet connectivity and API availability.
Links and References
- Firecrawl API Documentation: https://api.firecrawl.dev/docs (assumed URL based on baseURL)
- n8n Documentation on HTTP Request Nodes and Credentials: https://docs.n8n.io/