Short answer: Drop the "Webflow → Create CMS Item" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Name name | string | Required | The item name (maps to the Name field in Webflow) |
Slug slug | string | Optional | URL slug for the item. Auto-generated if empty. |
Fields (JSON) fields | string | Optional | Additional CMS fields as JSON. Keys must match your collection schema. |
Archived isArchived | options | Optional | Archived. Options: No, Yes |
Draft isDraft | options | Optional | Draft. Options: No (published), Yes (draft) |
{"collection_id": "e.g. 63a...abc","name": "e.g. New Blog Post","slug": "e.g. new-blog-post","fields": "{\"post-body\": \"<p>Content here</p>\", \"author\": \"John\"}","isArchived": "{{trigger.isArchived}}"}
{"id": "item123","isDraft": false,"fieldData": {"name": "New Blog Post","slug": "new-blog-post"}}
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.
Triggered by anything in the catalog. Free tier available. No credit card.