Actions6
Overview
The FireCrawl node's "Check Crawl Job Status" operation allows users to check the status of a specific crawl job by providing its unique Crawl Id. This is useful in workflows where you need to monitor or react to the progress or completion of web crawling tasks managed by the FireCrawl API. For example, after initiating a crawl, you can use this operation to periodically poll for its status and trigger subsequent actions once the crawl is complete.
Properties
| Display Name | Type | Description |
|---|---|---|
| Crawl Id | String | The ID of the crawl job. Required. |
| Use Custom Body | Boolean | Whether to use a custom body. Optional. |
- Crawl Id: Enter the unique identifier of the crawl job whose status you want to check.
- Use Custom Body: If enabled, allows sending a custom request body (usage depends on node configuration).
Output
- The output will be a JSON object containing the status and details of the specified crawl job. The exact structure depends on the FireCrawl API response, but typically includes fields such as job status, progress, and any error messages if applicable.
Dependencies
- External Service: Requires access to the FireCrawl API.
- Credentials: Needs a configured "FireCrawl API" credential in n8n, including the base URL (
baseUrl) and any required authentication tokens or keys.
Troubleshooting
- Invalid Crawl Id: If an incorrect or non-existent Crawl Id is provided, the node may return an error indicating that the job was not found.
- Authentication Errors: Missing or invalid credentials will result in authentication errors. Ensure your "FireCrawl API" credentials are correctly set up in n8n.
- API Connectivity Issues: Network problems or incorrect base URL settings can cause connection failures.
Links and References
- n8n Documentation
- FireCrawl API documentation (refer to your service provider for the official link)