Overview
This node integrates with the IFC Pipeline service to perform various file-related operations such as uploading files, downloading files, listing directories, and checking job statuses. It is particularly useful in workflows that involve managing IFC (Industry Foundation Classes) files or related data formats within the IFC Pipeline environment.
For the Upload File operation specifically, the node uploads a binary file from the workflow into the IFC Pipeline system. This is beneficial when automating the transfer of design or data files (e.g., IFC, IDS, CSV) into the pipeline for further processing or storage.
Practical example:
- Automatically upload an IFC model file generated by a BIM software into IFC Pipeline for validation or sharing.
- Upload CSV reports or IDS files as part of a data integration workflow.
Properties
| Name | Meaning |
|---|---|
| File Type | The type of file to upload. Options: IFC, IDS, CSV, Other. |
| Binary Property | The name of the binary property on the input item that contains the file data to upload. |
Output
The output of the Upload File operation is a JSON object representing the response from the IFC Pipeline API after the file upload. This typically includes metadata about the uploaded file or confirmation details.
The output structure is wrapped in an array of items, each corresponding to an input item processed. Each item contains a json field with the API response data.
No binary data is output by this operation; it only returns JSON metadata.
Dependencies
- Requires an active connection to the IFC Pipeline API via an API key credential configured in n8n.
- Uses helper functions to handle binary data extraction and API requests.
- The node expects the input data to contain binary data under the specified binary property name.
Troubleshooting
Error: "No binary data exists on item!"
This occurs if the input item does not have any binary data attached. Ensure that the previous node provides binary data.Error:
No binary data exists on item in property "<propertyName>"!
The specified binary property name does not exist on the input item. Verify the binary property name matches the actual binary data property.API request failures
Check that the API key credential is valid and has sufficient permissions. Also verify network connectivity to the IFC Pipeline service.File type mismatch or unsupported file types
Confirm that the selected file type matches the actual file content being uploaded.
Links and References
- IFC Pipeline official documentation (not provided here, but users should consult their service docs for API details)
- n8n documentation on handling binary data: https://docs.n8n.io/nodes/creating-nodes/binary-data/