Bidirectional Content Hub Integration

The bidirectional integration between OrderCloud and Content Hub aims to streamline the process of managing your product data, from content to commerce.

OrderCloud to Content Hub

There are two main cases in which this integration will prove useful. If you have existing product data from another system that you would like to programmatically import into OrderCloud or, you have an existing marketplace with product data in OrderCloud and you would like to begin using Content Hub to manage your product content. It is ideal to leave OrderCloud in charge of commerce and product visibility concerns, while Content Hub manages all of the content and images for a product. Ensure you have the integration configured before you run any import or EntitySync of your product data.

If you have existing product data in OrderCloud, you can make use of EntitySync to export your product data and sync it to Content Hub.

The integration between OrderCloud and Content Hub creates a product shell in Content Hub in your specified schema any time a product is created in OrderCloud. The intent of this integration is to allow seamless editing of product content if you create products in OrderCloud. No additional product changes/updates in OrderCloud will be synced to Content Hub, the integration is only meant to create a record in Content Hub for you.

To enable the integration, create a new DeliveryConfiguration in OrderCloud. You will need your Content Hub API Key that you create in the steps below.

1{
2  "ID": "contenthub",
3  "Name": "ContentHub",
4  "Enabled": true,
5  "DeliveryTargets": {
6    "ContentHub": {
7      "ApiKey": "{Your Content Hub API Key}",
8      "Endpoint": "{The Base URL of your Content Hub instance}",
9      "TargetSchemaName": "{Schema name that products should be created to. e.g. M.PCM.Product}",
10      // OPTIONAL. Default behavior syncs ID, Name, and Description properties to fields of the 
11      // same name in Content Hub. If left null, ensure your Content Hub target schema contains 
12      // properties with the aforementioned names.
13      "ConfigData": {
14        "Mapper": {
15          "ID": {
16            "Property": "{The name of your Content Hub unique ID field}",
17            "DefaultCulture": null // ID should not be multi-language.
18          },
19          "Name": {
20            "Property": "{The name of your Content Hub Name field}",
21            // OPTIONAL. If non-null, set to the name of the DefaultCulture string you wish to sync to 
22            // in Content Hub. If null, it is assumed the field is not multi-language.
23            "DefaultCulture": null
24          },
25          "Description": {
26            "Property": "{The name of your Content Hub Description field}",
27            "DefaultCulture": null
28          }
29        }
30      }
31    }
32  }
33}

Then create a ProductSynchronization record in OrderCloud. Note that the request body field “SyncProductChanged” accounts for both changes and creations. In the case of this integration, we are only syncing products on create.

1{
2  "SyncProductChanged": true,
3  "DeliveryConfigID": "{the ID of your DeliveryConfiguration}" // e.g. contenthub
4}

Now that the configuration is complete, if you create a new product in OrderCloud filling out values for ID, Name and Description, you should see a new entity created in Content Hub - ready for you to seamlessly manage content!

Content Hub to OrderCloud

Configuring the necessary Action and Trigger combination in Content Hub enables the creation of a Product record in OrderCloud any time an entity of a specified schema in Content Hub is created or modified. This integration tracks changes to three properties you define as a unique ID, Name and Description on your Content Hub model. These properties mapped to OrderCloud’s Product.ID, Product.Name, and Product.Description will be kept up to date with the values in Content Hub. The integration will also give you the option of syncing flat properties to OrderCloud’s Product.xp (non multi-language/taxonomy fields), and will also sync Content Hub asset Public Links to OrderCloud’s Product.xp.Images as an array of objects containing URLs for the Original, Thumbnail and Preview - depending on the configuration of the assets' public links. This allows for seamless administration of commerce capabilities for the product entities you are already managing in Content Hub.

Your adoption strategy will look slightly different depending on if you are a new or existing Content Hub user. If you are an existing Content Hub user, you need to identify properties you would like to sync to OrderCloud's Product.ID, Product.Name and Product.Description properties. The field you sync to Product.ID needs to be a unique field.

Configure Content Hub to OrderCloud Integration

As an existing Content Hub user, it is likely that you already have your tenant configured in a way that works for your business. With this in mind, we can configure your existing data model to work for the integration, enabling seamless adoption.

OrderCloud Configuration

• Configure an API Client for the integration

  • Name it anything you like, something descriptive like “Content Hub Integration”

  • Add a ClientSecret

  • Select “AllowAllSellers”

  • Configure the default context user. Make sure this user is assigned a security profile that has ProductAdmin at minimum.

  • Take note of the ClientID and ClientSecret, as you will need these for creating a Content Hub Action.

  • Take note of the BaseURL for your specific region/environment, as you will need this for creating a Content Hub Action.

Content Hub Configuration

• Identify your target Schema

  • Which of your existing schemas represents your products? Identify which of your schemas represents the entities you would like to be synced to OrderCloud in order to manage commerce functionality, bridging the gap between content and commerce.

  • When choosing your schema, make note of a field that you have designated as unique, you will need a unique field to sync to OrderCloud’s ID property. If you do not have a unique string field in your schema, you can follow the steps below to add one.

If your schema does not have a unique field, use the following steps to add one.

• Navigate the settings page for that schema

• Add a new string property member to the schema called ID. This name is just a suggestion, feel free to name it whatever makes sense for you, and make note of the name. Mark the property as unique and click save.

Create an API key for the integration

• Click on Users from the settings page

• Either create a new user to be used for the integration as an “API User”, or create a new user

• Click the key icon for API Token

• Click New token

• Save this token, it will never be shown to you in the UI again - so make note of it, you will need it in future steps

Ensure your API User has the correct permissions to be able to view and edit entities.

Configure a new Action

• You can name this anything you want, make it descriptive something like “OrderCloud Sync”.

• Select “API Call” in the type dropdown

• The POST Method should be automatically selected, if it is not, select “POST” as the method.

• The API URL is dependent on the region of your OrderCloud environment. Find the URL for your respective region and copy it exactly.

• Leave the timeout at 30s. We do not need any headers.

• For Values, use the following table to enter your values. Make sure you copy the keys exactly. Copy and pasting from this document will help prevent typos.

Configure a new Trigger

• You can name this trigger anything you want, make it descriptive something like “OrderCloud Sync” which matches our Action. For objective, check all 3 boxes for creation, modification and deletion. For execution type, click “In background”.

• Configure a trigger for your chosen schema, add any properties that you would like to trigger an event off of.

Image Syncing

• If there is an image property, include this as well. Our example schema has an image property Asset which is represented by the relationship PCMProductToAsset. Make note of this relationship name, as it will come into play later on.

• Next, configure two more trigger conditions for M.Asset and M.PublicLink following the screenshot for which properties to configure.

• Select the Action for the trigger we just configured

  • Now that we have configured the trigger, switch to the “Actions” tab and select the Action that we configured in the previous step.

• Save the trigger.

With that, the integration should be fully configured. Test it out by creating an Entity of your specified type, then attempt to “GET” the product in OrderCloud and if the product exists, you can celebrate that you now have a functioning bidirectional integration between OrderCloud and Content Hub.

Still have questions?
Ask in our Community Channel

Content Powered By