Overview
This node interacts with the IFC Pipeline service to perform various file-related operations and job status checks. Specifically, the "Get Job Status" operation retrieves the current status of a specified job within the IFC Pipeline system. This is useful for monitoring asynchronous or long-running tasks submitted to IFC Pipeline, allowing users to programmatically check progress or completion.
Practical examples include:
- Automating workflows that depend on the completion of IFC Pipeline jobs by polling their status.
- Integrating job status checks into larger automation pipelines to trigger subsequent actions based on job outcomes.
Properties
| Name | Meaning |
|---|---|
| Job ID | The unique identifier of the job whose status you want to retrieve. This is required for the "Get Job Status" operation. |
Output
The output JSON contains the status information of the requested job as returned by the IFC Pipeline API. It typically includes fields describing the job's current state, progress, and any relevant metadata provided by the service.
The node does not output binary data for this operation; all output is structured JSON representing job status details.
Dependencies
- Requires an active connection to the IFC Pipeline API.
- Needs an API authentication credential configured in n8n to authorize requests to IFC Pipeline.
- Uses helper functions from bundled shared code to make HTTP requests and handle responses.
Troubleshooting
- Common issues:
- Providing an invalid or non-existent Job ID will likely result in an error or empty response.
- Network connectivity problems or incorrect API credentials can cause request failures.
- Error messages:
- Errors thrown by the node typically contain the message from the IFC Pipeline API. For example, "Job not found" indicates the Job ID does not exist.
- "No binary data exists on item!" errors are unrelated to this operation but may appear if other operations are used incorrectly.
- Resolution tips:
- Verify the Job ID is correct and corresponds to an existing job.
- Ensure API credentials are valid and have necessary permissions.
- Check network connectivity and endpoint accessibility.
Links and References
- IFC Pipeline official documentation (for API details and job status schema)
- n8n documentation on creating and using custom nodes and credentials