IfcPipeline File Operations

Overview

The node provides integration with the IFC Pipeline service to perform various file-related operations. Specifically, for the List Directories operation, it retrieves and lists available directories and files from the IFC Pipeline storage.

This node is useful in automation workflows where you need to programmatically explore or manage files stored in IFC Pipeline, such as:

• Automatically fetching directory listings before processing or downloading files.
• Integrating IFC Pipeline file structures into broader data pipelines.
• Monitoring or auditing files and folders within IFC Pipeline.

Example: A user can list all directories and files in their IFC Pipeline account to dynamically decide which files to download or process next.

Properties

Note: For the List Directories operation, only the "Additional Fields" collection property is available, but it has no options configured.

Output

The output of the List Directories operation is a JSON array representing the directories and files retrieved from IFC Pipeline.

• Each item in the output corresponds to an entry (directory or file) returned by the API endpoint /list_directories.
• The structure of each JSON object matches the raw response from the IFC Pipeline API.
• The output does not include binary data for this operation.

Dependencies

• Requires an active connection to IFC Pipeline via an API key credential.
• Uses internal helper functions to make authenticated HTTP requests to IFC Pipeline endpoints.
• No external environment variables are explicitly required beyond the API credential configuration.

Troubleshooting

• No directories listed / empty output:
  Ensure that the API credentials are valid and have permission to access the directories. Also verify that there are directories/files present in the IFC Pipeline account.

• Authentication errors:
  Check that the API key credential is correctly set up in n8n and has not expired or been revoked.

• API request failures:
  Network issues or incorrect API endpoint configurations could cause failures. Review error messages for HTTP status codes and retry if transient.

• Unhandled exceptions:
  If the node throws unexpected errors, enabling "Continue On Fail" will allow the workflow to proceed while capturing error details in the output.

Links and References

• IFC Pipeline official documentation (for API details and authentication): [Not provided in source]
• n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
• General info on handling file operations in automation workflows.