Skip to content
MoveWorkflows

Pipedream Webflow steps in n8n

Updated 2026-10-21 · 3 min read · n8n: Webflow (Native n8n node)

Webflow workflows on Pipedream do content and lead handling: form submissions go to a CRM or Slack, rows from Airtable or Sheets become CMS items, a publish pings the team. n8n has a native Webflow node for CMS items and a Webflow Trigger for site events.

The n8n side

Webflow node (n8n-nodes-base.webflow), resource Item: Create, Delete, Get, Get Many, Update. You pick site and collection from lists, and field values are entered per field slug.

Webflow Trigger (webhook, per site), events:

  • Form Submission
  • Site Publish
  • Collection Item Created / Updated / Deleted
  • Ecomm New Order, Ecomm Order Changed, Ecomm Inventory Changed

What maps where

Pipedream (app webflow) In n8n Status
Create Collection Item Item → Create manual
Update Collection Item Item → Update manual
Get Collection Item, List Collection Items Item → Get / Get Many manual
Delete Collection Item Item → Delete manual
Publish Site HTTP Request → POST /v2/sites/{id}/publish manual
List Orders, Fulfill Order HTTP Request → orders endpoints manual
New Form Submission Webflow Trigger, Form Submission manual
New Collection Item Created, Collection Item Updated Webflow Trigger, Collection Item events manual
New E-commerce Order Webflow Trigger, Ecomm New Order manual
Site Published Webflow Trigger, Site Publish manual

Webflow is not in the converter's mapped list. Each action arrives as a placeholder with its props (site ID, collection ID, fieldData) in a comment, and the trigger as a Manual Trigger naming the source.

Webflow credentials in n8n

  • OAuth2: a Webflow app; one credential can cover several sites you authorize. The current node and trigger versions accept only this credential.
  • API access token (per site, Site settings → Apps & integrations): the n8n docs still list it, but in the current source it works only with the older v1 node and trigger, or in HTTP Request calls.

Keep Legacy off unless the workflow still calls Data API v1.

Typical migration: form to HubSpot

Pipedream: Webflow New Form Submission → HubSpot create contact → Slack message. n8n: Webflow Trigger (site, Form Submission) → If (form name = "Contact") → HubSpot → Contact → Create or Update → Slack → Message → Send. Filter by form name: the trigger fires for every form on the site.

Webflow migration pitfalls

  • Rate limits. 60 requests per minute on Starter and Basic site plans, 120 on CMS, eCommerce and Business. Bulk item imports need batching with a Wait node.
  • Draft vs live. Items created via API are staged until published (or created as live items via the live endpoint). Add a Publish Site call if the page must update.
  • Field slugs. The API uses slugs (post-body), not display names; option and reference fields need item or option IDs.
  • Old webhooks. Pipedream's sources registered webhooks on the site; remove them in site settings after the switch.

How to move your Webflow workflows

  1. Export from Pipedream.
  2. Upload on /convert; the free report lists every Webflow step with its props.
  3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

See the Pipedream to n8n guide. Related: WordPress, Airtable, HubSpot.

FAQ

Which Webflow events does the n8n trigger support?
Form Submission, Site Publish, Collection Item Created, Updated and Deleted, and the ecommerce events New Order, Order Changed and Inventory Changed, per site.
What does the Webflow node cover?
The Item resource (CMS collection items): Create, Delete, Get, Get Many, Update. Publishing a site, orders and fulfilment go through HTTP Request.
Do I need the Legacy toggle?
Only if you still use Webflow's deprecated Data API v1. The current Webflow node and trigger (v2) accept only OAuth2; keep Legacy off.
Do Webflow steps convert automatically?
No. They arrive as placeholders with their props (site, collection, field data), and the trigger as a Manual Trigger naming the source.

Related

Sources