Pipedream

How to integrate Pipedream with Webflow

There are four ways to wire Pipedream into a Webflow site, and which one you pick depends on how much of the work an agent should do for you. Pointing an AI client at the MCP servers on both sides lets you describe an automation in plain language and have it read and write real site data. The Pipedream app from the Webflow Apps marketplace gives you native triggers and actions with no code. Webflow webhooks cover event types the app does not expose natively, by posting to a Pipedream HTTP endpoint. For anything past that, the Webflow Data API plus custom Node.js or Python inside a workflow step handles real-time CMS sync and order routing.

What is Pipedream? Pipedream is a serverless automation platform aimed at developers, with more than 3,000 app connectors and first-class support for writing code inside a workflow. It was acquired by Workday and still ships and sells under the Pipedream name. Because it is itself an automation platform, it sits in the same slot as Zapier, Make, and n8n rather than connecting through them.

Connect Webflow and Pipedream through MCP

If your automation work already starts in an AI client, connect the Webflow MCP server first and let the agent handle the Webflow half directly. It exposes tools for building and managing sites and for analyzing traffic and engagement, alongside governance controls that cover per-site agent instructions, permissions and roles, and the site activity log. It is included on every Webflow Site plan, starting with the free Starter tier, so there is no paid gate to clear before trying it.

Pipedream runs its own MCP offering on the other side. You add one Pipedream MCP server to your client, sign in, then choose which of its connected apps to expose as tools, so an agent can call Slack, Google Sheets, a CRM, or a database through Pipedream's managed authentication instead of you storing and refreshing tokens yourself. Browse what is available at Pipedream's MCP catalog.

In practice the two servers do different jobs and you want both. Webflow's server is where an agent reads your collections and publishes your edits. Pipedream's is where the same agent reaches the systems Webflow does not know about. Keep the scoping deliberate: enable only the apps a given agent needs, since every enabled app is a credential that agent can now spend.

Use the Pipedream app

Install the Pipedream app from the Webflow Apps marketplace, authorize your Webflow account through OAuth, and build workflows from pre-built triggers and actions. Webflow lists the app as reviewed and it supports enhanced security and management features, so it can be governed alongside your other installed apps.

Eight triggers start a workflow, and each one registers a real Webflow webhook rather than polling:

• New Form Submission: Runs a workflow the moment a visitor submits a Webflow form, with the field data delivered as key-value pairs.
• New Collection Item Created: Fires when a CMS item is added to a Collection list, which is the usual hook for content sync.
• Collection Item Updated: Fires when an existing CMS item changes, so you can push edits out to a search index or a downstream store.
• Collection Item Deleted: Fires when a CMS item is removed, which is what keeps an external mirror from drifting out of date.
• New E-commerce Order: Fires on each new order, carrying customer details, line items, and totals into the workflow.
• E-commerce Order Updated: Fires when an order changes state, covering fulfilment and refund transitions.
• E-commerce Inventory Updated: Fires when a stock level moves, which is how you keep a warehouse system and the storefront agreeing.
• Site Published: Fires on publish, useful for cache purges, sitemap pings, or a build notification to your team.

That list is worth checking against older write-ups, which commonly describe only four triggers and tell you to fall back to raw webhooks for site publishes and inventory changes. Those two are now native.

Eighteen actions cover the write side, grouped by what they touch:

• Collection items: Create Collection Item, Update Collection Item, Get Collection Item, List Collection Items, and Delete Collection Item handle the Webflow CMS read and write path.
• Collections and sites: Get Collection, List Collections, Get Site, List Sites, and Publish Site let a workflow discover structure and then push changes live.
• Orders: Get Order, List Orders, Fulfill Order, Unfulfill Order, Refund Order, and Update Order cover the full order lifecycle from a workflow.
• Inventory: Get Item Inventory and Update Item Inventory read and set stock levels on an e-commerce item.

Pick a trigger, choose a site and collection from the dropdowns, then chain actions from Pipedream's connector library. One detail matters more than the feature list: the components are built on Webflow's version 2 API client, not the retired version 1 endpoints, so item payloads use the current fieldData shape and the id field rather than the old flat fields and _id. You can read the component source to confirm what a given action sends before you depend on it.

Configure Webflow webhooks

Use raw webhooks for the event types the app does not expose as native triggers, such as page creation, page metadata changes, collection item unpublished, and new comments. Create a Pipedream workflow with an HTTP trigger, copy the endpoint URL it generates, then register that URL in Webflow.

In your site settings, open Apps & Integrations, find the Webhooks section, add a webhook, choose the event, and paste the Pipedream URL. This takes no code at all.

You can also add client-side events that Webflow does not emit on its own. Drop a Code Embed element onto a page with a small script that sends a fetch request to the same Pipedream endpoint when a visitor clicks a button or reaches a scroll depth. Escape any markup you paste in, and keep the endpoint URL out of code that also carries a secret, since anything in a Code Embed is public.

Build with the Webflow Data API in Pipedream

Write custom Node.js or Python inside a workflow step when the pre-built actions run out, with access to npm and PyPI packages. This is the developer-level path, and it is where multi-step API orchestration and integration with proprietary systems live.

Automate CMS content sync

Keep CMS collections aligned with an external source of truth through scheduled polling or webhook-driven events. These are the endpoints you will reach for most:

• Create items: POST /v2/collections/{collection_id}/items adds staged items to a collection.
• Update items: PATCH /v2/collections/{collection_id}/items updates existing items, with the item IDs passed in the request body.
• Publish items: POST /v2/collections/{collection_id}/items/publish takes an array of item IDs and pushes staged items live.
• List items: GET /v2/collections/{collection_id}/items pages through a collection, and the list items endpoint caps each request at 100 items.

For real-time sync rather than polling, have Webflow fire collection_item_created, collection_item_changed, or collection_item_deleted at a Pipedream HTTP trigger. Build error handling into the workflow, because Webflow deactivates a webhook that keeps failing.

Process form submissions with custom logic

The form_submission webhook plus the Forms endpoints let you validate and enrich a submission before routing it, instead of forwarding it untouched. The payload carries the form field data as key-value pairs plus the form name and a timestamp, so a workflow can parse it, apply your validation rules, then open a CRM record or a support ticket. Two endpoints do the reading: GET /v2/sites/{site_id}/forms returns the forms on a site with their field definitions, and GET /v2/sites/{site_id}/form_submissions/{form_submission_id} fetches one submission by ID.

Validate in the workflow rather than client-side only, since a webhook payload reflects whatever was posted to Webflow.

Route e-commerce orders to external systems

Subscribe to ecomm_new_order and ecomm_order_changed to get order events at your Pipedream endpoint, then extract the details and forward them to accounting or fulfilment. The relevant reads are:

• Get order: GET /v2/sites/{site_id}/orders/{order_id} returns customer info, line items, payment status, and order totals.
• List orders: GET /v2/sites/{site_id}/orders pages through orders and supports filtering by status.
• List products: GET /v2/sites/{site_id}/products returns the product catalogue with its SKUs.
• Write back: the Fulfill Order and Update Order actions let the same workflow mark an order fulfilled once your warehouse system confirms it.

Make the workflow idempotent on order ID. Webflow may deliver the same event more than once on retry, and an invoice created twice is a support ticket.

Webhook security and authentication

Webflow supports OAuth 2.0 for apps acting on behalf of a user and site tokens for site-scoped integrations, and the Pipedream app handles the OAuth exchange for you when you connect an account. That means the credential lives in Pipedream's account store rather than in a workflow step, which is where you want it when several people can edit the workflow.

For inbound requests, Webflow sends x-webflow-timestamp and x-webflow-signature headers on webhooks that were created through the API, and you validate the HMAC signature in your workflow before acting on the payload. Webhooks created through the Webflow dashboard do not carry those headers, so create them programmatically whenever the payload triggers something you cannot take back.

What you can build with the Pipedream Webflow integration

Pipedream sits between your Webflow site and everything else as a serverless layer you can configure visually or drop into code, which means most of these start as a trigger and three steps rather than a project. Here is what teams put together most often:

• Automated lead routing: Catch a form submission, validate and enrich the record against a third-party service, then open a deal in your CRM without anyone rekeying it.
• Self-updating resource directory: Sync collection items from an Airtable base or a spreadsheet on a schedule, so a partner directory or job board stays current with no manual CMS edits.
• Order operations feed: Route new orders to accounting for invoicing and to Slack for the team, giving operations a live view of purchases without logging into separate tools.
• Content publishing pipeline: Connect a headless CMS such as Contentful so publishing an article there creates and publishes the matching Webflow CMS item.
• Publish-time housekeeping: Use the Site Published trigger to purge a CDN cache and ping search engines the moment a site goes live.

All five lean on the same CMS endpoints, so start with our Webflow CMS API guide before you wire up the first workflow.