Automated Content Synchronization from Notion to Webflow CMS Drafts - n8n Workflow

• Content teams managing large-scale documentation or blog posts in Notion.


• Developers or marketers who need to automate the content deployment pipeline to Webflow.


• Users looking for advanced examples of integrating Notion and Webflow using a custom n8n workflow structure.


• Anyone seeking robust n8n templates for data synchronization and status tracking.

Managing content across multiple platforms, especially when Notion is used for creation and Webflow for publishing, often leads to tedious manual transfers. This comprehensive n8n workflow solves that problem by providing a reliable, automated synchronization pipeline.

This specific n8n automation triggers manually to fetch content prepared in Notion. It performs a vital check: does the item already exist in Webflow? Based on this, the n8n node decides whether to create a new draft item or update an existing one, ensuring no data is overwritten and keeping Webflow items in sync with the Notion source. Furthermore, the workflow uses a Notion n8n node to update the page status upon successful submission, providing crucial feedback within your project tracking database. This intricate n8n template is designed for high-volume content operations.

This n8n workflow operates upon manual execution, making it a reliable, on-demand synchronization tool.

1. Trigger and Query: The process begins with a manual n8n trigger. The Get Notion Pages n8n node immediately queries a specified Notion database, filtering for pages with the 'Status' property set to 'Ready for publish' and matching a specific project relation.


2. Item Processing: The workflow uses the Loop Over Items n8n node to process each 'Ready for publish' page sequentially.


3. Content Retrieval and Merge: The workflow executes the Get Notion Block n8n node to pull the full content blocks for the page. A subsequent Merge Content n8n node (a code node) combines the Notion page properties and the raw block content into a unified JSON structure, ready for Webflow.


4. Webflow Lookup: The Get Webflow Items n8n node queries the target Webflow collection to retrieve existing items, primarily checking for the presence of an item with the same 'Name'.


5. Decision Point: The Update or Create n8n node (Switch node) acts as the core logic flow control. It evaluates whether the content name exists in the Webflow list. If the name is not found, it branches to the 'Create' path. If the name is found, it branches to the 'Update' path.


6. Webflow Action: The flow uses a dedicated HTTP Request n8n node to either Create Webflow Item (POST) or Update Webflow Item (PATCH), ensuring the content is set as a draft (isDraft: true).


7. Status Tracking: Upon successful Webflow integration, the Done n8n node updates the original Notion page status to '5. Done'. Critically, if the Webflow API call fails, the error handling path routes to the hold n8n node, setting the Notion status to 'On Hold' for manual review. This robust error handling is key to this n8n workflow.


8. Completion and Wait: A Log Submission node records the action, followed by a brief Wait n8n node to manage API rate limits before the loop continues to the next item.

To use this n8n template, follow these steps:

1. Import: Copy the provided n8n workflow JSON and import it into your n8n instance.


2. Notion Credentials: You need active credentials for the Notion API. Update the credential links in both the Get Notion Pages and the status update n8n nodes (Done, hold). Ensure your Notion integration has access to the target database and pages.


3. Webflow Credentials: This n8n workflow uses HTTP Bearer Auth credentials to interact with the Webflow API. Replace the existing credentials with your Webflow API token, ensuring it has read/write permissions for the CMS.


4. Configuration:

1. Execution: Once configured, execute the n8n workflow manually to start the synchronization process.

When clicking ‘Execute workflow’ (Manual Trigger): Serves as the starting n8n trigger for the entire automation. This is an on-demand n8n workflow.
Get Notion Pages (Notion n8n node):
Function: Queries the Notion database for pages ready for publication.
Key Configuration: Resource: databasePage, Operation: getAll. Filters based on 'Status: Ready for publish' and a specific 'Project' relation.
Loop Over Items (Split In Batches n8n node):
Function: Ensures the entire n8n workflow executes sequentially for each Notion page retrieved, preventing resource congestion.
Merge Content (Code n8n node):
Function: A critical n8n node that reconstructs the content. It parses the raw block content (which is expected to be a serialized JSON object containing all required Webflow fields) and combines it with the page metadata (like name and ID) into a single payload used downstream.
Get Webflow Items (HTTP Request n8n node):
Function: Checks the Webflow CMS Collection for existing items based on the content's name.
Key Configuration: Uses a Bearer Token for authentication and queries the collection endpoint.
Update or Create (Switch n8n node):
Function: Determines the path forward: whether to update an existing Webflow item or create a new one, based on the Get Webflow Items lookup result.
Create Webflow Item / Update Webflow Item (HTTP Request n8n nodes):
Function: Performs the actual Webflow API interaction (POST for creation, PATCH for updates).
Key Configuration: Heavy use of Handlebars expressions (e.g., {{ JSON.stringify($('Merge Content').first().json.mergedContent.fieldData.name) }}) to map dozens of Notion properties directly to specific Webflow fields. Both are configured to set the item as a draft (isDraft: true).
Done / hold (Notion n8n nodes):
Function: Provides essential status feedback. Done updates the Notion page status to '5. Done' on success. hold updates the status to 'On Hold' specifically after an API error during the creation or update steps, leveraging the error output of the preceding n8n node.