How to Sync Notion Webflow Content Publishing?
Description
Publish blog posts from Notion to Webflow without copy and paste. The flow scans your Notion database on a schedule, turns rich content into clean HTML, and keeps your Webflow collection up to date. It fits teams that draft in Notion but want a fast, reliable way to publish on Webflow.
On each run, the schedule pulls all blog pages from Notion and filters for a Sync to Webflow checkbox. Each selected page is processed in batches. The workflow fetches full page data and blocks, converts blocks into HTML, and grabs the cover image URL. It then compares the Notion slug with all Webflow items to decide whether to create a new post or update an existing one. A code step enforces unique slugs by adding a number when needed. After publishing, the Webflow item ID and final slug are written back to Notion, and a Slack message confirms success.
Setup needs a Notion database with a slug text field and a Sync to Webflow checkbox, plus connected Notion, Webflow, and Slack credentials in n8n. Map Webflow fields like name, slug, rich text, and image to your collection. Expect faster publishing, fewer formatting errors, and clean slug management. Great for marketing teams, agencies, and editors who want a simple and repeatable publishing flow.
Tools Required
What this workflow does?
- Scheduled runs pull all blog pages from a Notion database.
- Filter by a Sync to Webflow checkbox to control which posts go live.
- Fetch full page data and block content from Notion for each post.
- Convert Notion blocks to clean HTML for Webflow rich text fields.
- Extract the Notion cover image URL for use in Webflow collection fields.
- Compare Notion slugs with all Webflow items to choose create or update.
- Ensure unique slugs by adding a number when a conflict is found.
- Write back the final slug and Webflow item ID to Notion for tracking.
- Send a Slack success message after processing to keep the team informed.
- Batch processing supports many posts without timeouts.
What are the benefits?
- Reduce manual publishing work from 2 hours per post to 10 minutes
- Automate 90% of formatting and upload steps
- Improve content accuracy by removing 95% of copy paste errors
- Handle 10 times more posts per week with the same team
- Connect Notion, Webflow, and Slack in one flow
- Keep slugs unique and consistent across both platforms
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with Notion, Webflow and Slack. See the Tools Required section above for links to create accounts with these services.
- In Notion, ensure your blog database has a slug text property and a Sync to Webflow checkbox. Share the database with your Notion integration so it has read and write access.
- Open the Notion nodes in n8n. In the Credential to connect with dropdown, click Create new credential, then follow the on screen steps to connect your Notion account. Test the connection.
- Open the Webflow nodes. Create new credential using OAuth2 in n8n Cloud, pick your site, and authorize. Confirm you can see your target collection ID in the node.
- Open the Slack node. Create new credential with OAuth2, choose the correct workspace and channel, and authorize posting permissions. You can remove this node if you do not want notifications.
- In the Webflow create and update nodes, check field mapping: name to post title, slug to the Notion slug field, rich text to the HTML output, and image fields to the cover URL.
- Verify the Compare by slug node points to the Webflow collection list and matches on the slug field. Make sure the slug field names match your collection schema.
- Confirm the code step for slug uniqueness is active and placed before the Webflow create or update branches.
- Set the Schedule Trigger to your desired frequency. Start with manual run to test once, then enable the schedule.
- Run the workflow with one sample post. Check that the Webflow item gets created or updated, and that Notion receives the final slug and Webflow item ID.
- If you see authentication errors, recheck credentials and permissions. For Notion, ensure the integration has access to the database. For Webflow, confirm the correct site and collection are selected.
- If slugs collide or a 400 error appears, confirm the code step is enabled and the slug field is not locked by any CMS rules. Adjust field names if your Webflow schema differs.
Need help or want to customize this?
Ask in the Futurise Pro Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
