Platform

Content Management

Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers.

Enterprise Data Engine

Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle.

Automate

Automate your content creation and approval flows while taking advantage of AI services to enhance and curate content.

Publish On Time

Source and deliver high impact, quality content to your customers on schedule with automated assistants and scalable worldwide deployment.

Train AI Models

Continuously train your own AI models as experts on your business, brand, products to engage with customers in real-time.

Reports and Analytics

Gain automatic insights into how your team works. Learn what do to make them more effective and improve customer engagement.
Use Cases

Health Care / Compliance

Work with automated sidekicks to quickly create, annotate and publish important content to physicians and patient-facing clinical teams around the world.

Train AI Models

Train AI models to be experts on your company contents and products to deliver customer recommendations, guidance and decision support.

Retail

Deliver your company branding, messages and product information to customers in real-time with scheduled publishing, hot fixes, A/B testing and versioned rollback.

Travel

Bulk load hotel, resort and travel information from internal data sources. Curate and publish to deliver real-time search and booking for live application customers.
Documentation
Developers
Pricing

Home

Getting Started

Data Engine

User Interface

Developers

Forms

Self Managed

Actions

You can optionally configure Actions that execute when a release goes live.

Some actions support variables. The following variables are always available:

release - a JSON object of the release along with all metadata about the release
releaseId - the ID of the release object
branchId - the ID of the release branch
snapshot - the ID of the snapshot that was generated after merge

The following Actions are supported:

Send Email
Fire Web Hook

For each action, you need to provide a configuration JSON block that informs the action of how to run. Here are a few examples:

Send Email

{
    "to": "bob@uncle.com",
    "subject": "A release was triggered for UA: ${release._doc}",
    "body": "Information about the release"
}

Web Hook

{
    "method": "POST",
    "url": "https://internal.mycompany.com/publish"
}

The Web Hook endpoint will receive a JSON payload with the variables for the release. The headers for the request will include the following:

CLOUDCMS_BRANCH - the ID of the snapshot branch
BRANCH - the ID of the snapshot branch
branchId - the ID of the snapshot branch

These are sent in triplicate with different names. This is to more effectively support different virtualized preview servers and custom endpoints that customers have built. The Cloud CMS Application Server supports all three of these headers. The preferred header going forward is CLOUDCMS_BRANCH.