Actions13
Overview
The "Create Asset" operation in the Crownpeak DQM node allows users to submit new content assets to the Crownpeak DQM CMS via its API. This is useful for automating the process of adding web page content or other digital assets into the Crownpeak system, enabling continuous integration and deployment workflows for website content management.
Typical use cases include:
- Automatically creating new web pages or content snippets from external sources.
- Integrating content creation into broader automation pipelines.
- Submitting HTML or other content types programmatically to be managed and quality-checked by Crownpeak.
For example, a user might send an HTML string representing a new webpage's content along with its content type to create a new asset in a specified website within Crownpeak.
Properties
| Name | Meaning |
|---|---|
| Page Content | The actual content of the asset to be created, typically HTML or text to be submitted. |
| Content Type | The MIME type of the content being submitted. Default is text/html; charset=UTF-8. |
Output
The output is a JSON array where each element corresponds to the response from the Crownpeak API for the asset creation request. The structure depends on the API response but generally includes details about the newly created asset such as its identifier, status, and metadata.
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 the base URL of the Crownpeak API endpoint configured in the credentials.
- The node uses HTTP requests with appropriate headers and URL parameters to interact with the Crownpeak API.
Troubleshooting
Common issues:
- Missing or invalid API key will cause authentication failures.
- Incorrect website ID or malformed content may result in API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
"Unsupported operation"error indicates that the selected operation is not implemented or misspelled.- HTTP errors returned from the API (e.g., 400 Bad Request, 401 Unauthorized) should be checked for correct input parameters and valid credentials.
Resolutions:
- Verify API key and ensure it has necessary permissions.
- Confirm that the website ID is correct and exists in Crownpeak.
- Validate the content format and content type before submission.
- Check network access and proxy settings if applicable.
Links and References
- Crownpeak DQM API Documentation (refer to official Crownpeak developer resources)
- n8n HTTP Request Node documentation for understanding underlying request mechanics