Google Docs content export

Cloudpress reads a Google Doc's content, including headings, formatting, images, and links, and converts it into the structure a CMS expects rather than a team copying and pasting it by hand. A Beam agent starts an export when a document is marked ready, such as a status change or an approval comment, reads the document's current content, and writes it to the CMS as a new entry or an update to an existing one. If the document is missing required fields, uses formatting the CMS template doesn't support, or the export fails, the agent routes it to a person before anything publishes.

Notion page export

Cloudpress also reads a Notion page the same way it reads a Google Doc, pulling the page's blocks, properties, and formatting into a CMS entry. A Beam agent starts the export when a page's status property changes to one the team has designated as ready, reads the page's content and properties, and writes them into the matching CMS fields. If a required property is empty, the page references content Cloudpress can't convert, or the destination entry already has conflicting content, the agent routes the page to a person instead of overwriting it.

CMS field mapping and formatting

Moving content from a document into a CMS means matching each piece, a title, a body, an image, a tag, to the right field, and keeping the formatting readable once it lands there. A Beam agent applies the mapping and formatting rules the team has set up for a given content type, writes the converted content into those fields, and checks that nothing landed in the wrong place. When the source document doesn't match any of the mapped content types, or a field's content looks malformed after conversion, the agent flags the entry for a person to fix before it goes live.