Overview

This node operation uploads a file to the IFC Pipeline service. It is useful for automating the process of sending files of various types (IFC, IDS, CSV, or other) to the IFC Pipeline platform for further processing or storage. For example, users can upload architectural model files (IFC) or data files (CSV) directly from their workflow to the IFC Pipeline without manual intervention.

Use Case Examples

1. Uploading an IFC file from a binary data property named 'data' to the IFC Pipeline for model processing.
2. Uploading a CSV file from a custom binary property to the IFC Pipeline for data analysis.

Properties

Output

JSON

• storage_ref - Reference to the stored file in IFC Pipeline returned after upload.
• fileName - Name of the uploaded file, if available.
• mimeType - MIME type of the uploaded file, if available.

Dependencies

• Requires an API key credential for IFC Pipeline API authentication.

Troubleshooting

• Error 'No binary data exists on item!' indicates the input item lacks any binary data; ensure the input contains binary data.
  Error 'No binary data exists on item in property ""!' means the specified binary property does not exist on the input item; verify the binary property name is correct and matches the input data.
• Upload failures may occur if the API key credential is invalid or lacks permissions; verify the credential configuration.