Overview
This node interacts with a File Management Service (FMS) API to perform file-related operations. Specifically, the Download operation under the File resource allows users to download files stored in the FMS by specifying an object key and providing user authentication details.
Common scenarios for this node include:
- Automating retrieval of files from a remote file storage system.
- Integrating file downloads into workflows that process or analyze file contents.
- Securely accessing files using user credentials and client authentication.
For example, a user can provide the unique key of a file stored in the FMS along with their authentication tokens to download the file content as part of an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Object Key | The unique key identifying the file object to download from the FMS. |
| User Name | The name of the user requesting the file download; used for authentication. |
| User Token | The token associated with the user for authenticating the download request (password type). |
| Client ID | The client identifier used for API authentication. |
| Client Secret | The client secret key used to generate HMAC signatures for secure API requests (password type). |
Output
The node outputs a JSON object containing:
statusCode: The HTTP status code returned by the FMS API for the download request.body: The body of the response, which contains the downloaded file data or related information.
If the file is successfully downloaded, the body will contain the file content or metadata as returned by the FMS API. The node does not explicitly handle binary data output in this implementation; the file content is included in the JSON response body.
Dependencies
- Requires access to the FMS API endpoint for downloading files (
https://your-fms-endpoint/download). - Needs valid user credentials: user name, user token, client ID, and client secret.
- Uses HMAC SHA256 hashing to sign requests for authentication.
- Requires n8n's HTTP Request helper to make API calls.
Troubleshooting
- Authentication errors: If the user name, user token, client ID, or client secret are incorrect or expired, the API will reject the request. Verify all credentials and regenerate tokens if necessary.
- Invalid Object Key: Providing a wrong or non-existent object key will result in a failed download or empty response. Confirm the object key is correct.
- Network issues: Ensure the FMS API endpoint is reachable from the n8n instance.
- Error messages: If the node throws an error, it will include the message from the caught exception. Enabling "Continue On Fail" allows the workflow to proceed despite errors, returning error details in the output JSON.
Links and References
- HMAC SHA256 Documentation
- HTTP Authentication Schemes
- (No direct public link to the FMS API was provided in the source code.)