WEBFLOW n8n INTEGRATION: AUTOMATE WEBFLOW WITH N8N

This trigger fires automatically whenever an item is removed from a Webflow CMS collection. It's essential for maintaining data consistency across your connected systems—when content disappears from Webflow, your other platforms need to know about it immediately.

Configuration parameters: Credential to connect with: Select your authenticated Webflow account from the dropdown. This parameter is required for the trigger to access your site. Site Name or ID: Enter the specific Webflow site name or its unique identifier. This text field is required to specify which site to monitor. Event: Pre-set to "Collection Item Deleted"—this dropdown selection is required and determines which event activates your workflow.

Typical use cases: Remove corresponding records from Airtable or Notion when blog posts are deleted. Update external inventory systems when products are removed from your catalog. Archive deleted content to Google Drive before permanent removal. Notify content managers via Slack when items are unexpectedly deleted.

When to use it: Ideal for maintaining referential integrity between Webflow and external databases, audit logging, or triggering cleanup workflows when CMS content is removed.

This trigger activates the moment a new item is added to any Webflow CMS collection. It's perfect for automating onboarding workflows, content distribution, and real-time notifications whenever fresh content lands on your site.

Configuration parameters: Credential to connect with: Required dropdown to select your Webflow account credentials for API authentication. Site Name or ID: Required text input specifying which Webflow site to monitor for new collection items. Event: Set to "Collection Item Created"—this required dropdown determines the specific event that initiates the trigger.

Typical use cases: Automatically tweet or post to LinkedIn when new blog articles are published. Add new portfolio items to a Notion database for internal tracking. Send Slack notifications to the team when new case studies go live. Sync new product listings to external marketplaces or inventory systems.

When to use it: Best suited for content distribution workflows, team notifications, cross-platform syndication, and maintaining synchronized databases across multiple tools.

This trigger fires immediately when a customer completes a purchase on your Webflow e-commerce store. It's the foundation for order processing automations, from fulfillment notifications to accounting integrations.

Configuration parameters: Credential to connect with: Required dropdown for selecting your authenticated Webflow credentials. Site Name or ID: Optional text field to specify the e-commerce site. Leave empty if monitoring a default or single site. Event: Set to "Ecomm New Order"—required to capture new purchase events.

Typical use cases: Send order confirmations through a custom email service like SendGrid or Brevo. Create invoices in accounting software like QuickBooks or Xero. Add customer data to your CRM (HubSpot, Pipedrive) for follow-up sequences. Notify fulfillment teams in Slack with order details and shipping requirements.

When to use it: Essential for any Webflow e-commerce site that needs automated order processing, customer communication, or integration with external fulfillment and accounting systems.

This trigger activates whenever your Webflow site is published, whether manually or through the Designer/Editor. It's valuable for deployment workflows, cache invalidation, and keeping external systems aware of site updates.

Configuration parameters: Credential to connect with: Required dropdown to select your Webflow account for authentication. Site Name or ID: Optional text input to specify which site to monitor. Can be left blank for default site targeting. Event: Set to "Site Publish"—required parameter that defines the triggering event.

Typical use cases: Clear CDN caches (Cloudflare, Fastly) after site updates go live. Notify the development team via Slack when staging sites are published. Log deployment timestamps to a tracking spreadsheet for audit purposes. Trigger screenshot captures of key pages for visual regression testing.

When to use it: Ideal for DevOps workflows, deployment tracking, cache management, and keeping distributed teams informed about site updates.

This trigger fires when any existing item in a Webflow CMS collection is modified. It's crucial for two-way sync setups and ensuring external systems always reflect the latest content changes.

Configuration parameters: Credential to connect with: Required dropdown for selecting your Webflow credentials stored in n8n. Site Name or ID: Required text field where you enter the site name or unique ID to monitor. Event: Set to "Collection Item Updated"—required dropdown selection for this specific trigger.

Typical use cases: Sync updated blog posts to a headless CMS backup or translation platform. Update corresponding records in Airtable when CMS fields change. Trigger re-indexing in Algolia search when product descriptions are modified. Send Slack alerts when high-priority pages are edited by team members.

When to use it: Perfect for maintaining data synchronization between Webflow and external platforms, tracking content changes, and automating update notifications.

This trigger activates instantly when a visitor submits any form on your Webflow site. It's one of the most commonly used triggers for lead capture, contact management, and automated response workflows.

Configuration parameters: Credential to connect with: Required dropdown to authenticate with your Webflow account. Site Name or ID: Required text input specifying the site with forms you want to monitor. Event: Set to "Form Submission"—required to capture form data when visitors submit.

Typical use cases: Add new leads directly to HubSpot, Salesforce, or Pipedrive CRM. Send instant Slack notifications to sales teams when contact forms are submitted. Trigger personalized email sequences through ActiveCampaign. Store form responses in Google Sheets or Airtable for analysis and reporting.

When to use it: Essential for any site using Webflow forms for lead generation, contact requests, newsletter signups, or any data collection that requires immediate processing.

This trigger fires when product inventory levels change in your Webflow e-commerce store. It's vital for stock management, alerting, and maintaining accurate inventory across sales channels.

Configuration parameters: Credential to connect with: Required dropdown for selecting your Webflow credentials. Site Name or ID: Optional text field to specify which e-commerce site to monitor. Event: Set to "Ecomm Inventory Changed"—required to capture stock level modifications.

Typical use cases: Send low-stock alerts to purchasing teams via Slack or email. Sync inventory levels to external platforms like Shopify or Amazon. Automatically pause ad campaigns when products go out of stock. Update inventory tracking spreadsheets in real-time.

When to use it: Critical for e-commerce operations managing inventory across multiple channels or needing proactive stock monitoring to prevent overselling.

This trigger activates when the status or details of an existing order change, such as when an order is fulfilled, refunded, or updated. It keeps your fulfillment and customer service workflows responsive to order lifecycle changes.

Configuration parameters: Credential to connect with: Required dropdown to select your authenticated Webflow account. Site Name or ID: Required text input for specifying the e-commerce site. Event: Set to "Ecomm Order Changed"—required to monitor order status modifications.

Typical use cases: Send shipping confirmation emails when order status changes to "Fulfilled". Update CRM records when orders are refunded or cancelled. Notify customer service teams of order issues requiring attention. Sync order status changes to external ERP or fulfillment systems.

When to use it: Ideal for order lifecycle management, customer communication automation, and keeping fulfillment systems synchronized with Webflow e-commerce.