Actions13
Overview
The node integrates with the Crownpeak DQM CMS API to perform various operations related to website content assets and quality management. Specifically, the "Get Spellcheck Issues" operation fetches spellcheck issues for a specified content asset within a website. This is useful for content editors and quality assurance teams who want to automatically identify spelling errors in web content managed by Crownpeak DQM.
Practical examples include:
- Automatically retrieving spellcheck issues for a webpage asset before publishing.
- Integrating spellcheck issue data into a content review workflow.
- Monitoring content quality over time by regularly fetching spellcheck reports.
Properties
| Name | Meaning |
|---|---|
| Asset Identifier | The unique identifier of the content asset for which to retrieve spellcheck issues. |
Output
The node outputs a JSON array where each element corresponds to the response from the Crownpeak DQM API for the requested operation. For the "Get Spellcheck Issues" operation, the JSON output contains details about spelling errors found in the specified asset. This typically includes information such as the misspelled words, their locations, suggested corrections, and possibly severity or context.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Crownpeak DQM CMS API.
- Needs configuration of the base URL for the Crownpeak DQM API endpoint.
- The node uses HTTP requests to communicate with the external Crownpeak DQM service.
Troubleshooting
Common issues:
- Invalid or missing API key will cause authentication failures.
- Incorrect or non-existent Asset Identifier may result in "not found" errors.
- Network connectivity problems can prevent successful API calls.
- Using an unsupported operation value will throw an error.
Error messages:
"Unsupported operation: getSpellcheckIssues"— indicates a mismatch between selected operation and implemented logic; ensure the operation name is correct.- HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) should be checked against credentials and asset IDs.
Resolutions:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Confirm the asset ID exists and belongs to the configured website.
- Check network access and proxy settings if applicable.
- Use valid operation names as defined in the node's properties.
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