Overview
The node "IfcPipeline File Operations" provides various file-related functionalities within the IFC Pipeline environment. Specifically, the Download From URL operation allows users to download a file from any given URL directly into the IFC Pipeline system.
This operation is useful when you want to import external files into your IFC Pipeline workspace without manually downloading and uploading them. For example, you might use it to fetch a BIM model or related data file hosted on a public server or cloud storage, streamlining workflows that involve integrating external resources.
Properties
| Name | Meaning |
|---|---|
| URL | The web address of the file you want to download. This must be a valid URL pointing to the file. |
| Filename | (Optional) A custom filename to assign to the downloaded file. If left empty, the original filename from the URL will be used. |
Output
The output of this operation is a JSON object containing metadata about the downloaded file as returned by the IFC Pipeline API. This typically includes information such as the file's identifier, status, or confirmation of successful download.
No binary data is directly output by this operation; instead, it returns structured JSON data representing the result of the download request.
Dependencies
- Requires an active connection to the IFC Pipeline API, authenticated via an API key credential configured in n8n.
- The node depends on internal helper functions to make HTTP requests to the IFC Pipeline service endpoints.
- Network access to the specified URL must be available from the n8n instance for the download to succeed.
Troubleshooting
- Invalid URL or inaccessible resource: If the URL is incorrect or the file is not publicly accessible, the node will fail to download the file. Verify the URL and ensure proper permissions.
- API authentication errors: Ensure that the API key credential for IFC Pipeline is correctly set up and has sufficient permissions.
- Empty or missing filename: If no filename is provided and the URL does not contain a valid filename, the node may assign a default name or fail. Providing a custom filename can prevent this issue.
- Network issues: Firewall or proxy settings might block access to the URL or IFC Pipeline API endpoints. Confirm network connectivity.
Common error messages will include descriptive text from the IFC Pipeline API or HTTP client errors indicating the nature of the failure.
Links and References
- IFC Pipeline official documentation (for API details and file operations)
- n8n documentation on creating and using credentials
- General HTTP file download best practices