Cloudpress
CMS & ContentConnect AI agents to Cloudpress, which exports content from Google Docs and Notion to a connected CMS. Agents start exports, convert docs to HTML or Markdown, and monitor job status so publishing to WordPress, Webflow, or Contentful happens without copy and paste.
What This Integration Enables
Cloudpress is not a CMS and it is not trying to be one. It exists because writers will not leave Google Docs and Notion, and because no CMS accepts what those tools produce without somebody cleaning it up first. That cleanup is the tax this connector removes. FlowRunner agents call Cloudpress to move a finished document into WordPress, Webflow, Contentful, or another connected destination with its headings, links, tables, and images intact, then poll the resulting job until it reports done.
The agent can also stop short of publishing. Convert Google Doc To HTML and Convert Google Doc To Markdown return the rendered document without touching a CMS at all, which makes them useful both as an output in their own right and as a preview of what an export would produce. That preview is what turns the risky part of this integration into a human-in-the-loop moment instead of a surprise, because Cloudpress exports can be pointed at an existing destination document and replace what is already published there.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Approved drafts into the marketing site
An editor finishes a post in Google Docs and moves it into the approved folder. The agent retrieves the document JSON, calls Export Google Doc against the WordPress destination connection, and polls Get Job Status until the job completes. It reads the warnings the job returns, because a warning usually means an image failed to download or an embed was not recognized, and posts those warnings to the content channel rather than letting them disappear into a log. The writer never opens the CMS and the editor never reformats a heading.
A Notion content calendar feeding a headless CMS
A content team plans in Notion and ships to Contentful. When a page in the Notion database reaches the ready status, the agent calls List Connections to resolve the Notion source and the Contentful destination, then starts Export From Connection with the Notion page ID. Additional field mappings carry the calendar's own metadata, such as the author and the campaign, into the destination entry so the CMS record arrives complete rather than half filled. The team plans where they already plan, and the structured entry appears where the site reads from.
Conversion with no CMS on the other end
Not every document is destined for a site. An agent building a weekly digest calls Convert Google Doc To Markdown on each approved doc and assembles the results into a newsletter body, with no export and no destination connection involved. The same call is what the agent uses as a dry run before a real export: render the document, show a person what Cloudpress will produce, and only then commit it to a live destination.
Human-in-Loop Highlight
The dangerous operation here is not publishing, it is republishing. An export that carries a destination reference writes over the document already sitting at that reference, and Cloudpress will do it faithfully whether the reference is right or wrong. So when an agent is about to export into an existing destination document rather than create a new one, it stops. It calls Convert Google Doc To HTML first, checks List Document Exports for what was last sent to that destination, and posts a message to the content channel: "This export will replace the live page at [destination]. Here is the rendered document that would replace it, and here is what was last exported there on [date]. Publish, or send this to a new document instead?" The editor answers in the channel and the agent resumes, either overwriting deliberately or creating a fresh destination document. The connector is happy to overwrite. The decision about which live page gets replaced belongs to a person who knows what is on it.
Agent Capabilities
13 actionsExports
2- Export From Connection Exports a document from a connected source, such as Notion, to a connected CMS destination. The agent supplies the source and destination connection IDs plus the source document reference, and receives a job to poll. Used when both ends of the pipeline are already configured in Cloudpress.
- Export Google Doc Exports a Google Doc to a connected CMS destination by uploading the document JSON directly. Supports auto mapping of document properties, a destination reference to overwrite existing content, additional field mappings, and per export webhook endpoints. Used when the agent already holds the document from the Google Docs API.
Conversions
2- Convert Google Doc To HTML Converts a Google Doc to HTML without exporting anything. Options cover returning a full HTML document, detecting embeds from standalone links, and turning single cell tables into fenced code blocks. Used to render a preview before an overwrite, or to feed HTML to a destination Cloudpress does not connect to.
- Convert Google Doc To Markdown Converts a Google Doc to Markdown without exporting anything. Used for docs repositories, newsletters, and anywhere the destination wants Markdown rather than a CMS entry.
Jobs
2- Get Job Status Retrieves the status and result of an export job by ID. Used to poll an export to completion and to read the warnings and output documents it produced, which is where partial failures such as a missing image surface.
- List Document Exports Retrieves the export history for the account, including source connection, source document, destination connection, and timestamp. Used to answer what was last published to a destination before deciding whether to overwrite it.
Connections
2- List Connections Retrieves the configured content source and CMS destination connections, optionally filtered by kind or CMS type. Used to resolve a destination by name instead of hardcoding an ID into a flow.
- Get Connection Retrieves a single connection by ID, including its name, CMS type, and kind. Used to confirm an agent is about to write to the destination a person expects.
Account
1- Get Account Retrieves the account tied to the access token, including the account name and the authenticated user. Used as a connection check at the start of a flow.
Webhooks
4- Create Webhook Registers a webhook that Cloudpress calls when the specified events occur for the given connections. Used to be notified of export completion or failure instead of polling.
- List Webhooks Retrieves the webhooks configured in the account with their endpoints, events, and connections. Used to audit which systems are listening to export events.
- Get Webhook Retrieves a single webhook by ID. Used to verify an endpoint before relying on it.
- Delete Webhook Permanently deletes a webhook so Cloudpress stops calling its endpoint. Used to retire a listener when a downstream flow is decommissioned.
Frequently Asked Questions
What can FlowRunner do with Cloudpress?
FlowRunner agents can run Export From Connection, Export Google Doc, and Convert Google Doc To HTML in Cloudpress, plus 10 more actions.
Does connecting Cloudpress to FlowRunner require OAuth?
No. Cloudpress connects to FlowRunner with an API key, no OAuth flow required.
Can Cloudpress trigger a FlowRunner workflow automatically?
Cloudpress doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Cloudpress
$100 in credits. No card required. Connect in minutes.