Integration architecture

Sitecore Content Hub provides flexible integration methods with external systems and for cloud development pipelines in general. This section explains the different building blocks of Sitecore Content Hub.

Global architecture

Sitecore Content Hub offers different layers for integration, as shown in the following diagram.

Content Hub architecture

The different integration components can work independently or in combination with other integration components based on the required use cases.


With Experience Edge for Content Hub, Content Hub becomes a Content as a Service (CaaS) solution.



Experience Edge for Content Hub

Sitecore Experience Edge for Content Hub is the solution for brands and organizations that manage content for multiple functions and audiences using numerous devices.

Experience Edge is a set of services for headless content delivery, and is based on the Content as a Service (CaaS) model that focuses on managing content into feeds. These feeds mean that other applications and properties can consume and use the content according to their particular needs.


The various connectors allow the integration of Sitecore Content Hub with different major product collections.



Sitecore Connect for Content Hub

Sitecore Connect for Content Hub allows users to browse, search and insert digital assets from Sitecore Content Hub directly within Sitecore Content and Experience editing tools.

Sitecore Connect for Creative Cloud

Sitecore Connect for Creative Cloud is a powerful extension that connects Sitecore Content Hub with Adobe Creative Cloud tools and enables direct linking to stored assets.

Sitecore Connect for Salesforce

Sitecore Connect for Salesforce allows users to to include assets from Sitecore Content Hub in Salesforce Marketing Cloud Email App.

Sitecore Connect for Microsoft D365 Commerce - Content Hub

Enables you to unify your commerce content synchronizing product data in Microsoft D365 Commerce and Content Hub. You can also use Dynamics 365 Commerce visual page builder to reference enriched product details and product assets such as images, videos, files, and markup from Content Hub.

Tools for integration

The following tools allow users to integrate Sitecore Content Hub with external systems.




Triggers are a push mechanism in Sitecore Content Hub that executes certain actions if certain conditions are met after specific events occur. Triggers are defined by a set of triggering events (Objectives), a set of conditions, and a set of actions.

Triggers can be used as a push mechanism towards external systems by making API calls (e.g. invoke an Azure Function) or by publishing messages to an Azure Service Bus queue or an Azure Event Hub.


Actions are extensible objects that can be included in other page components (e.g. selection component) and that can execute a specific task like running a predefined script, making an external API call and publishing messages to an Azure Service Bus queue or an Azure Event Hub.


Sitecore Content Hub allows users to integrate custom scripts in their business logic. Scripts can be manually triggered by end-users or automatically triggered by the application (e.g. using Triggers) depending on the script type and the use case. Sitecore Content Hub offers different script types, with each type having different context properties.


A command-line interface (CLI) processes commands to a computer program in the form of lines of text. The program which handles the interface is called a command-line interpreter or command-line processor. The CLI is used for communicating with Sitecore Content Hub™ instances through the REST API using the C# Web SDK.


Sitecore Content Hub offers an import/export package feature that allows users to migrate their structural changes between different instances of Sitecore Content Hub.

External components

External page components are extensible components that can be integrated into portal pages. They allow the integration of external libraries within Sitecore Content Hub pages.

External components contain a code section that gets executed when the component is initialized, as well as a template section that contains an HTML markup that gets injected in the DOM when the component is initialized.

C# Web SDK

The C# Web SDK is an external tool that makes it easier for C# developers to implement their own logic in manipulating the object resources.

JavaScript SDK

The JavaScript SDK is an external tool that makes it easier for JavaScript developers to implement their own logic in manipulating the object resources.


The REST API of Sitecore Content Hub is a Hypermedia API built on top of HTTP where all objects are modeled as resources. Each resource represents the state of the object at the time of the request. Standard HTTP requests and responses are used to query and manipulate the state of the objects.

Triggers, actions, and scripts

Triggers, Actions and Scripts are frequently used together in the following logic:

  1. Scripts are configured to execute business logic (e.g. API calls, data validation, data modification)

  2. Actions of type Action script are configured to run the scripts when called.

  3. Triggers are configured to call the script actions when an event occurs and the conditions are met.


For more information about the different modules available in Sitecore Content Hub, see Modules and licenses.


For details on when to use Scripts and when to use the Microsoft Azure functionality, see How to choose the integration tool.

Do you have some feedback for us?

If you have suggestions for improving this article,