Form UI builder for Make scenarios that captures user input as variables
Built for Make Pro users building customer-facing automation apps.
“I have the Pro Plan 1- I have a Database on Make.com with ID’s from 1 to X, each has an array with information. 2- I have a connection with a Document generator…”
The receipts — real demand
“I have the Pro Plan 1- I have a Database on Make.com with ID’s from 1 to X, each has an array with information. 2- I have a connection with a Document generator called Documentero. My goal is to have a screen for the user to input the ID, and it will use these fields to populate the Documentero connection and generate my doccument.”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Make Pro plan users building customer-facing automation apps and needing a form interface to collect user input as scenario variables. No search volume, but the pain signal describes a common product-builder workflow (database lookup, document generation, variable injection).
Competition & the opening
Make natively supports scenario input variables and webhook triggers with custom forms; Typeform, Tally.so, Fillout, and Jotform all integrate with Make via webhooks; Softr builds no-code apps with Make integration. Market is crowded (7/10). The gap is Make users want form UI built inside Make's interface, not a separate tool, and want pre-built templates for common patterns (document generator +
What's hard to build
Building a form builder UI (validation, conditional logic, styling) is feature-heavy and non-trivial. Integrating seamlessly with Make's scenario state, variable naming, and webhook payloads requires deep Make API knowledge. Hosting and scaling the form submissions, especially for customer-facing apps with SLA expectations, adds operational complexity.
Why now
Make's webhook + variable input pattern is clunky compared to dedicated form builders; users want embedded UI without leaving Make.
How you'd monetize
usage-based ($0.05-0.10 per form submission) or $12-20/mo tier for up to 500 sub