Actions7
Overview
This node, named "Firecrawl," is designed to interact with the Firecrawl API to retrieve data related to crawl jobs. Specifically, the "Get crawl status" operation allows users to query the status of a particular crawl job by providing its unique Crawl ID. This functionality is useful in scenarios where you need to monitor or track the progress and results of web crawling tasks initiated through Firecrawl.
Practical examples include:
- Monitoring the completion status of a scheduled web crawl.
- Fetching real-time updates on a crawl job to trigger subsequent workflows based on its state.
- Integrating crawl status checks into larger automation pipelines for data extraction or analysis.
Properties
| Name | Meaning |
|---|---|
| Crawl ID | The unique identifier of the crawl job whose status you want to retrieve. Example: 1234abcd-5678-efgh-9012-ijklmnopqrst |
| Use Custom Body | A boolean flag indicating whether to send a custom request body instead of the default. Typically false for this operation. |
Output
The node outputs JSON data representing the status information of the specified crawl job. This JSON typically includes details such as the current state of the crawl (e.g., running, completed, failed), timestamps, and possibly metadata about the crawl results.
If the node supports binary data output, it would generally relate to any files or raw data retrieved from the crawl, but based on the provided code and properties, the primary output is structured JSON status information.
Dependencies
- Requires an API key credential for authenticating with the Firecrawl API.
- The base URL for the API defaults to
https://api.firecrawl.dev/v1but can be overridden via credentials configuration. - No additional external dependencies are indicated beyond standard HTTP requests to the Firecrawl service.
Troubleshooting
- Missing or invalid Crawl ID: Ensure that the Crawl ID is correctly provided and matches an existing crawl job; otherwise, the API will likely return an error or empty response.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Confirm network connectivity to the Firecrawl API endpoint.
- Unexpected API responses: Check if the API version or endpoint has changed; update the node or credentials accordingly.
Common error messages might include authentication failures, 404 not found for invalid Crawl IDs, or 400 bad requests if parameters are malformed.
Links and References
- Firecrawl API Documentation (assumed official docs for further details)
- n8n documentation on Creating Custom Nodes