Mira File DownloadInstall

Overview

The Mira File Download node allows users to download files stored in a specific library on the Mira App Server. It is designed to fetch files by specifying the library and file IDs, optionally renaming the downloaded file. This node is useful in workflows where automated retrieval of documents or media from the Mira server is required, such as backing up files, processing documents, or integrating with other systems that consume these files.

Practical examples include:

• Automatically downloading reports or invoices stored in a Mira library for further processing.
• Fetching media files from a Mira library to upload them to another platform.
• Archiving files from Mira into cloud storage or local systems.

Properties

Output

The node outputs an array of items, each containing:

• json: Metadata about the downloaded file including:

  • message: Confirmation message ("File downloaded successfully").
  • operation: The operation performed ("file_download").
  • libraryId: The library ID used for the download.
  • fileId: The file ID downloaded.
  • fileName: The final file name used for the binary data.
  • fileSize: Size of the downloaded file in bytes.
  • mimeType: MIME type of the downloaded file.
  • timestamp: ISO timestamp when the file was downloaded.

• binary: Contains the actual file data under the key data. This binary data represents the downloaded file content.

• pairedItem: Links the output item to the corresponding input item index.

Dependencies

• Requires an API key credential to authenticate requests to the Mira App Server.
• The node makes HTTP GET requests to the Mira server's file download endpoint.
• The server URL and access token must be configured in the node credentials.
• No additional external dependencies are needed beyond standard n8n helpers and HTTP request capabilities.

Troubleshooting

• Missing or empty Library ID/File ID: The node throws an error if either the Library ID or File ID is missing or empty. Ensure these fields are correctly set.
• Authentication errors: If the API key or access token is invalid or expired, the HTTP request will fail. Verify the credentials configuration.
• File not found: If the specified file does not exist in the given library, the server may return a 404 error. Confirm the IDs are correct.
• Network issues: Connectivity problems can cause request failures. Check network access to the Mira server.
• File naming issues: If no custom file name is provided, the node attempts to extract the file name from response headers. If these headers are missing or malformed, the node defaults to a generic file name pattern.

Links and References

• Mira App Server API documentation (for file download endpoints) — consult your Mira server API docs.
• n8n HTTP Request node documentation for understanding HTTP options and binary data handling: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/