Actions13
- Agent Actions
- Datastore Actions
- Query Actions
- Reranker Actions
- LMUnit Actions
- Parser Actions
Overview
The node provides access to Contextual AI services, including parsing jobs. Specifically, the "Parse Status" operation under the "Parser" resource allows users to check the status of a previously submitted parse job by its Job ID. This is useful in workflows where asynchronous parsing tasks are submitted and their completion or progress needs to be monitored before proceeding.
Practical examples include:
- Monitoring the progress of document parsing jobs to trigger subsequent processing steps once parsing completes.
- Checking if a parsing task failed or succeeded to handle errors gracefully.
- Integrating with external systems that require confirmation of parsing status before data extraction.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the parse job whose status you want to check. |
| Authentication | Method of authentication to use; currently supports "API Key" for accessing the service. |
Output
The output JSON structure contains the response from the Contextual AI service regarding the status of the specified parse job. It typically includes fields such as job state (e.g., pending, completed, failed), timestamps, and possibly error messages or result summaries depending on the job's current status.
If the node supports binary data output, it would relate to any files or parsed content returned upon job completion, but this is not explicitly indicated in the provided code snippet.
Dependencies
- Requires an API key credential for authenticating requests to the Contextual AI service.
- The node depends on internal routing logic (
resourceRouter) to dispatch operations based on resource and operation parameters. - No additional external dependencies are evident from the static analysis.
Troubleshooting
Common issues:
- Invalid or expired Job ID leading to errors or empty responses.
- Authentication failures due to missing or incorrect API key.
- Network connectivity problems preventing communication with the Contextual AI service.
Error messages and resolutions:
- "Unauthorized" or similar: Verify that the API key credential is correctly configured and has necessary permissions.
- "Job not found": Confirm the Job ID is correct and that the job was successfully created.
- Timeouts or network errors: Check internet connection and service availability.
Links and References
- Contextual AI official documentation (hypothetical link)
- n8n documentation on creating custom nodes