FREEFirst project with us? Your landing page design is on the house.See the offer

Webflow

A custom calculator tool on Webflow Cloud, under your own domain

How to run a custom calculator on its own URL under your Webflow domain: hosted on Webflow Cloud, deployed from GitHub, leads saved to the CMS, admin panel.

By Abdul QuadirUpdated 2026-11-078 min read
TL;DR
  • Build the tool as a small app in a GitHub repository and attach it to your Webflow site on a path such as /calculator.
  • Webflow Cloud deploys the app when the repository changes, so updates ship with a push.
  • A server route saves each submission as a CMS item through the Webflow API, with the token kept as a secret.
  • Items created through the API are drafts by default. Keep lead items as drafts so they never go live.
  • Protect the admin panel with a real login and keep it out of search.

The short answer

To run a custom calculator on its own URL under your Webflow domain, build it as a small app in a GitHub repository, then attach it to your Webflow site in Webflow Cloud on a mount path such as /calculator. Webflow Cloud deploys the app when the repository changes. A server route in the app saves each submission as a Webflow CMS item through the Data API, and a separate admin route, behind a login, lists the leads for your team.

How we built it for Paradox Machines

Paradox Machines builds data infrastructure for AI-native teams. We built their site in Webflow, then added a calculator tool on a dedicated URL under the main domain. The tool was custom code hosted on Webflow Cloud, with its code in a GitHub repository. When the team pushed a change, Webflow Cloud deployed it with no manual upload.

Every tool submission created an item in the Webflow CMS. A private admin panel, with an admin ID and password, listed the leads with filters so the team could use the data. They have since moved their site to Astro.

Is Webflow Cloud the right home?

Your toolGood home
A few inputs, maths in the browser, nothing savedA custom code embed on a Webflow page
Needs a server route, secrets or saved data, on the same domainAn app on Webflow Cloud, on a mount path
A large product with its own team and release cycleIts own app on a general host, often on a subdomain

The middle row is where Webflow Cloud fits best. Read what Webflow Cloud is for its frameworks, runtime and storage before you commit.

The pieces

  • Repository. The app's code in GitHub, with a main branch for production and another for staging.
  • App on a mount path. Webflow's docs describe an app attached to a site being served under that site's domain at a path, such as my-site.webflow.io/my-app.
  • Calculator page. The form and the maths, in the app.
  • Submit route. A server route that checks the input and saves it.
  • CMS Collection. One item per lead, with a field per answer.
  • Admin route. A page behind a login that lists and filters leads.

Match the look of the site

Visitors should not feel they left your site. The tool needs the same header, footer, fonts and colours as the Webflow pages around it. One way is to copy the header and footer markup into the app and load the same styles, then check the two side by side after every design change. Keep the navigation links pointing back to the Webflow pages, and link the tool from your Webflow menu once it is ready.

Keep the app light as well. A calculator does not need a heavy framework on the page. Fast loading matters as much here as on any landing page, since people often reach the tool from an ad or a search result.

Save submissions to the CMS

The submit route sends each lead to Webflow through the Data API's create items endpoint. The docs say it needs a token with the cms:write scope, and that items are created as drafts by default.

  • Keep the token on the server. Store it as a secret in the app's environment. Webflow's docs say secrets are encrypted and masked, and that changes apply only after a new commit triggers a deployment.
  • Keep leads as drafts. Never set them to publish. Lead data has no reason to be on the live site, so also check that no Collection list or template page shows it.
  • Check input on the server. Types, lengths and allowed values, whatever the browser sent.
  • Block spam. A hidden honeypot field and a simple limit per visitor go a long way.
  • Watch your plan's limits. Each lead is a CMS item, and plans cap items. If you expect many leads, Webflow Cloud's own SQLite storage may suit better. Our post on planning around Webflow CMS limits lists what to check.

Build the admin panel

  • A real login. Store a hashed password, not plain text, and set the session in a secure, HTTP-only cookie.
  • Slow down guessing. Limit failed logins.
  • Out of search. Add noindex and do not link the panel from the site.
  • Useful filters. By date, by answer and by status, plus an export to CSV for sales.
  • Read through the API. The admin route reads the Collection with the same server-side token. The token never reaches the browser.

Deploys and environments

Webflow Cloud deploys the app when the repository changes. Give staging its own environment on its own branch, with its own variables and a test Collection, so test leads never mix with real ones. Remember that a changed variable needs a new commit before it applies. Test on staging, merge to main, then check the live tool and send one real test lead.

Scope it before you build

A short scope list saves rework. Answer these before anyone writes code:

  1. What does the tool calculate, and who signs off the formula?
  2. Which answers does it ask for, and which are required?
  3. Does the visitor see the result before or after leaving their email?
  4. What happens to each lead: who reads it, and where does it go next?
  5. Who can open the admin panel, and how do they get access?
  6. Who owns the repository and fixes the tool when something breaks?

The last question matters most. A tool on Webflow Cloud is code, so someone has to own it after launch, just like any other part of the site.

Search and privacy

If the tool should rank, give it a proper title, description, canonical URL and a short text answer above the form, and check that it is in your sitemap. Pages in the app come from your code, not from Webflow's page settings.

The tool collects personal data, so say what you collect and why next to the form, and update your privacy policy. This is not legal advice: ask a qualified adviser what applies in your markets.

What to do next

Write down what the tool calculates, what it asks and who reads the leads. If the answer to "does it need a server" is no, an embed is simpler. If it is yes, see Webflow development or tell us about your tool. We can build the app, the CMS link and the admin panel.

Abdul Quadir
Abdul QuadirFounder of Kookies. Builds Webflow and Astro sites for startups and growing teams.

Terms used: Webflow, Webflow Cloud

FAQs

Questions
people ask.

Abdul Quadir
Still have a question?Ask us directly. We reply within a day.
Book a callPick a timehello@kookies.io

Yes. Webflow Cloud can attach an app to your Webflow site on a mount path, so the tool runs at an address such as /calculator on your domain.

Webflow Cloud deploys the app when its GitHub repository changes, so the team ships updates with a push.

Yes. A server route can create CMS items through the Data API with a token that has the cms:write scope. Items are drafts by default.

Not if you keep them as drafts and no Collection list or template page shows them. Check both before launch.

On the server only, stored as a secret in the app's environment. Never in browser code.

Yes. For Paradox Machines we built a calculator on Webflow Cloud, deployed from GitHub, with each submission saved to the CMS and a private admin panel.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.