IfcPipeline File Operations icon

IfcPipeline File Operations

Work with files in IFC Pipeline

Actions5

Overview

This node enables interaction with the IFC Pipeline service to perform various file-related operations. Specifically, for the Download File operation, it allows users to download a file stored in the IFC Pipeline by specifying its path. The downloaded file's data is then attached to the workflow item as binary data under a user-defined property.

Common scenarios where this node is beneficial include:

  • Automating retrieval of files from IFC Pipeline for further processing or analysis within an n8n workflow.
  • Integrating IFC Pipeline file downloads into larger automation pipelines, such as triggering downstream tasks once a file is retrieved.
  • Archiving or backing up files from IFC Pipeline by downloading them automatically.

Practical example:

  • A user wants to download a specific IFC model file from IFC Pipeline and then convert or analyze it using other nodes in the workflow. They specify the file path and the binary property name to store the file content, enabling seamless access to the file data downstream.

Properties

Name Meaning
File Path The full path of the file in IFC Pipeline that you want to download.
Binary Property The name of the binary property on the output item where the downloaded file data will be stored. Default is "data".

Output

The node outputs the downloaded file as binary data attached to each item under the specified binary property name. The binary data includes:

  • The file content itself.
  • Metadata such as filename and MIME type, which is inferred based on the file extension:
    • .ifc → application/x-step
    • .ids → application/xml
    • .csv → text/csv
    • .json → application/json
    • Other extensions default to application/octet-stream

The JSON part of the output contains metadata about the operation result, but the main payload is the binary file data ready for use in subsequent nodes.

Dependencies

  • Requires an API key credential for authenticating with the IFC Pipeline service.
  • Uses internal helper functions to make HTTP requests to IFC Pipeline endpoints.
  • No additional external dependencies beyond the IFC Pipeline API and n8n core helpers.

Troubleshooting

  • No binary data exists on item!
    This error occurs if the input item does not contain any binary data when expected (not typical for download operation but relevant for upload). For download, ensure the file path is correct and accessible.

  • No binary data exists on item in property "X"!
    If the specified binary property name does not exist or is misspelled, the node cannot write the downloaded file data. Verify the binary property name matches exactly.

  • File not found or invalid file path
    If the file path provided does not exist in IFC Pipeline, the API will likely return an error. Double-check the path string for correctness.

  • Authentication errors
    Ensure the API key credential is correctly configured and has sufficient permissions to access the requested file.

  • MIME type detection issues
    If the file extension is uncommon, the node defaults to application/octet-stream. This usually does not cause failures but may affect how downstream nodes interpret the file.

Links and References

Discussion