CmonSite
CMS & ContentConnect AI agents to CmonSite, the French website and online store builder. Agents create, update, list, and delete blog articles so site content stays fresh without manual publishing.
What This Integration Enables
CmonSite is built for French small businesses that need a site and a store without a web team, and its API is honest about that: it covers the blog and the account, and nothing else. There is no catalog endpoint, no order endpoint, no page endpoint. That narrowness is the point rather than a gap to apologize for. The one part of a small business site that goes stale first is the blog, because it is the only part that requires somebody to write something new every month, and that is exactly the surface this connector covers.
FlowRunner agents create, read, update, and delete blog articles with their SEO metadata, publication status, publish date, categories, and tags. Because updates are partial, an agent can change one attribute, flipping a status or moving a publish date, without resending the article. The value for an agency running dozens of these sites is that publishing stops being a per site login and becomes a workflow with a human-in-the-loop step where the site's structure is at stake.
Without FlowRunner
With FlowRunner
Use Case Scenarios
An editorial calendar that publishes itself
An agency plans client content in Google Sheets. When a row is marked approved, the agent reads the body and SEO fields, resolves the client's site with Get Account Info, matches the category and tag labels against what is already published, and calls Create Blog Article with a publish date set in the future. CmonSite holds the article until that date. The account manager sees the scheduled queue by calling List Blog Articles filtered on status, instead of asking whoever published last.
Correcting a live article without republishing it
A client emails a correction: a phone number in a post is wrong. The agent finds the article with List Blog Articles, reads the current body with Get Blog Article, applies the correction, and calls Update Blog Article with only the changed field. Because CmonSite changes only what is sent, the SEO metadata, publish date, categories, and tags stay exactly as they were. The agent posts the before and after text into the client channel so the correction is on the record.
Retiring content a client no longer wants to stand behind
An old post references a product line the client has discontinued. The agent locates it, confirms the ID with Get Blog Article, and presents the account manager with two paths: unpublish it by calling Update Blog Article with a changed status, which is reversible, or call Delete Blog Article, which is not. The agent recommends the reversible one and waits. Deletion on CmonSite has no trash to recover from, so the agent treats the reversible option as the default and the permanent one as an explicit request.
Human-in-Loop Highlight
The gate on this integration is not the publish, it is the taxonomy. On create and update, CmonSite accepts categories and tags either as numeric IDs or as labels, and when a label does not match an existing entry, CmonSite creates a new one. There is no operation in this connector to rename or delete a category afterward. So a single typo, or an upstream system that writes "Actualites" where the site already uses "Actualite", permanently adds a term to a client's site navigation that nobody can remove through the API. Before the agent sends any label it has not seen before, it stops. It calls List Blog Articles, gathers the category and tag labels already in use, and posts to the account channel: "This article carries the category [label], which does not exist on [site url]. Publishing it will create a new category that cannot be removed through the API. Use an existing category, or create this one?" The account manager answers, and the agent publishes with resolved IDs rather than guessed labels. Agents can write to the site all day. Adding a permanent term to somebody's navigation is a person's call.
Agent Capabilities
6 actionsBlog Articles
5- Get Blog Article Retrieves a single article by its numeric id, returning the content along with SEO metadata, publication status, publish date, and associated categories and tags. Used to read an article before updating it, or to sync its content into another system.
- List Blog Articles Returns a paginated list of articles wrapped in a paginator envelope with the current page, page size, and total count. Supports filtering by publication status and publish date range, and sorting by publish date or id. Used to browse the publishing queue, find an id, or collect the category and tag labels already in use on the site.
- Create Blog Article Creates an article with content, SEO metadata, publish date, and category or tag associations. Categories and tags can be supplied by existing numeric ids or by label, in which case CmonSite matches or creates them. Returns the created article with its new id and public url.
- Update Blog Article Updates an existing article by id, changing only the fields supplied. Used to flip a status, move a publish date, or correct a line of copy without resending the whole article.
- Delete Blog Article Permanently deletes an article by id. There is no undo, so an agent should confirm the id with List Blog Articles or Get Blog Article first and treat an unpublish through Update Blog Article as the safer default.
Account
1- Get Account Info Returns information about the account and website tied to the configured API key, currently the site url. Used to verify the key is valid and, in a multi client setup, to confirm which website an agent is about to write to before it writes anything.
Frequently Asked Questions
What can FlowRunner do with CmonSite?
FlowRunner agents can run Get Blog Article, List Blog Articles, and Create Blog Article in CmonSite, plus 3 more actions.
Does connecting CmonSite to FlowRunner require OAuth?
No. CmonSite connects to FlowRunner with an API key, no OAuth flow required.
Can CmonSite trigger a FlowRunner workflow automatically?
CmonSite doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with CmonSite
$100 in credits. No card required. Connect in minutes.