How To Structure Webflow CMS Workflows in Make and Zapier

A Webflow CMS workflow needs to distinguish new items from existing items. Save the Webflow item ID when you create each item.

The original series uses Zapier and Integromat, now called Make. The routing principle still applies.

Store the identifiers

In your source table, keep the source record ID, Webflow Collection ID, and Webflow item ID separately. The Collection ID identifies the group. The item ID identifies the specific entry.

Route create and update actions

1. Load the source record and its saved Webflow item ID.
2. If an item ID exists, update that item.
3. If no item ID exists, check whether an earlier create already succeeded.
4. Create the item only when no matching item exists.
5. Save the returned item ID before marking the workflow complete.

Use the source record ID as your matching key. Do not rely on a name that someone may change. Prevent concurrent runs from creating the same source record twice.

Separate content changes from publication

Webflow's CMS API distinguishes staged content from live content. Check whether your connector creates a draft, updates staged data, or publishes content. Start with one draft item. Change its name and confirm the workflow updates the same item ID. Check a failed run before retrying a create action.

Continue with field mapping in part two. Then review reference fields before linking collections.

For a current implementation path, update Webflow CMS items from Airtable with Make.

Original video

Watch the original video on How To Structure Webflow CMS Workflows in Make and Zapier.

Before expanding the workflow, map Airtable values to Webflow field types.