How to send Webflow form leads to Pipedrive as contacts with Webflow Cloud

A Webflow Cloud integration can send Webflow form submissions directly to Pipedrive through a Next.js Route Handler, avoiding manual data entry and third-party automation services while keeping the Pipedrive API token off public page code. The setup requires a Webflow form with consistent field names, a Webflow Cloud environment and mount path, a Pipedrive personal API token and company domain, a Next.js 15 App Router project using npm, and a shared secret included in the webhook URL. The handler validates the secret, reads Webflow’s payload fields, creates a Pipedrive person through the v2 API with properly structured email and phone arrays, and uses distinct status codes to identify authorization, configuration, validation, routing, and Pipedrive connectivity errors. Deployment involves storing the token and secret as Webflow environment secrets, testing the mounted endpoint with curl, and configuring a Webflow Form submission webhook to call the full URL including the mount path. Common problems include unsupported Next.js edge-runtime declarations, omitted mount paths, missing deployed environment variables, and mismatched secrets, while the basic handler can later be expanded to prevent duplicates or create associated Pipedrive leads and deals.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.