LoginSign Up
← Back to all sparks
F

Formaloo

MKT AUTO
Velocity6.3

No-code platform for building forms, surveys, customer databases and apps

www.formaloo.com ↗

Formaloo is turning its form builder into something you describe rather than configure.

form-builderai-authoringno-code-logicportalsworkspace-configrelease-train
◆Current state
Formaloo runs a monthly release train, and the last few cycles moved it from a form builder to a workspace platform: portals with domain-restricted signup, workspace-level Themes, teams, timezone-consistent records, and voting on Kanban and Gallery boards. July's Magic Logic release is the turn — form logic, previously a rule system learned field ID by field ID, can now be generated from a plain-English description and reviewed as readable rules before it applies. The two cycles since are smaller: ranking and slider fields, Unsplash in the image picker, per-page covers.
◆Where it's heading
Two threads are converging. The platform thread keeps replacing per-object configuration with workspace-level systems — Themes, timezone, teams, cleanup — so an admin sets something once and every form inherits it. The AI thread is aimed squarely at the setup cost of that system, and Magic Logic's design (generate, list every rule in plain text, then apply) suggests Formaloo wants AI authoring configuration rather than running at response time.
◆Prediction
Expect the Magic Logic pattern — describe, preview as readable rules, apply in one click — to spread to the other configuration surfaces these release notes keep calling time sinks: themes, portal access rules, and data block setup.

◆Recent moves

  1. 13d ago

    Ranking fields to allow users submit priorities

    Ranking fields let respondents order their priorities and carry that order into the workflow and reporting, arriving alongside a Slider field and Workspace Cleanup. This is a field-library cycle rather than a platform one — the kind of month that fills gaps competitors already cover. The entry summarizes rather than enumerates, so the smaller form, data, PDF and account fixes are not itemized.

  2. 21d ago

    Unsplash, per-page covers, and a cleaner dashboard.

    Unsplash search lands inside the image picker, Classic form pages get individual cover images, ending pages take a cover and logo, and forms appear directly in dashboard folders. Presentation work on the same workspace-level track as Themes — fewer steps to make a form look right. Nothing here changes what a form can do.

  3. 1mo ago

    Magic Logic generates form rules from a plain-English description

    ⚡ SPARK

    Magic Logic is where Formaloo's AI thread stops assisting and starts authoring: it reads the existing form, fields, pages, formula fields and current rules, then writes the branching, scoring and routing logic from a description. It shows every generated rule as plain text for review before anything touches the form, which fits the platform's habit of making configuration inspectable. Three further AI features ship alongside it.

  4. 2mo ago

    Portal signup adds domain rules and magic-link registration

    Portals can now restrict signup by regex on the email field — a corporate domain, any .edu address — and register brand-new users by magic link rather than only logging existing ones back in. The two compose, so a domain-gated portal can onboard without passwords or manual approval. This is the portal half of Formaloo becoming somewhere users hold accounts, not just a form they submit once.

  5. 3mo ago

    Let your team vote on what matters

    Kanban and Gallery cards get upvote buttons that re-sort by vote count, with the eligible audience configurable between workspace members, portal visitors, or both. It closes the loop on boards customers were already running for roadmaps and feature requests but had to poll for elsewhere. Another external workflow pulled inside the portal.

  6. 3mo ago

    Workspace Themes replace per-form design configuration

    Themes make design a workspace-level object — layout, palette, fonts, logo, custom CSS — attached to forms instead of configured per form, so editing one updates every form connected to it. Standalone per-form design is gone: every new form requires a theme, and deleting one forces reassignment first. This is the clearest instance of the pattern running through the year, replacing per-object setup with an inherited workspace system.