--- title: "Webflow Integration" description: "Automate CMS content and e-commerce workflows. 3 triggers fire on form submissions and order events. 16 actions manage collections, items, fields, and publishing." url: https://flowrunner.ai/integrations/webflow date_modified: 2026-08-01T02:40:32-07:00 --- # Webflow [Web Platform](https://flowrunner.ai/integrations/category/developer-infrastructure) Automate CMS content and e-commerce workflows. 3 triggers fire on form submissions and order events. 16 actions manage collections, items, fields, and publishing. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 3 triggers · 16 actions · OAuth · available [Webflow website](https://webflow.com/) · Capability data verified 2026-08-11 1. On Form Submit fires from Webflow contact form 2. Agent extracts name, company, email, and inquiry data from submission 3. Agent creates contact in HubSpot and assigns to correct sales territory 4. Agent adds lead to appropriate Instantly outreach sequence 5. Sales rep receives Slack notification with lead details within seconds 6. Site publish after content changes requires marketing manager approval via Slack ## What This Integration Enables Webflow integration gives agents access to the CMS layer and e-commerce event stream. Agents create and manage collection items to keep dynamic content current, process inbound form submissions as workflow triggers, and react to order creation and updates with downstream processing. ### Without FlowRunner **Manual lead routing**: Web form submissions emailed to a shared inbox and routed by hand **Delayed CRM entry**: Leads sit in email until someone manually creates the HubSpot record **Static case study library**: New case studies require marketing staff to log into Webflow and create items manually ### With FlowRunner **Lead in CRM within seconds**: Every Webflow form submission creates an attributed HubSpot contact automatically **Full order routing on purchase**: Webflow order triggers ShipBob, Stripe, email, and QuickBooks simultaneously **CMS updated from HubSpot data**: Case studies published to Webflow the moment HubSpot marks them ready ## Use Case Scenarios ### Lead Form to CRM On Form Submit fires from the Webflow contact form. The agent extracts the submission data, creates a contact in HubSpot, assigns the lead to the correct sales territory, and sends a Slack notification to the assigned rep. The lead is in the CRM and the rep is notified within seconds of the form submission. ### Order Fulfillment Routing On New Order fires for a Webflow store. The agent creates a fulfillment order in ShipBob with the customer's shipping address and items. It creates the customer in Stripe and charges the payment. It sends a confirmation email via MailerSend. It records the sale in QuickBooks. The order flows through every connected system without manual processing. ### Dynamic Content Sync A marketing team manages case study data in HubSpot. When a case study record is marked Published, the agent retrieves the content, creates a Collection Item in the Webflow case studies collection with the title, summary, quote, and results data, and publishes the site. The new case study is live on the website without anyone opening Webflow. ## Human-in-Loop Highlight Before publishing a Webflow site after content changes, the agent does not publish automatically for content that affects critical pages. It routes a review step via Slack: "I have updated \[N\] collection items and the site is ready to publish. Preview the changes here: \[staging URL\]. Approve publish or request changes?" The marketing manager previews and approves. The publish happens with human sign-off. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 15 actions ### Collection Management 6 - **Create Collection** Creates a new CMS collection in Webflow. Used in site structure setup and new content category workflows. - **Delete Collection** Removes a collection. Used in content governance workflows. - **Get Collection Schema Info** Retrieves the field definitions for a collection. Used when agents need to understand the data structure before writing items. - **Create Collection Field** Adds a new field to an existing collection. Used when content schemas evolve and new fields need to be added programmatically. - **Update Collection Field** Modifies an existing field definition. - **Delete Collection Field** Removes a field from a collection. ### Collection Item Operations 4 - **Create Collection Item** Creates a new item in a CMS collection. Used when operational events should generate public-facing content: a new case study in HubSpot triggers creation of the case study page in Webflow, a new product in the ERP creates the product page in Webflow. - **Update Collection Item** Modifies an existing CMS item. Used to keep content current: pricing changes in the ERP update the product page, a deal stage change updates a customer showcase listing. - **Delete Collection Item** Removes a CMS item. Used in content governance and archival workflows. - **Get Collection Items** Returns items in a collection. Used when agents need to audit or process existing content. ### Site Operations 3 - **Get Site Details** Returns site metadata and configuration. Used in administrative and monitoring workflows. - **Get Site Domains** Returns the domains configured for a site. Used in environment management workflows. - **Publish Site** Triggers a site publish to make changes live. Used after content updates are complete and reviewed. ### Form Data 2 - **Get Form Submissions** Returns submissions from a Webflow form. Used in polling-based intake workflows where form data needs to be processed periodically. - **Delete Form Submission** Removes a form submission. Used in cleanup workflows after data has been processed. ## Triggers 3 triggers ### Event Triggers 3 - **On Form Submit** Fires when a visitor submits a Webflow form. Used to kick off lead capture, inquiry routing, and application processing workflows the moment a form is submitted. - **On New Order** Fires when a new e-commerce order is placed in Webflow. Used to trigger order fulfillment, inventory updates, and customer notification workflows immediately after purchase. - **On Order Updated** Fires when an order status changes: fulfilled, refunded, canceled. Used to trigger downstream processing: fulfillment confirmation emails, inventory adjustments, ERP updates. ## Frequently Asked Questions ### What can FlowRunner do with Webflow? FlowRunner agents can run Get Collection Schema Info, Get Site Details, and Get Site Domains in Webflow, plus 13 more actions. ### Does connecting Webflow to FlowRunner require OAuth? Yes. Webflow connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Webflow trigger a FlowRunner workflow automatically? Yes. Webflow supports 3 triggers that can start a FlowRunner workflow automatically. **Work at Webflow?** This integration exposes Webflow to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/webflow. Site index: https://flowrunner.ai/llms.txt