Crownpeak DQM icon

Crownpeak DQM

Interact with Crownpeak DQM CMS API

Overview

The node integrates with the Crownpeak DQM CMS API to perform various operations related to website content quality management. Specifically, the Get Website Checkpoints operation retrieves all checkpoints associated with a specified website. Checkpoints represent quality or compliance checks configured for that website, useful for monitoring and improving content standards.

This node is beneficial in scenarios where users want to automate the retrieval of website quality checkpoints for reporting, auditing, or triggering further workflows based on checkpoint data. For example, a user might fetch checkpoints to analyze which quality rules are applied to a website or to prepare a dashboard showing current checkpoint statuses.

Properties

Name Meaning
Website ID The unique identifier of the website for which to retrieve details or checkpoints.

Output

The output is a JSON array containing the data returned by the Crownpeak DQM API for the requested website checkpoints. Each item in the array represents a checkpoint object with its properties as defined by the API response. This typically includes checkpoint identifiers, names, descriptions, and configuration details relevant to the website's quality checks.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Crownpeak DQM CMS API.
  • The node uses HTTP requests to communicate with the Crownpeak DQM API endpoint.
  • Proper configuration of the API base URL and valid credentials must be set up in n8n.

Troubleshooting

  • Common issues:

    • Invalid or missing Website ID will cause the API request to fail or return no data.
    • Incorrect or expired API key will result in authentication errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Unsupported operation: Indicates the selected operation is not implemented; ensure "Get Website Checkpoints" is chosen.
    • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) usually indicate credential or parameter issues. Verify the API key and Website ID.
  • Resolution tips:

    • Double-check the Website ID input for correctness.
    • Confirm the API key credential is valid and has necessary permissions.
    • Test API connectivity outside n8n to isolate network issues.

Links and References

Discussion