Actions8
Overview
This node integrates with the MediaCockpit Digital Asset Management (DAM) REST API, specifically enabling users to download assets stored in the MediaCockpit system. It supports downloading either the original asset file or a derivative version such as thumbnails or previews.
Common scenarios where this node is beneficial include:
- Automating retrieval of media files from MediaCockpit for further processing or distribution.
- Fetching preview images or thumbnails for display in other applications or workflows.
- Integrating MediaCockpit assets into content pipelines without manual downloads.
For example, a marketing team could use this node to automatically download the latest approved product images or video previews from MediaCockpit and then upload them to a website or social media platform.
Properties
| Name | Meaning |
|---|---|
| Asset ID | The unique identifier of the asset to download from MediaCockpit. |
| Download Asset | Operation selector; here it only has one option: "Download Asset" which triggers the download. |
| Download Derivative | Boolean flag indicating whether to download a derivative (thumbnail/preview) instead of the original file. |
| Derivative Group | When downloading a derivative, specifies the group/category of the derivative (e.g., "Preview"). |
| Derivative Type | When downloading a derivative, specifies the type/size of the derivative (e.g., "large"). |
Output
The node outputs an array of items, each containing:
json: Metadata about the downloaded asset including debug information such as:- The constructed download URL.
- Asset ID used.
- Whether a derivative was requested.
- HTTP response status and headers.
- Content type of the downloaded data.
- Filename determined for the downloaded file.
- File size and first bytes in hex format.
- Flags indicating if the content is likely JSON.
- Any errors encountered during JSON parsing of metadata responses.
binary.data: The actual binary content of the downloaded asset or derivative file. This binary data can be used downstream in the workflow for saving to disk, uploading elsewhere, or further processing.
Dependencies
- Requires an API key credential to authenticate with the MediaCockpit DAM REST API.
- Needs network access to the MediaCockpit API endpoint.
- Uses n8n's built-in HTTP request helper methods for communication.
- No additional external libraries beyond those bundled with n8n are required.
Troubleshooting
Common issues:
- Invalid or missing Asset ID will cause the download to fail.
- Requesting a derivative group/type that does not exist may result in errors or empty responses.
- Network connectivity problems or incorrect API credentials will prevent successful authentication or download.
- If the API returns JSON metadata instead of file content, the node throws an error indicating possible issues with the asset or permissions.
Error messages:
"Download failed: API returned JSON metadata instead of file content."
Indicates the asset could not be downloaded as a file, possibly due to invalid asset ID or lack of access rights. Verify the asset exists and credentials have proper permissions."No binary data found. Please connect a node that provides binary data..."(from upload operation, not relevant here but present in code)
Means the node expected binary input but none was provided.- HTTP errors or timeouts will be surfaced as node operation errors with details.
To resolve errors, verify:
- Correct Asset ID is provided.
- API credentials are valid and have necessary permissions.
- Network connectivity to the MediaCockpit API endpoint.
- Derivative parameters match available options in MediaCockpit.
Links and References
- MediaCockpit DAM official documentation
- n8n HTTP Request Helper Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/
- General info on digital asset management systems: https://en.wikipedia.org/wiki/Digital_asset_management