Content Item Lifecycle

Kontent.ai stores every piece of content, such as an article or product description, as an item that moves through stages like draft, review, and published. A Beam agent reads an item's current stage and checks it against the schedule or rule a content team has approved, such as retiring a promotion once its end date passes. Where the connector and account permissions allow it, the agent moves the item to its next stage and updates the linked components that reference it elsewhere. Items still referenced elsewhere, or missing a required field for their stage, are routed to a human before the change is made.

Content Type Structures

Every item in Kontent.ai follows a content type that defines its fields, such as headline, body, or image, so structure stays consistent across an organization. A Beam agent reads an item against its content type before making any change, confirming which fields exist and which are required before writing anything back to it. Where the connector allows it, the agent fills in or updates the fields a workflow needs and leaves the rest of the item untouched. Items where a required field is empty, or where the content type itself has recently changed, are routed to a human to check before the item moves forward.

Multichannel Content Delivery

Kontent.ai serves the same content item out to more than one channel, such as a website and an app, from a single source. A Beam agent reads which channels an item is set to reach and confirms the item meets each channel's requirements before anything goes live there. Where the connector and account permissions allow it, the agent clears the item for the channels it satisfies and holds it back from the ones it doesn't. Items that fail a channel's requirements, or that a team has marked for manual approval, are routed to a human before that channel receives them.