Overview

This node interacts with the Firecrawl API to retrieve the status of a batch scrape job. It is useful for monitoring the progress or completion of web scraping tasks that have been submitted as batch jobs. For example, a user can input a batch ID to check if the scraping job has finished and to get details about the scrape results.

Use Case Examples

1. Checking the status of a batch scrape job by providing its batch ID.
2. Monitoring multiple batch scrape jobs by repeatedly querying their statuses.

Properties

Output

JSON

• batchId - The ID of the batch scrape job queried.
• status - Current status of the batch scrape job (e.g., pending, running, completed).
• results - Data or metadata returned from the batch scrape job, such as scraped content or error details.

Dependencies

• Firecrawl API key credential

Troubleshooting

• Ensure the Batch ID is correct and corresponds to an existing batch scrape job; otherwise, the API may return an error or no data.
• If using a custom body, verify the body format matches the API requirements to avoid request failures.
• Check network settings such as proxy and SSL options if requests fail due to connectivity or certificate issues.
• Timeout errors may occur if the server is slow to respond; consider increasing the timeout setting if needed.

Links

• Firecrawl API Documentation - Batch Scrape Status - Official API documentation for retrieving batch scrape job status.