MediaCockpit PIM icon

MediaCockpit PIM

Interact with MediaCockpit PIM REST API

Overview

This node integrates with the MediaCockpit PIM REST API to manage nodes within a Product Information Management system. Specifically, for the "Update Node Attribute" operation, it allows users to update a single attribute of an existing node by specifying the node ID and the attribute key-value pair or providing full metadata.

Common scenarios include:

  • Updating descriptive information or external keys of product nodes.
  • Correcting or enriching metadata attributes on existing nodes.
  • Automating attribute updates in bulk workflows where node data changes frequently.

Practical example:

  • A user wants to update the "externalKey" attribute of a product node identified by its node ID to synchronize with an external system's identifier.

Properties

Name Meaning
Node ID The unique identifier of the node to update.
Attribute Key The specific attribute key to update (e.g., externalKey, internalDescription, or database ID).
Text Value The new text value to assign to the specified attribute key.
Metadata An advanced option allowing the user to provide a full JSON metadata object to update the node’s attributes, overriding the simple text value.

Output

The node outputs an array of JSON objects representing the results of the operations performed. For the "Update Node Attribute" operation, each output item typically contains:

  • Confirmation of success.
  • Details of the updated attribute(s).
  • The response from the MediaCockpit PIM API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the MediaCockpit PIM REST API.
  • The node uses the base URL configured via credentials to construct API requests.
  • Network access to the MediaCockpit PIM API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Node ID will cause the update to fail.
    • Incorrect attribute keys may result in no changes or API errors.
    • Providing malformed JSON in the Metadata field can cause request failures.
    • Network or authentication errors if the API key is invalid or expired.
  • Error messages:

    • "Create node failed: <message>" indicates failure during node creation but similar error handling applies to update operations.
    • Errors thrown by the API are wrapped as node operation errors with context about the item index.
  • Resolutions:

    • Verify that the Node ID exists and is correct.
    • Ensure attribute keys match those supported by the MediaCockpit PIM system.
    • Validate JSON syntax when using the Metadata property.
    • Confirm API credentials are valid and have sufficient permissions.

Links and References

Discussion