How to build a user dashboard with login and booking in Webflow

Webflow Cloud can host a Next.js booking dashboard under the same site path as a Webflow marketing site, avoiding separate subdomains and allowing shared navigation and login behavior. The implementation uses a Next.js 15 App Router project, since Webflow Cloud requires Edge-compatible `middleware.ts` and does not support the newer Next.js 16 proxy model or Edge runtime declarations in Route Handlers. A signed, HTTP-only session cookie created after authentication is verified by both middleware and booking API routes, ensuring that dashboard access and booking data are consistently tied to the authenticated user ID. The guide describes connecting an identity endpoint and protected booking service through server-side Route Handlers, keeping credentials and API keys out of the browser, while client-side requests must include the Webflow Cloud mount path through `NEXT_PUBLIC_BASE_PATH`. Deployment requires environment variables for session signing, identity and booking endpoints, a booking API key, and the mount path, with production testing focused on redirects, cookie verification, and correctly prefixed API calls. It also identifies common failures involving renamed middleware, unsupported runtime settings, missing base paths, and inconsistent secrets, while noting that rate limiting, CSRF or origin checks for state-changing routes, brute-force protection, and upstream spend caps remain necessary production considerations.

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.