Pipe dream

Forms store submissions and send notification emails. But forms alone cannot transform data for a CRM or support desk, nor can they route it into a spreadsheet. The same gap applies to the Webflow CMS and e-commerce events. A separate system such as Pipedream has to receive the payload and act on it.

A form submission can open a Zendesk ticket. After a Contentful publish, Pipedream can create a matching Webflow CMS item; inventory changes can update Google Merchant Center products. Pipedream's Webflow connector authenticates via OAuth and calls the Webflow Data API v2. There are no servers to deploy and no tokens to refresh by hand.

Marketing and RevOps teams use the integration to route and enrich leads in real time. Content teams and agencies use it to keep CMS collections in sync with sources like Airtable and Google Sheets. E-commerce operators wire order and inventory events into accounting and fulfillment tools. Developers get code steps in Node.js or Python when the pre-built components run out.

How to integrate Pipedream with Webflow

What is Pipedream? Pipedream is a workflow automation platform for connecting APIs, AI agents, databases, and services. It integrates 3,000+ apps with managed authentication and supports code steps in Node.js, Python, Go, and Bash. Workflows run on Pipedream's managed infrastructure, and connected accounts hold the OAuth credentials for your Webflow authorization.

Teams pair the two when a Webflow site supplies leads and orders or reports content changes. Other systems then need to react in real time. Pipedream is itself a full automation platform, so the connection is direct. No third-party bridge sits between the two tools.

• The Pipedream connector provides pre-built triggers for Webflow form submissions, CMS changes, site publishes, inventory changes, and e-commerce orders, plus actions for CMS, site, and order data, including a Publish Site action. Live CMS writes and self-validated signed webhooks are the parts that still call for the API or a code step.
• Webflow webhooks and Code Embed let you post site events to Pipedream HTTP endpoints and display workflow data on your pages.
• The Webflow and Pipedream APIs give you full control over site publishing, live CMS writes, and signed webhooks, but require writing code.

Most implementations combine two or more of these methods depending on the complexity of the setup.

Install the Pipedream app

The Pipedream app in the Webflow Marketplace carries the Approved by Webflow label and connects over OAuth. It requests read access to user information and read/write access to supported site resources. The same grant covers forms and submissions, the e-commerce store, assets, CMS data, and page data. You connect the account from Pipedream's workflow builder, and the pre-built components require no code. Pipedream stores your tokens and refreshes them automatically.

To set up the integration:

1. In Pipedream's workflow builder, add a trigger or action step and search for Webflow.
2. Click Connect Webflow, sign in, and grant permission in the popup.
3. Select your site, and for CMS steps, select a Collection.
4. Configure the step's props and deploy the workflow.
5. Send a test event to validate the setup, then turn on the trigger.

The connector ships with pre-built components covering the most common jobs:

• Trigger workflows on form submissions with New Form Submission.
• Trigger on content changes with New Collection Item Created, Collection Item Updated, and Collection Item Deleted.
• Trigger on Site Published, E-commerce Inventory Updated, New E-commerce Order, and E-commerce Order Updated events.
• Manage CMS data with Create Collection Item, Delete Collection Item, Get Collection, and Get Collection Item.
• Manage store and site data with Fulfill Order, Update Order, List Orders, Get Site, and Publish Site.

The Create Collection Item action creates staged draft items, not live ones. The API section below covers the extra call that publishes them.

Connect Webflow webhooks and Code Embed to Pipedream endpoints

Every Pipedream workflow can start from an HTTP / Webhook trigger, which generates a unique URL on *.m.pipedream.net. Your site posts form submissions and site events to that URL, with no code on either side. Pipedream parses incoming JSON automatically, and it lands at steps.trigger.event. You can map fields into downstream actions with {{steps.trigger.event.body.field}} expressions. This path suits builders who want a working pipeline without touching the API.

Send form submissions to a Pipedream URL

A webhook destination adds Pipedream on top of the built-in form handling. Submissions still save to the site and notification emails still send.

To route a form to Pipedream:

1. In Pipedream, create a workflow with the HTTP / Webhook Requests trigger and click Save and continue to accept the defaults.
2. Copy the generated URL.
3. In Webflow, select the form, open the Settings panel, and click the add icon next to Send to.
4. Choose Webhook, paste the Pipedream URL, and click Save.
5. Copy the one-time Secret key immediately; it is not shown again.

Do not point the form's custom action at Pipedream instead. A custom action bypasses the built-in form handling entirely. Submissions are not stored, notification emails do not send, and reCAPTCHA stops working, per the forms documentation.

Create site-level webhooks in Site settings

Site-level webhooks cover form submissions, site publishes, and CMS item created, updated, and deleted events. Order events (ecomm_new_order, ecomm_order_changed) are registered through the API, as covered below. Site-level form_submission webhooks fire for all forms by default. To target one form, pass the filter parameter documented for the Create Webhook API endpoint. The form's Send to > Webhook option routes one form's submissions. The dashboard route needs no code, but it omits the signature headers.

To add a site-level webhook:

1. Go to Site settings > Apps & integrations > Webhooks and click Add webhook.
2. Choose a trigger type, such as Form submission or Site publish.
3. Choose API version v2. The v1 API was deprecated on March 31, 2025, and you can no longer create v1 webhooks manually.
4. Paste your Pipedream HTTP trigger URL and save.

Webhooks created here do not include the headers needed to validate request signatures. If you need cryptographic proof that a request came from Webflow, register the webhook through the API instead.

Display workflow data on your site with Code Embed

The connection also runs in reverse. A Code Embed element can fetch data from a Pipedream HTTP endpoint client-side. It then renders that data on the page. Pipedream endpoints respond with Access-Control-Allow-Origin: *, so browser requests work without proxy configuration. HTTP triggers are public by default. Add a custom token or OAuth authorization on the trigger before you expose the URL in page code. Custom JavaScript on the page can display ConvertKit subscriber counts fetched by a Pipedream workflow on the backend.

To add the embed:

1. Build a Pipedream workflow with an HTTP trigger that responds with your data, using the no-code Return HTTP response action.
2. Open the Add panel in Webflow and drag a Code Embed element onto the canvas.
3. Paste a script that fetches your Pipedream endpoint URL and writes the result into the page, then save and publish.

Code Embed supports HTML, CSS in <style> tags, and JavaScript in <script> tags. Each embed caps at 50,000 characters. Access requires a Core, Growth, Agency, or Freelancer Workspace, or an active Site plan.

For scripts that should run on every page, add them in Site settings > Custom code instead. See Custom code in head and body tags for where head and footer code loads.

Build with the Webflow and Pipedream APIs

Direct API calls cover what the pre-built components do not. They can publish sites and create live CMS items. They also register signed webhooks. Code steps run on Pipedream's infrastructure in Node.js or Python, so there is no server to host. Inside a Node.js step, the managed Webflow token is available at this.webflow.$auth.oauth_access_token. It passes as a Bearer header on every request.

• Webflow's Data API v2 handles CMS collections and items, form submissions, orders, and site publishing at https://api.webflow.com/v2.
• Webflow webhooks push real-time events to Pipedream HTTP triggers across 14 trigger types.
• Pipedream's REST API deploys and manages your Webflow event sources and workflows across sites at https://api.pipedream.com/v1.

The sub-methods below are the three API tasks that come up most in Webflow workflows.

Publish CMS changes live

The connector's Create Collection Item action stages drafts. Pipelines that need immediate publication call the live-item endpoints instead, through an HTTP Request action or a code step.

• Create items that publish on creation with POST https://api.webflow.com/v2/collections/{collection_id}/items/live. That call requires the cms:write scope and returns 202.
• Publish existing staged items with POST https://api.webflow.com/v2/collections/{collection_id}/items/publish.
• For batch work, POST /v2/collections/{collection_id}/items/bulk creates up to 100 staged items per request. PATCH /v2/collections/{collection_id}/items/live updates up to 100 published items.

DELETE /v2/collections/{collection_id}/items/live unpublishes items by setting isDraft: true, which supports takedown workflows.

Register webhooks with signature validation

Only webhooks created through the API include the x-webflow-timestamp and x-webflow-signature headers. If your workflow must reject spoofed requests, skip the dashboard and register the webhook programmatically.

To set it up:

1. Create a Pipedream workflow with an HTTP trigger and copy its URL.
2. Register the webhook with POST https://api.webflow.com/v2/sites/{site_id}/webhooks and pass a triggerType such as form_submission and the Pipedream URL. This call requires the sites:write scope. The form_submission type accepts an optional filter parameter to target one form by name.
3. In a code step, concatenate the timestamp and stringified request body with a colon. Compute an HMAC-SHA256 hash using the webhook secret as the key and compare it to x-webflow-signature. Reject timestamps older than 5 minutes.

A receiver that does not return HTTP 200 gets retried, and repeated failures deactivate the webhook. This method also covers ecomm_new_order and ecomm_order_changed. The connector already ships New E-commerce Order and E-commerce Order Updated triggers, so take the API route for these events only when you need to validate the signature yourself.

Publish your site from a workflow

The connector's Publish Site action republishes without code. Calling the publish endpoint directly gives the same result with explicit control over which custom domains publish and over single-page publishing.

To publish programmatically:

1. Add a Node.js code step with your connected Webflow account.
2. Call the publish endpoint with the managed token, for example:CODEBLOCK_0
3. Include at least one of customDomains (an array of domain IDs) or publishToWebflowSubdomain in the body. Add pageId to publish a single page. A 202 response means the publish was queued.

Combine this step with the staged-item endpoints above to batch a set of CMS updates. Republish once at the end.

What can you build with the Pipedream Webflow integration?

Integrating Pipedream with Webflow lets you route form, CMS, and e-commerce events into thousands of connected apps without building or hosting a webhook receiver.

• Lead capture with CRM routing: The New Form Submission trigger sends each lead to Zendesk, Airtable, or any of the 3,000+ connected apps. Pipedream ships pre-built Webflow-to-Airtable templates for a no-code version, and further examples cover Zoom registrants and Discord messages..
• CMS sync pipelines: External content sources feed the Webflow CMS automatically. Publishing in Contentful creates the matching Webflow item. A resource directory can refresh from Airtable or Google Sheets on a schedule. A Collection Item Created trigger can create a matching HubSpot company.
• E-commerce back office: Order data flows into QuickBooks for invoicing. The E-commerce Inventory Updated trigger keeps Google Merchant Center product listings in sync with stock levels.
• Post-publish automation: The Site Published trigger chains downstream steps after every publish. Examples include a Postmark email, a Slack notification, a CDN cache purge, or an analytics ping.

If you need more control over when CMS items go live, the API integration path covers those cases with full flexibility.