Automate Webflow Item Creation & Updates with n8n

What This Workflow Does

This workflow lets you create a Webflow CMS item and update it right after, all by clicking a button in n8n. It solves the problem of manual editing in Webflow and saves time while reducing mistakes. When you run it, a new CMS entry is made, updated with more details, and then its latest status is fetched for confirmation.

You don't need to wait for scheduled times. You control when the item is added and changed, without hopping in and out of Webflow.

Tools and Services Used

• n8n: For building and running the automation workflow.
  
• Webflow CMS API: To create, update, and get CMS items remotely.
  
• Manual Trigger node: Starts the workflow manually on demand.
  
• Webflow node: Handles create, update, and get operations on CMS collections.
  

Who Should Use This Workflow

This workflow is made for content managers or anyone who needs to add and update Webflow CMS data often. You don't have to open Webflow every time to edit items. If you want less errors and save editing time, this is for you.

You can run this any time you want, no hard schedules needed.

Inputs, Processing, and Output

Inputs

• Trigger from the Manual Trigger node.
  
• Static fields for the new CMS item, like name and slug.
  
• Site ID and Collection ID to tell Webflow where to operate.
  

Processing Steps

• Webflow node (create) makes a new CMS item with basic data.
  
• Webflow node (update) immediately adds more data, including image URL and flags.
  
• Webflow node (get) fetches the final updated item for confirmation.
  

Outputs

• Confirmation of a created and updated Webflow CMS item.
  
• Data you can use for notifications, reports, or logs.
  

Beginner Step-by-Step: How to Use This Workflow in Production

Step 1: Download and Import

1. Click the Download button on this page to save the workflow file.
   
2. Open your n8n editor.
   
3. Use "Import from File" to load the workflow into n8n.
   

Step 2: Configure Credentials and IDs

1. Add your Webflow API credentials in n8n if not added already.
   
2. Open each Webflow node and check the Site ID and Collection ID fields.
   
3. Update these IDs to match your Webflow site and collection.
   

Step 3: Adjust Item Fields If Needed

1. Check nodes that create or update items for field values like "name" and "slug".
   
2. Change any text or URLs to match your content needs.
   

Step 4: Test the Workflow

1. Click “Execute Workflow” to run it manually via the Manual Trigger node.
   
2. Watch the output to check the item appears in your Webflow CMS.
   

Step 5: Activate for Use

1. Once tested, activate the workflow in n8n to run when triggered.
   
2. Run it anytime you want new content created and updated.
   

If self hosting n8n is your setup, consider checking self-host n8n for managing your workflows safely.

Common Customizations

• Change or add CMS fields in the update node (ex: description, price).
  
• Replace Manual Trigger with Schedule Trigger to run automatically each day or week.
  
• Add Error Trigger node to send notifications if Webflow API calls fail.
  

Troubleshooting Tips

Problem: "Invalid site or collection ID in Webflow node"

This means some ID entered is wrong or outdated.

Check the exact IDs on your Webflow dashboard and update nodes with correct ones.

Problem: "Could not update CMS item"

The workflow cannot find the right item ID or lacks permission.

Make sure the update node uses {{$json["_id"]}} to get the item ID from the create node.

Also check your Webflow API Key has write access.

Pre-Production Checklist

• Confirm Webflow API Key is valid with required rights.
  
• Check siteId and collectionId values match your Webflow setup.
  
• Run a manual test to verify item creation and update.
  
• Ensure your network is stable and not blocked from Webflow API.
  
• Verify updated fields appear correctly in Webflow CMS.
  

Summary

✓ Saves time by skipping manual editing in Webflow CMS.

✓ Reduces mistakes by automating create and update steps.

→ Gives control to run whenever needed without automated schedules.

→ Provides data to confirm successful CMS updates.