Actions13
Overview
The "Get Checkpoint Details" operation in the Crownpeak DQM node retrieves detailed information about a specific checkpoint within the Crownpeak Digital Quality Management (DQM) CMS system. This node is useful for users who want to inspect or audit the status, metadata, or configuration of a particular checkpoint used in website quality assurance workflows.
Typical scenarios include:
- Fetching checkpoint details to verify its configuration or status before running audits.
- Integrating checkpoint data into automated reporting or monitoring systems.
- Using checkpoint metadata to correlate with asset quality checks or error reports.
For example, a user might input a checkpoint ID to get its name, creation date, or other relevant attributes to understand what quality checks are applied at that checkpoint.
Properties
| Name | Meaning |
|---|---|
| Checkpoint ID | The unique identifier of the checkpoint whose details you want to retrieve. |
Output
The output is a JSON array where each element corresponds to the response from the API call fetching checkpoint details. The structure typically includes various properties describing the checkpoint such as its ID, name, description, creation date, and possibly other metadata related to the checkpoint's configuration in the Crownpeak DQM system.
No binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Crownpeak DQM CMS API.
- Needs the base URL and website ID configured in the credentials or node parameters.
- The node makes HTTP GET requests to the Crownpeak DQM API endpoints.
Troubleshooting
- Common issues:
- Invalid or missing checkpoint ID will result in errors or empty responses.
- Incorrect or expired API key will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
- Error messages:
- "Unsupported operation" if the operation parameter is set incorrectly.
- HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or resource issues.
- Resolutions:
- Verify the checkpoint ID is correct and exists in the Crownpeak system.
- Ensure the API key credential is valid and has necessary permissions.
- Check network access and endpoint URLs.
Links and References
- Crownpeak DQM official API documentation (refer to your organization's API docs for exact URLs).
- n8n documentation on creating and using custom nodes and credentials.