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 job by its unique ID.
Common scenarios include:
- Monitoring long-running data extraction jobs to know when they complete.
- Integrating Firecrawl data extraction status checks into automated workflows.
- Triggering subsequent actions based on the completion or failure status of an extract job.
For example, after starting an extract job in Firecrawl, you can use this node to periodically poll the job status until it completes, then proceed to download or process the extracted data.
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 (true) or not (false). |
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 state (e.g., pending, running, completed), progress details, timestamps, and any error messages if applicable.
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 JSON content type and expects JSON responses.
Troubleshooting
- Invalid Extract ID: If the provided Extract ID is incorrect or does not exist, the API may return a 404 or error response. Verify the Extract ID is correct.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key credential is properly configured.
- Network Issues: Connectivity problems to the Firecrawl API endpoint will cause request failures. Check network access and proxy settings if applicable.
- Custom Body Usage: If "Use Custom Body" is enabled but the body content is malformed or inappropriate, the API may reject the request. Use this option only if you understand the required request format.
Links and References
- Firecrawl API Documentation (for detailed API endpoints and response formats)
- n8n Documentation on Creating Custom Nodes