Webflow apps · Project scope

Webflow extensions built around real workflows.

Webflow teams extend the CMS with discovery, memberships, structured data, directories, and business automation. Review each opportunity by workflow, delivery model, compatibility boundary, and support path.

Explore extensions Request a custom build

Webflow extension directory

Choose the workflow,
then verify the fit.

Each page separates the desired capability from what is actually available. A custom or project scope is not presented as an instant download.

01

Webflow CMS search and filter app

Collection search, multi-filter navigation, sorting, pagination, saved items, and fast directory browsing.

5K+ installs on leader Built to order
View extension
02

Webflow membership app

Authentication, gated content, Stripe plans, member profiles, permissions, and self-service billing.

Established app category Built to order
View extension
03

Webflow CMS maps and directory app

CMS-connected maps, distance search, location filters, profiles, favorites, and directory workflows.

Marketplace demand Built to order
View extension
04

Webflow schema and SEO app

CMS-mapped structured data, validation, page templates, redirects, and repeatable SEO controls.

1K+ installs on leader Built to order
View extension
05

Webflow forms and CRM automation

Qualified forms, routing, enrichment, CRM synchronization, alerts, and reliable webhook delivery.

Core integration need Built to order
View extension

Demand labels are directional market evidence captured on October 27, 2026. They do not claim Growtype sales, ranking outcomes, or a released marketplace product.

Webflow delivery

Quality before scale

Programmatic pages should answer a real buying question.

This directory is organized around distinct Webflow workflows. Every page carries its own scope, implementation boundary, compatibility notes, verification steps, and next action.

  • Distinct intentOne workflow and one primary decision per page.
  • Evidence boundaryCapabilities, opportunities, and released packages are labeled separately.
  • Useful next stepCompatibility and scope are confirmed before implementation or payment.

Webflow extension questions

Know the delivery boundary.

Are these ready-made Webflow apps?

Each page states its delivery model. Items marked as a project or custom scope are implementation opportunities, not instant marketplace downloads. Compatibility, inclusions, ownership, price, and delivery are confirmed before work begins.

Can Growtype build a different Webflow extension?

Yes. Share the workflow, affected customer journey, connected systems, and operating constraints. Growtype will review the supported platform APIs and confirm whether the request can be delivered responsibly.

What is checked before delivery?

The agreed workflow, permissions, data ownership, API and webhook behavior, responsive and accessible states, failure recovery, analytics, performance, and release plan are checked in proportion to risk.

Need a different Webflow workflow?

Build the missing layer.

Share the customer journey, connected systems, and operating constraints. Growtype will confirm platform fit, scope, ownership, price, and delivery before work begins.

Request a custom build