Actions7
Overview
This node integrates with the Firecrawl API to retrieve data related to crawl jobs. Specifically, the "Get crawl status" operation fetches the current status of a specified crawl job by its unique Crawl ID. This is useful for monitoring and managing web crawling tasks, allowing users to programmatically check progress or results of crawls initiated elsewhere.
Practical examples include:
- Automatically checking if a web crawl has completed before triggering downstream processing.
- Monitoring crawl statuses in dashboards or alerting systems.
- Integrating crawl status checks into larger automation workflows that depend on crawl completion.
Properties
| Name | Meaning |
|---|---|
| Crawl ID | The unique identifier of the crawl 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. |
Output
The node outputs JSON data representing the status of the requested crawl job. This typically includes fields such as crawl progress, state (e.g., running, completed, failed), timestamps, and possibly metadata about the crawl. The exact structure depends on the Firecrawl API response but generally provides comprehensive details about the crawl's current state.
No binary data output is indicated.
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
- Missing or invalid Crawl ID: Ensure the Crawl ID is correctly provided and matches an existing crawl job; otherwise, the API may return errors or empty results.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Network issues or incorrect base URL: Confirm network connectivity and that the base URL is correct if customized.
- Unexpected API responses: Check if the Firecrawl API service is operational and review any error messages returned for guidance.
Links and References
- Firecrawl API Documentation (assumed official docs for further details)
- n8n documentation on creating custom nodes