Actions13
Overview
The "List Assets" operation of the Crownpeak DQM node interacts with the Crownpeak DQM CMS API to retrieve a list of content assets associated with a specified website. This operation is useful for scenarios where you need to fetch and process multiple content assets, such as auditing website content, generating reports, or integrating asset data into other workflows.
For example, a user might want to list all assets on a website to check their quality status or to update them in bulk based on certain criteria.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return (minimum 1) |
Output
The output is a JSON array where each element represents an asset retrieved from the Crownpeak DQM CMS API. Each asset object contains details as provided by the API, typically including identifiers, metadata, and other asset-specific information.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Crownpeak DQM CMS API.
- The node uses the base URL configured in the credentials to form API requests.
- Proper configuration of the website ID in the credentials or input parameters is necessary to scope the asset listing.
Troubleshooting
- Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect or missing website ID may result in empty responses or errors.
- Exceeding API rate limits could lead to request failures.
- Error messages:
- "Unsupported operation" error if the operation parameter is set incorrectly.
- HTTP errors returned from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or parameter issues.
- Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Ensure the website ID is valid and corresponds to an existing website in Crownpeak DQM.
- Adjust the "Limit" property to a reasonable number to avoid overwhelming the API.
Links and References
- Crownpeak DQM API Documentation (refer to official Crownpeak resources for detailed API specs)
- n8n Documentation on creating and using custom nodes and credentials