Actions13
Overview
This node integrates with the Crownpeak DQM CMS API to retrieve asset errors filtered by a specific checkpoint. It is useful for quality assurance and content validation workflows where you need to identify issues or errors associated with a particular content asset at a given checkpoint in the content lifecycle.
Typical use cases include:
- Automatically fetching error reports for a content asset after a quality checkpoint has been run.
- Integrating error data into broader content management or reporting pipelines.
- Triggering notifications or remediation steps based on detected asset errors at checkpoints.
For example, after publishing a webpage asset, you might want to get all errors found during a specific checkpoint scan to ensure content quality before going live.
Properties
| Name | Meaning |
|---|---|
| Asset Identifier (assetId) | The unique identifier of the content asset for which to fetch errors. |
| Checkpoint ID (checkpointId) | The identifier of the checkpoint at which to retrieve the asset's errors. |
Output
The node outputs a JSON array where each element represents an error related to the specified asset at the given checkpoint. The exact structure depends on the Crownpeak DQM API response but typically includes details such as error type, description, location within the asset, severity, and possibly remediation suggestions.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Crownpeak DQM CMS API.
- Needs the base URL and website ID configured in the credentials or node parameters.
- The node makes HTTP requests to the Crownpeak DQM API endpoints.
Troubleshooting
Common Issues:
- Missing or invalid API key will cause authentication failures.
- Incorrect asset or checkpoint IDs will result in "not found" or empty responses.
- Network connectivity problems can cause request timeouts or errors.
Error Messages:
Unsupported operation: Indicates that the selected operation is not implemented; ensure "Get Asset Errors by Checkpoint" is chosen.- HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually mean incorrect credentials or invalid parameters.
Resolutions:
- Verify API key validity and permissions.
- Double-check asset and checkpoint identifiers.
- Ensure the website ID matches the asset's website context.
- Confirm network access to the Crownpeak DQM API endpoint.
Links and References
- Crownpeak DQM API Documentation (refer to official Crownpeak resources for detailed API specs)
- n8n Documentation on HTTP Request Node (for understanding underlying HTTP calls)