n8n + Webflow Integration: Automate Your Website Workflows

The n8n Webflow integration turns your Webflow site from a static publishing tool into an automated business engine. Instead of manually copying form responses into spreadsheets, publishing CMS drafts one at a time, or chasing order fulfillment across tabs, you wire it all together in n8n and let workflows handle the repetitive parts. With over 400 integrations available, n8n makes Webflow the front door to your entire tool stack.

Why Automate Webflow with n8n

Webflow is excellent for building production websites without traditional development, but it hits a wall the moment you need backend logic. Form submissions sit in the Webflow dashboard until someone checks them. CMS items need manual publishing. E-commerce orders require separate fulfillment steps.

n8n fills that gap. It connects to Webflow's API and reacts to events — new form submissions, CMS changes, order completions — then routes data to the rest of your stack. Unlike Zapier, where every step costs you an execution, n8n gives you unlimited executions and the ability to branch, loop, and transform data freely.

Common automation scenarios include:

• Sending form leads to HubSpot, Salesforce, or a Google Sheet instantly
• Publishing CMS blog posts from a Notion or Airtable editorial calendar
• Triggering Stripe invoice creation and Slack alerts on new orders
• Backing up your entire CMS collection to a database on a schedule
• Monitoring published pages for SEO issues and broken links

Connecting Webflow to n8n

Before building workflows, you need to set up the Webflow credentials in n8n. Webflow uses OAuth2 for authentication, and n8n handles the full flow.

Step 1: In your Webflow workspace, go to Apps & Integrations → Workspace Applications. Create a new application and note the Client ID and Client Secret.

Step 2: Set the redirect URI to your n8n instance's OAuth callback URL. If you're running on n8nautomation.cloud, this will be https://yourname.n8nautomation.cloud/rest/oauth2-credential/callback.

Step 3: In n8n, go to Credentials → New Credential → Webflow OAuth2 API. Paste your Client ID and Client Secret, then click Connect. Authorize the requested scopes — typically sites:read, forms:read, cms:read, cms:write, and ecommerce:read.

Step 4: Test the connection by adding a Webflow node to a workflow and selecting Get All Sites. If your sites appear, you're good to go.

Workflow 1: Route Form Submissions to Your CRM

This is the most common Webflow automation. A visitor fills out a contact or demo request form, and the data lands in your CRM within seconds — no manual export required.

Nodes in this workflow:

1. Webflow Trigger — Set the event to form_submission. Select your site and the specific form. Each submission fires this trigger with the full field data.
2. Set Node — Map Webflow's form field names to your CRM's expected fields. Webflow forms return field data keyed by the field name you set in the designer (e.g., Email, Company, Message). Normalize these here.
3. IF Node — Route leads based on criteria. For example, if the Company Size field is over 50 employees, route to a sales rep; otherwise, add to a nurture sequence.
4. HubSpot Node (or Salesforce, Pipedrive) — Use the Create/Update Contact operation. Map email, name, company, and any custom properties. Enable Update if exists so repeat submissions update the record rather than creating duplicates.
5. Slack Node — Post a notification to your #new-leads channel with the contact name, company, and a direct link to the CRM record.

This five-node workflow replaces the manual process of checking Webflow forms, copying data, and pasting it into your CRM — a task that typically eats 15-30 minutes per day for active sites.

Workflow 2: Automated CMS Publishing Pipeline

If your team manages content in Notion, Airtable, or Google Docs before publishing to Webflow, this workflow eliminates the copy-paste step entirely.

Nodes in this workflow:

1. Schedule Trigger — Run every 30 minutes (or use a Notion/Airtable trigger for instant publishing).
2. Notion Node — Query your editorial database for items where the Status property equals Ready to Publish. Use a filter to only grab unpublished items.
3. Markdown Node — Convert Notion's rich text blocks to HTML. Use the Markdown to HTML operation if your content comes as Markdown, or the HTML node for direct conversion.
4. HTTP Request Node — Call Webflow's CMS API (POST /v2/collections/{collection_id}/items) with the title, slug, body HTML, featured image URL, meta description, and any other CMS fields. Set isArchived to false and isDraft to false to publish immediately.
5. Notion Node — Update the original item's Status to Published and stamp the publish date.

Workflow 3: E-Commerce Order Processing

Webflow E-Commerce handles checkout, but everything after the sale — fulfillment, accounting, customer communication — needs external tools. n8n bridges that gap.

Nodes in this workflow:

1. Webflow Trigger — Set the event to ecomm_new_order. This fires when a customer completes checkout, delivering the full order object including line items, shipping address, and payment status.
2. Switch Node — Branch based on order properties. Digital products go one route (email delivery), physical products go another (fulfillment), and high-value orders (over $500) get flagged for manual review.
3. Google Sheets Node — Append the order to your orders spreadsheet with columns for order ID, customer email, items, total, and timestamp. This gives your operations team a simple dashboard.
4. SendGrid Node — Send a personalized order confirmation email using a dynamic template. Pass the customer name, order items, and estimated delivery date as template variables.
5. Slack Node — Alert your fulfillment team in #orders with the shipping address and items to pack.

For physical products, you can extend this with a ShipStation or EasyPost node to automatically generate shipping labels and tracking numbers, then update the Webflow order status via the API.

Workflow 4: Scheduled CMS Backups

Webflow doesn't offer native CMS backups beyond site-level snapshots. If someone accidentally deletes a CMS collection item, that content is gone. This workflow creates automatic backups you control.

Nodes in this workflow:

1. Schedule Trigger — Run daily at 2 AM (or whatever off-peak time works for your team).
2. HTTP Request Node — Call GET /v2/collections/{collection_id}/items for each CMS collection. Use pagination to fetch all items (Webflow returns max 100 per page).
3. Code Node — Combine all items into a single JSON array. Add a timestamp and collection name as metadata.
4. Google Drive Node (or S3, Dropbox) — Upload the JSON file to a /webflow-backups/ folder with a filename like blog-posts-2026-04-11.json.
5. IF Node — Check if the item count differs from yesterday's backup by more than 10%. If so, fire a Slack alert — unexpected drops might indicate accidental bulk deletion.

Running this on a managed n8n instance at n8nautomation.cloud means your backup schedule runs reliably without you babysitting a server. Scheduled triggers just work — no cron job configuration or uptime monitoring needed.

Workflow 5: SEO Content Monitoring and Alerts

This workflow watches your Webflow CMS for SEO issues before they hurt your rankings — missing meta descriptions, duplicate titles, or broken image links.

Nodes in this workflow:

1. Schedule Trigger — Run weekly on Monday mornings.
2. HTTP Request Node — Fetch all items from your blog or pages CMS collection via Webflow's API.
3. Code Node — Loop through items and flag issues: meta descriptions under 120 characters or over 160, missing featured images, titles longer than 60 characters, slugs containing uppercase characters or special characters, and empty body content.
4. IF Node — Filter to only items with at least one issue.
5. Gmail Node — Send a weekly SEO audit email to your content team with a table listing each item, its URL, and the specific issues found.

You can extend this with an HTTP Request node that actually fetches each published URL and checks for broken links or missing Open Graph tags. Pair it with the HTML Extract node to parse the live page and compare it against what the CMS says should be there.

Each of these workflows takes 15-30 minutes to build in n8n's visual editor, and once active, they run continuously without intervention. If you'd rather skip the server setup entirely and start building immediately, n8nautomation.cloud gives you a dedicated n8n instance with Webflow credentials ready to configure in under two minutes — starting at $15/month with automatic backups and guaranteed uptime.