// v0.03 // FormForge
Build the form. Route the answer. Keep the trail.
I turn one JSON schema into a form, its validation and its response table. Rules decide what happens next, and every decision is logged with the reason it fired or did not.
01 //
Build
Three-pane builder with conditional logic written as sentences. Edits to a published form create a new version.
02 //
Route
If budget is more than 5000, tag it and notify sales. The run log says why a rule fired, or why it did not.
03 //
Export
Responses table with filters, bulk tags and a CSV that survives commas, quotes and unicode.
Why this exists
FormForge keeps intake and routing together: one versioned form schema, clear rules and an explanation saved with each response.
Questions
Is this real data?
Yes. Saved forms, responses and rule decisions are stored on the server with workspace permissions. Notifications use real delivery providers and show their actual outcomes.
Can I embed a form?
Yes. The embed tab gives an iframe snippet. Published forms work on their own public URL and in a cross-origin iframe.
How is spam handled?
Server-validated submission sessions, timing and honeypot checks, rate limits, quotas and duplicate protection reduce automated abuse.