Short answer: You can update cms item in Webflow by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Webflow Update CMS Item action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Collection ID collection_id | string | Required | Collection ID. Example: 63a...abc |
Item ID item_id | string | Required | Item ID. Example: 64b...def |
Fields fields | json | Required | JSON object of the collection-item field keys to update. Field keys must match your Webflow collection schema slugs (e.g. "name", "slug", "post-body"). Example: {"name":"Updated Title","slug":"updated-slug"} |
Draft isDraft | options | Optional | Draft. Options: No (published), Yes (draft) |
{"collection_id": "e.g. 63a...abc","item_id": "e.g. 64b...def","fields": "{\"name\":\"Updated Title\",\"slug\":\"updated-slug\"}","isDraft": "{{trigger.isDraft}}"}
{"id": "64b...def","fieldData": {"name": "Updated Title"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.