Add "isDraft" parameter to Webflow Node (CMS Items)

Feature Requests
,
1

I would like to request the addition of the isDraft property to the Webflow node, specifically for the Create and Update operations on CMS items.

The idea is:

To add a new boolean option/toggle called “Is Draft” to the Webflow node for “Create” and “Update” operations.
This toggle should map to the isDraft property in the Webflow CMS API v2. When enabled, the item remains in a “Draft” state instead of being automatically moved to the “Staged for Publish” queue.

My use case:

I manage automated content updates where several items might be updated via n8n simultaneously. Currently, when the node performs an Update, the items are automatically “Queued to Publish” (Staged).
If anyone on the team clicks “Publish” on the Webflow Designer to push a different change, all these “Staged” items from n8n go live immediately without prior human review. By having an isDraft option, I can ensure these updates stay safe as drafts until an editor manually approves them.

I think it would be beneficial to add this because:

The current behavior creates a critical bottleneck and a risk for production environments.
The Problem: There is currently no way to update an item via n8n without it entering the publishing queue.
The Risk: Incomplete or unreviewed updates are accidentally published during site-wide deployments.
The Solution: Implementing isDraft: true allows for a true “Human-in-the-loop” workflow, where automation handles the data entry but humans retain final control over what goes live.

Any resources to support this?

Yes, the Webflow API v2 documentation specifically includes the isDraft field to solve this exact staging issue.
Webflow API Reference: Update Items | Webflow Developer Documentation
Field: isDraft (Boolean).

Are you willing to work on this?

I am not a core developer, but I can provide detailed testing and feedback to ensure the isDraft vs isArchived logic works correctly in real-world SEO and content workflows.

2

I’ve faced a similar need where I wanted to prevent my updates via n8n from being automatically published. Having an “isDraft” toggle in the Webflow node to keep items as drafts would be really useful. Meanwhile, a workaround could be to manage a custom field in Webflow to flag the status, then have a manual step or another workflow to publish items after approval. Not 100% ideal but it can reduce risks. Otherwise, I think your suggestion is very relevant for ensuring true human control in the process.

3

Hello! For now, I’ve managed to solve it using an HTTP request, adding the parameter isDraft: true in the JSON body. I can share the node with you if you need it. But when implementing it using the HTTP request, I realized that it could be something simple to implement natively and, above all, very useful.

1 Like