MediaCockpit DAM icon

MediaCockpit DAM

Interact with MediaCockpit DAM REST API
Join our community

Actions8

Overview

The node "MediaCockpit DAM" enables interaction with the MediaCockpit Digital Asset Management (DAM) REST API. Specifically, for the Get Asset by ID operation, it retrieves detailed information about a single digital asset using its unique identifier. This is useful in workflows where you need to fetch metadata or details of a specific asset stored in the MediaCockpit DAM system.

Common scenarios include:

  • Retrieving asset metadata for display or processing.
  • Integrating asset data into other systems or reports.
  • Validating asset existence before further operations like download or update.

Example: You have an asset ID from a previous step and want to get all associated metadata to decide if the asset should be downloaded or updated.

Properties

Name Meaning
Asset ID The unique identifier of the asset to retrieve from MediaCockpit DAM.
Build JSON Optional custom JSON configuration to control the output format of the asset data. Leave as {} to use the default output format.

Output

The node outputs a JSON object containing the asset's metadata retrieved from the MediaCockpit DAM API. The exact structure depends on the API response and optionally on the Build JSON configuration if provided.

  • The json field contains the asset details such as identifiers, attributes, and metadata fields.
  • No binary data is output for this operation; it strictly returns JSON metadata.

Dependencies

  • Requires an API key credential configured in n8n to authenticate against the MediaCockpit DAM REST API.
  • The node uses HTTP requests to communicate with the MediaCockpit API endpoint.
  • Network access to the MediaCockpit API server must be available.

Troubleshooting

  • Invalid Asset ID: If the asset ID does not exist or is incorrect, the API may return an error or empty result. Verify the asset ID is correct.
  • Authentication Errors: Ensure the API key credential is valid and has permissions to access the asset.
  • API Endpoint Issues: Network problems or incorrect API URL configuration can cause request failures.
  • Malformed Build JSON: If providing a custom JSON build configuration, ensure it is valid JSON; otherwise, the output may fail or be unexpected.

Common error messages:

  • "Unknown operation: getById": Indicates the operation parameter was not recognized; ensure the operation name is exactly "getById".
  • HTTP errors with status codes like 401 or 403 indicate authentication or permission issues.
  • JSON parse errors in debug fields suggest malformed responses or misconfiguration.

Links and References

Discussion