hermosodocs

Blog publishing: WordPress, Shopify, Webflow and Wix

Hermoso publishes blog posts to the site a brand already runs. You write the post once, as plain text, light markdown or HTML, and it is formatted the way each platform stores it. Every create and every edit answers with the platform's own copy of the post, read back after the change, and with its public address once it is live. Publishing a blog post costs no credits.

The four platforms

PlatformHow it connectsDraftScheduleWhat a post is
WordPressSite address, username and an application password. A site hosted on WordPress.com signs in with WordPress.com.YesOn WordPressA post
ShopifyInstall Hermoso from the Shopify App Store. The store is the account, so there is nothing to paste.YesOn ShopifyAn article in one of the store's blogs
WebflowA site API token, with Sites set to read-only and CMS set to read and write.YesThrough HermosoAn item in the CMS collection you choose
WixAn API key with the Blog and Media Manager permissions, and the site ID.YesOn WixA blog post

Connect

Each credential is checked against the platform before it is saved. A wrong key or a token without the right permissions is refused with the reason, and nothing is stored.

Write a post

Every publish tool takes the same core fields.

FieldWhat it is
titleRequired. The post's title.
textThe body. Plain text and light markdown (## headings, - lists, **bold**, [links](url)) are formatted for the platform. HTML is sent as you wrote it.
statuspublish (the default) or draft. WordPress, Shopify and Wix also take a future date and schedule the post themselves.
excerptThe summary shown in lists.
slugThe end of the post's address.
imageUrl, imageUrlsThe first image is the cover (featured) image. Any others go inside the body.
seoTitle, seoDescriptionThe search title and description, on Shopify, Webflow and Wix.
PlatformPublishAlso takes
WordPresspost_to_wordpressCategories and tags by name (a missing one is created), a video, and the statuses pending and private.
Shopifypost_to_shopify_blogTags, an author name, which blog (list_shopify_blogs) when the store has several, and a video in the body.
Webflowpost_to_webflowfieldData: any other field of your collection, by its slug, such as an author or category reference.
Wixpost_to_wixUp to 30 tags and 10 categories by name (a missing one is created), and a video in the body.

Nothing you wrote is shortened. A title, tag or excerpt over a platform's limit is refused with the limit, so you can change it yourself.

Webflow: your collection's own fields

A Webflow blog is a CMS collection with fields its designer chose, so Hermoso maps the post onto the collection it finds: the title and slug, the rich text field for the body, a plain text field for the summary, an image field for the cover, and search title and description fields when the collection has them. list_webflow_collections with a collectionId shows the fields and the mapping. If the post has a part the collection has no field for, the post is refused and the reply names the missing field.

Required fields. Blog templates often require fields of their own. Hermoso fills the ones it can from the post itself:

Hermoso never guesses an author, a category or any other choice. In the web composer, the fields it cannot fill appear under the channels as pickers of the values your Webflow site allows, read from Webflow when you choose the channel. Over the API or MCP, list_webflow_collections with a collectionId returns required: auto (filled from the post) and ask (each field with its allowed values), and a post missing one is refused with each field's slug, type and allowed values. Pass them in fieldData (or webflowFields on schedule_post). A reference or option may be given by its id or by its name, for example {"author": "Jane Writer", "category": "Guides"}. A text longer than a field's own limit is refused with both numbers, never cut.

Two Webflow limits to know. A cover image can be up to 4 MB. Webflow's API cannot take code blocks in a rich text field, so a body with one is refused.

Schedule

There are two ways to publish later.

A scheduled blog post needs a title. Everything that can be checked ahead of time is checked when you schedule it, so a post is not refused hours later with nobody watching.

Edit, read and delete

PlatformList and readEditDelete
WordPresslist_wordpress_posts, get_wordpress_postupdate_wordpress_postdelete_wordpress_post: to the trash, or permanently
Shopifylist_shopify_articles, get_shopify_articleupdate_shopify_articledelete_shopify_article: permanent
Webflowlist_webflow_items, get_webflow_itemupdate_webflow_itemdelete_webflow_item: permanent
Wixlist_wix_posts, get_wix_postupdate_wix_postdelete_wix_post: to the trash, or permanently

list_webflow_items with title finds every item whose title contains those words, ignoring case: "hermoso qa" finds "Hermoso QA test post". It reads up to the 1,000 most recently changed items and says so when the collection has more.

An edit changes only the fields you pass. An edit to a post that is already live is published too. A delete never runs on the first call: it answers with a sentence naming the post, and deletes only when you call it again with confirm: true.

When Wix refuses a new post, Hermoso checks the blog's drafts before it answers, because Wix can keep a draft of a post it refused. The answer names that draft and its postId, so you can publish it with update_wix_post or delete it, instead of posting a second copy.

Views and other numbers

Wix reports views, likes and comments for a published post. WordPress, Shopify and Webflow do not report views for a post through their APIs, so Hermoso shows performance for those posts as unavailable. For them, use the site's own analytics.