# Webflow status field

### About Webflow Status field

Webflow lets you control the status of an item by marking it as either Published, Draft, or Archived. With our Webflow Status field sync, you can now control that state from apps like Airtable or Notion.

For example, if you manage your blog content in Notion, you can now control whether those blog posts are live or in draft from within Notion.

{% hint style="info" %}
Using the Webflow Status field may reduce sync speed by a few seconds per record.
{% endhint %}

### How to set up the Webflow Status field

1. Add a single-select field to your Airtable or Notion table and title it "Webflow Status"
2. Make sure it has *exactly* these three options:
   1. "Archived"
   2. "Draft"
   3. "Active"
3. In Whalesync, map that field to Webflow's "Webflow Status" field
   1. If adding this field to an existing base, make sure to initialize the data from Webflow (see screenshot below)

<figure><img src="/files/ZzerzaBlrEXxMZHLffat" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/kUrTpFLFHgvEpI4nFiYj" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Airtable lets you set a default value for single select fields so you can, for example, set a default value of 'Draft'.\
\
\*Note - if no default value is set and the value is empty in this field, the behavior will default to 'Published'.
{% endhint %}

### "Active" vs. "Published"

In Webflow, you can make an item "Published" as well as "Staged for Publish". When an item is "Staged for Publish" it means it will become published next time you publish your Webflow site.

With our Webflow Status field, both "Published" and "Staged for Publish" are captured by the option "Active".

### Mini-demo

<figure><img src="/files/gnDpQqshceLkL8VvVjZO" alt=""><figcaption><p>Demo using the Webflow status field</p></figcaption></figure>

### Limitations

#### Status field in conjunction with reference fields

One limitation of Webflow CMS collection items is that a **published** Webflow item cannot reference a **draft** Webflow item in a reference field. Unfortunately this is a Webflow restriction.

For example, the following will result in an error from the Webflow API:

1. Create two collections in Webflow. For this example, let's call them *People* and *Teams*
2. Create a reference field on the *People* collection that points to *Teams*
3. Create an item "Marketing" in the *Teams* collection and set it to "published"
4. Create an item "Sally Smith" in the *People* collection, add a reference to the "Marketing" item in the reference field, and set "Sally Smith" to "published"
5. Create a sync in Whalesync using the two Webflow collections and sync it to another app (such as Airtable)
6. In Airtable, set the Webflow Status field on the "Marketing" item to "Draft"

This will result in an error that will show up on the Whalesync Issues page. Webflow will reject the attempt to set the "Marketing" item to "Draft" because the **published** person "Sally Smith" is referencing the item. Unfortunately Whalesync does not have a workaround for this.

### Field Validation and Error Handling

#### Enforced Status Options

Whalesync now strictly enforces that the Webflow Status field must contain exactly one of these three values:

* **Archived**
* **Draft**
* **Active**

If you use any other value in your status field, you will receive an error message like:

```
Data "Pending" isn't one of the valid values: [Draft, Active, Archived].
```

This validation helps ensure consistency and prevents sync errors.

#### "Published" Option Support

We understand that "Published" might feel like a more natural option name for many users, so Whalesync accepts "Published" as a valid value to make your setup easier. However, here's what happens when you use it:

* Whalesync will automatically sync "Published" values back as "Active" to maintain consistency with our three-option system
* This ensures your data stays aligned with the standard status options (Draft, Active, Archived)
* You can use "Published" if it makes more sense for your workflow, just be aware that it will appear as "Active" when synced back

This flexibility allows you to use the terminology that feels most natural while keeping the system consistent.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.whalesync.com/connectors/webflow/webflow-status-field.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.