Automate Notion & Webflow with Make.com

This step-by-step guide shows you how to connect Notion and Webflow using make.com so you can automate content publishing, sync data, and remove repetitive manual work from your workflow.

By following this tutorial, you will learn how to turn Notion into a content hub and automatically push approved items into Webflow without writing code.

Why automate Notion and Webflow with Make.com

When you manage content in Notion and publish it in Webflow, keeping both systems aligned can become a time-consuming copy-and-paste routine. Automation with make.com solves this problem by creating a bridge between your database and your live site.

With a single scenario, you can:

• Publish new blog posts or pages from Notion directly to Webflow.
• Update existing Webflow CMS items when content changes in Notion.
• Use a status or checkbox property in Notion to control what is published.
• Save time and reduce mistakes caused by manual editing.

What you need before building in Make.com

Before creating your automation, prepare your tools and accounts. This ensures a smooth setup in make.com and avoids connection errors later.

Required accounts and access

• A Notion account with permission to create and edit databases.
• A Webflow account with access to a project that uses the CMS.
• A make.com account to create and run scenarios.

Make sure you can log in to all these services in the same browser session. You will grant access to make.com during the initial connection steps.

Prepare your Notion database

Set up a Notion database that will hold the content you want to publish in Webflow. Each row in this database should represent one Webflow CMS item, such as a blog post or case study.

Typical properties you might create in Notion include:

• Title – main post title, mapped to the Webflow CMS name.
• Slug – URL slug to match in Webflow.
• Rich content – body text or article content.
• Tags or categories – multi-select fields you can map to Webflow reference or option fields.
• Status – for example: Draft, Ready to Publish, Published.
• Webflow ID – an empty text property you will use later to store the Webflow item ID.

The Webflow ID field becomes important when you want to update existing CMS items from make.com rather than creating duplicates.

Prepare your Webflow CMS collection

Open your Webflow project and identify the CMS collection that will receive content from Notion. Note the fields that are required, their types, and any validation rules.

Common CMS fields to map include:

• Name or Title
• Slug
• Rich text body
• Thumbnail image
• Summary or Excerpt
• Category, Author, or other reference fields

Ensure that the structure of your Notion database mirrors what is needed in the Webflow collection. This will simplify the mapping process in make.com.

Create your first Make.com scenario

Once your Notion database and Webflow CMS are ready, you can build a scenario in make.com that links them together and automates content transfer.

Step 1: Start a new scenario in Make.com

1. Log in to your make.com dashboard.
2. Click Create a new scenario.
3. In the module search, type Notion and add the Notion module as the trigger or first data source.

During this step, you will be asked to connect your Notion account. Approve the requested permissions so that make.com can read your database.

Step 2: Choose a Notion trigger or search module

Depending on your use case, you can start the scenario in two main ways:

• Watch database items – triggers when new pages or rows are added or updated in the selected Notion database.
• Search or list database items – runs on a schedule in make.com and pulls items that meet a specific filter, such as Status = “Ready to Publish”.

Configure the trigger to point to your prepared Notion database and, if available, define filters or conditions so that only the right items move to Webflow.

Step 3: Add a Webflow module in Make.com

1. Click the plus icon next to the Notion module in your scenario.
2. Search for Webflow and add it as the next module.
3. Choose an action such as Create Item or Update Item for your CMS collection.

When prompted, connect your Webflow account to make.com and select the specific site and CMS collection that will receive the data.

Step 4: Map Notion fields to Webflow CMS fields

The most important configuration step inside make.com is field mapping. For each Webflow field, choose the corresponding Notion property.

Typical mappings include:

• Webflow Name ← Notion Title
• Webflow Slug ← Notion Slug
• Webflow Rich text ← Notion content property
• Webflow Category ← Notion tags or select property
• Webflow Main image ← Notion file or image URL

If you are using the Webflow ID field in Notion, map it carefully when using update actions. This allows make.com to identify which CMS item to modify.

Step 5: Add logic and filters in Make.com

To keep your workflow clean and reliable, use filters and conditions between modules in make.com. Useful examples include:

• Only continue if the Notion Status equals “Ready to Publish”.
• Branch logic to create a new Webflow item if the Webflow ID field is empty, or update the existing item if the field contains an ID.
• Skip items that do not have a required field such as title or slug.

By adding these checks, you prevent broken CMS entries and keep your data quality high.

Step 6: Test and activate your scenario

1. Click Run once in make.com to test the scenario with sample items.
2. Review the output in both Notion and Webflow to verify that content, slugs, and statuses are correct.
3. Adjust mappings or filters as needed, then set a schedule or let the trigger run automatically.
4. Activate the scenario so that it runs without manual intervention.

After activation, any new or updated items that meet your conditions will move from Notion to Webflow automatically through make.com.

Best practices for a stable Make.com setup

To keep your automation reliable over time, follow these habits when working with make.com and your connected tools.

• Keep schemas aligned: When you add or change fields in Webflow, update your Notion database and the scenario mapping accordingly.
• Use clear statuses: Control publishing with explicit states like Draft, In Review, Ready, and Published.
• Monitor logs: Check scenario runs inside make.com to quickly fix mapping errors or permission issues.
• Document your workflow: Describe how content should move between Notion and Webflow so your team uses the system consistently.

Learn more about Make.com and advanced workflows

If you want to dive deeper into connecting Notion and Webflow, explore the original tutorial on the official site at make.com’s Notion–Webflow how-to guide. It expands on configuration details, advanced mapping tips, and scenario variations for different CMS structures.

For broader automation strategy, technical consulting, and optimization support around tools like make.com, you can also visit Consultevo to explore professional implementation services.

With a solid Notion database, a well-structured Webflow CMS, and a carefully mapped scenario in make.com, you can turn a manual publishing workflow into a robust, automated content pipeline that scales with your project.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help