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
| Platform | How it connects | Draft | Schedule | What a post is |
|---|---|---|---|---|
| WordPress | Site address, username and an application password. A site hosted on WordPress.com signs in with WordPress.com. | Yes | On WordPress | A post |
| Shopify | Install Hermoso from the Shopify App Store. The store is the account, so there is nothing to paste. | Yes | On Shopify | An article in one of the store's blogs |
| Webflow | A site API token, with Sites set to read-only and CMS set to read and write. | Yes | Through Hermoso | An item in the CMS collection you choose |
| Wix | An API key with the Blog and Media Manager permissions, and the site ID. | Yes | On Wix | A blog post |
Connect
- WordPress: Connectors, then the WordPress card, or
connect_connectorwith{"provider": "wordpress", "fields": {"siteUrl": "https://yourblog.com", "username": "...", "appPassword": "..."}}. Make the application password in WordPress under Users, Profile, Application Passwords. - Webflow: Connectors, then the Webflow card, or
connect_connectorwith{"provider": "webflow", "fields": {"token": "..."}}. Generate the token in Webflow under Site settings, Apps & integrations, API access. Hermoso reads the site's CMS collections and picks the blog collection when one is clearly it. When it cannot tell, choose it on the card or withset_webflow_collection. - Wix: Connectors, then the Wix card, or
connect_connectorwith{"provider": "wix", "fields": {"apiKey": "...", "siteId": "..."}}. Make the key in the Wix API Keys Manager. The site ID is the long id after/dashboard/in the address of the site's dashboard. The site must be published and have the Wix Blog app: Wix refuses blog requests for a site that has never been published. A key made a few minutes ago can be refused for a short while as Wix activates it; Hermoso says so, and trying again a few minutes later works. - Shopify: install Hermoso from the Shopify App Store and open it once from your Shopify admin. A store that installed Hermoso before blog posts were added is asked to approve one new permission the next time the app is opened.
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.
| Field | What it is |
|---|---|
title | Required. The post's title. |
text | The body. Plain text and light markdown (## headings, - lists, **bold**, [links](url)) are formatted for the platform. HTML is sent as you wrote it. |
status | publish (the default) or draft. WordPress, Shopify and Wix also take a future date and schedule the post themselves. |
excerpt | The summary shown in lists. |
slug | The end of the post's address. |
imageUrl, imageUrls | The first image is the cover (featured) image. Any others go inside the body. |
seoTitle, seoDescription | The search title and description, on Shopify, Webflow and Wix. |
| Platform | Publish | Also takes |
|---|---|---|
| WordPress | post_to_wordpress | Categories and tags by name (a missing one is created), a video, and the statuses pending and private. |
| Shopify | post_to_shopify_blog | Tags, an author name, which blog (list_shopify_blogs) when the store has several, and a video in the body. |
| Webflow | post_to_webflow | fieldData: any other field of your collection, by its slug, such as an author or category reference. |
| Wix | post_to_wix | Up 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:
- a required plain text field named like a title or headline takes the post title;
- a required plain text field named like a summary, intro, excerpt or description takes your
excerpt, or the first lines of the body when you give none, kept within the field's length limit; - every required image field takes the post's cover image, so attach one when the template asks for images;
- a required publish date takes the time of posting.
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.
- On the platform: pass a future
datetopost_to_wordpress,post_to_shopify_blogorpost_to_wix. The post is stored on the platform as scheduled and the platform publishes it. - Through Hermoso:
schedule_postwith one of the four blog channels inchannels:["wordpress"],["shopify_blog"],["webflow"]or["wix"]. The post waits in your Hermoso calendar beside your social posts and Hermoso publishes it at that time. This is the way to schedule a Webflow post, because Webflow's API has no scheduling.
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
| Platform | List and read | Edit | Delete |
|---|---|---|---|
| WordPress | list_wordpress_posts, get_wordpress_post | update_wordpress_post | delete_wordpress_post: to the trash, or permanently |
| Shopify | list_shopify_articles, get_shopify_article | update_shopify_article | delete_shopify_article: permanent |
| Webflow | list_webflow_items, get_webflow_item | update_webflow_item | delete_webflow_item: permanent |
| Wix | list_wix_posts, get_wix_post | update_wix_post | delete_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.