Actions13
Overview
The node integrates with the Crownpeak DQM CMS API to manage and interact with digital content assets and related website data. Specifically, the Update Asset operation allows users to update the content of an existing asset within a specified website.
This node is beneficial in scenarios where automated content management workflows are needed, such as:
- Automatically updating web page content based on external data or editorial changes.
- Integrating content updates into CI/CD pipelines for websites managed via Crownpeak DQM.
- Synchronizing content changes from other systems into Crownpeak DQM without manual intervention.
For example, a marketing team could use this node to programmatically update product descriptions or promotional pages whenever new information becomes available, ensuring the website always reflects the latest content.
Properties
| Name | Meaning |
|---|---|
| Asset Identifier | The unique ID of the asset to update. |
| Page Content | The new content (e.g., HTML or text) to set for the specified asset. |
Output
The node outputs a JSON array containing the response from the Crownpeak DQM API for each input item processed. For the Update Asset operation, the output JSON typically includes confirmation details about the updated asset, such as status or metadata returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Crownpeak DQM CMS API.
- Needs configuration of the base URL and website ID within the credentials or node parameters.
- Uses HTTP methods (PUT for update) to communicate with the Crownpeak DQM REST endpoints.
Troubleshooting
Common issues:
- Invalid or missing Asset Identifier will cause the API request to fail.
- Incorrect or expired API key will result in authentication errors.
- Providing empty or malformed content may lead to unsuccessful updates or API errors.
- Network connectivity problems can prevent successful communication with the Crownpeak API.
Error messages:
"Unsupported operation": Indicates an invalid operation parameter; ensure "updateAsset" is selected.- HTTP 401 Unauthorized: Check that the API key credential is valid and has necessary permissions.
- HTTP 404 Not Found: Verify the asset ID exists and belongs to the configured website.
- HTTP 400 Bad Request: Confirm that the content format and parameters meet API requirements.
Resolving these usually involves verifying input parameters, credentials, and network access.
Links and References
- Crownpeak DQM API Documentation (example placeholder link)
- n8n HTTP Request Node Documentation
- Working with Credentials in n8n