Publish a Webflow blog post
post_to_webflowPublish or draft a blog post in a Webflow CMS collection by mapping title, body, summary, cover image, and required fields; get the live item URL or a clear refusal for missing values.
Instructions
Use this when the user wants to publish or draft a BLOG POST on their Webflow site. It becomes an item in the site's blog CMS collection. Publishing costs no credits. A title is REQUIRED and the text becomes the body: plain text or light markdown becomes HTML in the collection's rich text field, and HTML is sent as written (Webflow's API cannot take code blocks, so a body with one is refused). Hermoso maps the post onto the collection's OWN fields: title and slug, the body, a summary field, a cover image field (up to 4 MB), and search title and description fields when the collection has them. A part the collection has no field for is refused by name, never dropped. REQUIRED FIELDS of the collection are filled from the post where they can be: a required Title or Headline field takes the title, an Intro or Summary field the excerpt (else the first lines of the body), every required image field the cover image. A required Author, Category or other choice is NEVER guessed: the refusal names each such field's slug, type and allowed values (a Reference's items by name and id, an Option's options), and you pass them in fieldData by slug; a Reference or Option value may be the item's or option's id or its name. fieldData also sets any other field. status: publish (default) or draft. Webflow's API CANNOT SCHEDULE a post: for a later time use schedule_post with the webflow channel. The reply is Webflow's own copy of the item, with its public address. Webflow has no view counts on an item: never quote one. Not connected: the user connects it under Connectors > Webflow, or you call connect_connector with provider webflow (token).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>"
},
"name": "post_to_webflow"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hook | No | the post's angle — a list_hooks id or your own wording, reused exactly | |
| slug | No | the end of the post URL (made from the title when omitted) | |
| text | No | the body: plain text, light markdown or HTML | |
| brand | No | WHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted. | |
| title | Yes | REQUIRED: the post title | |
| ideaId | No | short id of the content-plan idea this post came from | |
| recipe | No | the post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format | |
| status | No | default publish | |
| altText | No | alt text for the images | |
| excerpt | No | the summary | |
| subject | No | what the post is about | |
| imageUrl | No | one image: becomes the cover (featured) image | |
| seoTitle | No | ||
| videoUrl | No | a link to a hosted video (YouTube or Vimeo), for a collection with a Video field; never a video file | |
| fieldData | No | the collection’s own fields by slug, e.g. {author: "<item id or name>", category: "<option id or name>"} (list_webflow_collections with collectionId shows them and their allowed values) | |
| imageUrls | No | several images: the first is the cover, the rest go inside the body | |
| collectionId | No | a collection other than the one chosen for the blog | |
| allowDuplicate | No | post it even though an identical post was just made | |
| idempotencyKey | No | any stable string: a repeat within 24h returns the original post instead of posting again | |
| seoDescription | No |