Description
n8n-nodes-ifcpipeline
This is an n8n community node that lets you use IfcPipeline in your n8n workflows.
IfcPipeline provides tools for working with Industry Foundation Classes (IFC) files in Building Information Modeling (BIM) workflows, enabling automation of IFC data processing and analysis.
n8n is a fair-code licensed workflow automation platform.
Installation
Operations
Credentials
Compatibility
Usage
Resources
Installation
Requirements
- Self-hosted n8n instance (community nodes are not available on n8n Cloud)
- n8n version 0.214.0 or newer
- IfcPipeline
Bundled installation
This node comes pre-installed with IfcPipeline.
For custom setups, see GUI Installation or Manual isntallation below.
GUI Installation (Recommended)
1. Open your n8n instance
2. Go to Settings > Community Nodes
3. Click Install
4. Enter n8n-nodes-ifcpipeline in the “Enter npm package name” field
5. Click Install
6. Reload your n8n instance when prompted
Manual Installation
If you can’t use the GUI installation method:
1. Navigate to your n8n user data directory:
cd ~/.n8n
2. If it doesn’t exist, create a custom directory:
mkdir -p custom/nodes
3. Install the package:
cd custom/nodes
npm install n8n-nodes-ifcpipeline
4. Start or restart n8n
Operations
This package includes the following nodes:
Credentials
This node requires access to an IfcPipeline API gateway running with
USEOBJECTSTORAGE=true (the S3/MinIO-backed variant of ifcpipeline —
there is no filesystem fallback from 0.7.0 onwards). The credential exposes:
http://api-gateway inside Docker, or https://ifcpipeline.example.com).IFCPIPELINEAPI_KEY.The credential Test hits /health so mis-pointed deployments (e.g. a
legacy filesystem-only gateway) are flagged early.
Usage
After installation, the IfcPipeline nodes will be available in the nodes panel under “IfcPipeline”. You can search for “IFC” to find all related nodes.
Object-storage model
All file references are S3 object keys under the configured bucket.
Legacy leading slashes and s3://bucket/... URIs are tolerated by the
gateway, but the canonical form is a bare key:
| Purpose | Example key |
|————————–|————————————————-|
| Uploaded inputs | uploads/Building-Architecture.ifc |
| ifccsv export | output/csv/Building-Architecture_export.csv |
| ifccsv import (updated IFC) | output/ifcupdated/Building-Architectureupdated.ifc |
| ifctester report | output/ids/validation_report.html |
| ifcdiff report | output/diff/comparison_report.json |
| ifcclash report | output/clash/report.json |
| ifc2json output | output/json/Building-Architecture.json |
| ifcconvert output | output/converted/Building-Architecture.glb |
| ifcpatch output | output/patch/Building-Architecture_patched.ifc|
| ifc5d (QTO) output | output/qto/Building-Architecturewithqtos.ifc|
Typical workflow steps:
1. Upload: the IfcPipeline → Upload File operation streams the file straight into MinIO and returns { storage: "s3", bucket, objectkey, objecturl, filepath, storageref }. storage_ref is the canonical, bucket-relative key downstream worker nodes should consume.
2. Process: wire storageref (or any upstream worker’s result.outputkey) into the next node’s filename / inputfile / inputfilename parameter. No prefixes, no mount paths.
3. Inspect / download: worker jobs return { outputkey, outputpath: "s3://…/…" }. IfcPipeline → Download File produces a token via /createdownloadlink and follows the resulting 307 redirect to a presigned MinIO URL transparently.
The path-picker dropdown in each node queries /listdirectories, which the object-storage gateway backs with a paginated listobjects_v2 over the bucket — so both fresh uploads and worker outputs show up automatically.
Resources
Acknowledgement
This project would not have been possible without the incredible work done by the IfcOpenShell project. Their dedication to creating an open-source IFC parser and toolkit has enabled the development of this node package. We would like to extend our gratitude to the entire IfcOpenShell team for their contributions to the IFC ecosystem.
