Verified purchaser
A rocky start, a lot of lessons, and how to skip my mistakes
1. What happened to me
I bought FormWise to build step-by-step tools: a form at the start, followed by chained tasks (A leads to B, B leads to C), without leaning too heavily on AI chat.
The first time I sat down to design, I realized that the form inside a flow doesn't behave like a traditional form. It looks and feels like a chat: questions appear one at a time, and you never see them together in neat boxes. The editor does let you set a character limit on each question, but in practice that limit isn't enforced. Users can type as much as they like, even if you capped the field at 25 characters. I worried that if someone pasted 2,000 characters into a short field, my costs would climb quickly from the form alone.
I asked FormWise's built-in AI assistant for help. It pointed me to a classic form view that didn't work for me, and suggested a "lock" system using AI that required an API key, which didn't work either. Feeling frustrated, I requested a refund. Today, I hold the top license, Tier 4.
Still, I kept exploring, because I couldn't find a comparable alternative anywhere else, and I'm glad I did. In the portal, you can connect each user's own API key. The portal also includes a regular-looking form, and that's what I use now to collect the data I need. It works exactly the way I wanted. Knowing this from day one would have saved me a lot of frustration.
2. The limitations I ran into while designing (and how I worked around them)
Instead of relying only on the documentation, I had Claude explore the actual editor. Here's what we found:
The flow is a chain that only moves forward. You can't go back to a previous step or repeat one.
Why it matters: if you want rounds ("ask, analyze, then ask again for whatever is missing"), you can't build that with nodes.
My workaround: rounds only exist in chat mode with history turned on, or by manually duplicating nodes a fixed number of times. I use chat only where it's truly needed.
There is no node to ask the user a question mid-flow.
Why it matters: you can't pause, request a piece of information, and continue.
My workaround: I put all the questions at the start, in the portal's welcome questions. If something is still missing, the AI asks for it in the chat.
There is no if/else.
Why it matters: without it, you can't build "if this happens, do that."
My workaround: I use the Classify node, which creates branches by category, plus the form's rules, which show or require questions based on earlier answers. The Evaluator node scores content but doesn't branch.
The wait node only waits for time.
Why it matters: it can't wait for a user's reply.
My workaround: I use it only to delay a step (for example, "in 2 hours"). To wait for replies, I use the chat.
Multi Run is not a loop.
Why it matters: it doesn't go through a list of items; it simply runs a fixed set of branches in parallel.
My workaround: I instruct the AI to handle all the items in the list in a single step.
Reading a web page uses FormWise credits. If each client brings their own AI key, this undermines the model.
My workaround: I built my own tool on a free Cloudflare server that reads the page without spending FormWise credits.
Knowledge base search works on exact words, not meaning. It didn't return the index I asked for.
My workaround: I wrote a map of the documents directly into the prompt, so the AI chooses the right document without relying on search.
Each custom tool must be enabled manually on every node. You have to click Discover Tools and switch it on. Otherwise the AI can't see it, and nothing warns you.
A tip that saves credits: if you upload your documents as .md files instead of PDF or Word, searching the knowledge base costs no credits. I tested it myself: it cost 0. PDF and Word files uploaded as files cost 1 credit per search, as stated in docs.formwise.ai.
3. My recommendations if you're just starting
The documentation at docs.formwise.ai isn't enough for an AI like Claude or ChatGPT to learn everything FormWise can (and can't) do before helping you design. This is what worked for me:
Connect Claude to your browser with /chrome and let it explore the entire tool line by line: flows, agents, portals, settings. Ask it to write everything down in a file.
Use that file as the AI's knowledge base. That way it guides you based on what FormWise actually does, not on what it assumes it does.
Supervise the design yourself from the very beginning. Go step by step, so you learn while you build and catch mistakes before they cost you money.
Team_FormWise
Oct 27, 2026Thank you for taking the time to write this up. Feedback this specific is rare, and most of what you found is accurate. A few quick notes, grouped the way you did.
On the character limit. You are right, and that is a bug on our side. The limit saves in the editor but is not enforced when a Flow runs. It is being fixed now, both in the form and on the server, so a pasted wall of text cannot slip past a short field.
On the form experience. Flow questions run in the chat composer by design, but we hear you that a classic one-page form is what many builders want. A proper form layout for Flows is on our list. In the meantime, the Portal's personalization questions are exactly the right tool for structured intake, and we will make that path much clearer in the docs and in the assistant so nobody has to discover it the hard way.
On the assistant pointing you to a "lock" feature. That does not exist. The assistant made it up, and we are tightening what it is allowed to say about the product so it stays grounded in what FormWise actually does.
On Flow limitations. Your read is correct: Flows run forward, Multi Run is parallel rather than a loop, and Pause waits on time rather than a reply. Two things are closer than they look. Agents can already pause mid-run and ask the user a question before continuing, and the natural next step is bringing that into Flows as a node. An If/Else node has also been built and is going through final work before release. Looping over a list and a "for each" mode for Multi Run are on the roadmap but not built yet. We will publish a plain "what Flows can and cannot do" page so you can plan around this instead of discovering it.
On Knowledgebase search. This one is a direct result of our own pricing, and your tip explains it. Markdown files become Pages, which are free to search but use keyword matching. PDFs and Word files go through semantic retrieval, which is why they cost a credit. We are working on giving Pages the same meaning-based search while keeping them free, so the cheaper path is no longer the weaker one.
On tools needing to be enabled per step with no warning. Fair. We are adding a check in the editor that flags a connected tool with nothing switched on.
On docs for AI assistants. We do publish docs.formwise.ai/llms-full.txt, and every workspace has an MCP server you can connect to Claude or Claude Code that exposes the live Flow schema and docs search. We clearly did not make either easy to find. That is on us, and we are surfacing both in Getting Started.
Web page reads on your own API key are a pricing question rather than a technical one, and it is a fair point we are discussing.
Thank you again for sticking with it and for writing up the workarounds. If you are open to it, we would love to send you early access to the Ask User node and If/Else when they land. Reach us at hello@formwise.ai.