Build, edit, and analyze forms directly inside Claude using simple conversations.
Create forms, edit fields, add logic, search submissions, and get insights, all by describing what you want. No manual setup or switching tools.
Hey Product Hunt 👋
I’m happy to announce the Jotform Claude App!
We built this to simplify how forms are created and managed.
Usually, you have to build forms step by step, then switch to other views or tools to test them and understand the responses.
With this, you can do all of that in one place by just describing what you need: create forms, edit them, run test submissions, and look at results.
Would be great to hear how you end up using it.
Report
while the idea is nice, and jotform itself is great, I don't realize how you come up with this need. Were users asking for working directly in claude or is just a new distribution channel?
@alxrda Fair question, it’s not just about Claude as a distribution channel.
We’re seeing a shift where users increasingly want to interact with software conversationally instead of clicking through menus and setup steps. Forms are actually a perfect fit for that, since most people think in terms of outcomes, not configurations.
So the idea was less “users asked for Claude specifically” and more “users want faster, AI-native workflows,” and Claude is a great environment for that experience.
Report
@aytekintank got it. Do you have this approach built within jotform? like an agent/chat like experience to create/manage forms - reports, everything?
@alxrda Yes, we’ve actually been moving in that direction across Jotform as well with products like Jotform AI Agents, Jotform AI and other AI-powered workflows.
The Claude App is more about bringing that conversational experience directly into environments where users already spend time and work naturally.
The "copy any design" angle is bold how does it handle dynamic or interaction-heavy sites? Curious if it captures animations and hover states or mostly static layout.
Report
yesterday i spent 30 mins on a multilingual contact form generating realistic test data. invalid Polish phone formats that pass length checks but fail country-code regex were what kept slipping through (libphonenumber catches it cleanly, but it's overkill for a contact form). with conditional branches test-data setup eats half the session.
@webappski Honestly this is exactly the kind of workflow pain we wanted to reduce with the Claude App.
A lot of the time goes into testing edge cases, conditional logic, and realistic submissions rather than building the form itself. Being able to generate, edit, and test conversationally makes those iterations much faster.
Report
Forms-in-a-chat-window is the right shape because the brittle part of form-building was never the fields — it was the loop: build, preview, find an edge case, dig back to the right field, repeat. Collapsing that into a conversation kills the tab-switching latency, and the implicit memory of the conversation context turns "add validation to the phone field" into a one-line ask instead of a five-click navigation.
Where I keep landing on these AI-in-existing-tool products is that the win shows up in the everyday flow, not in the marquee demo. I've been building a small AI-powered weekly meal-planning PWA called DishRoll on the side, and the same pattern holds: the value isn't "generate a 7-day plan" (that's a demo); it's "swap Thursday for something high-protein after my workout shifted" mid-week. Curious how Jotform handles state continuity across a long-running form-build conversation — do you expose the form-graph back to the model after each edit, or rely on the chat history as the source of truth?
@samir_asadov Really appreciate this perspective, and totally agree that the real value shows up in the iteration loop, not just the initial “generate a form” moment.
That’s actually a big part of why we approached it conversationally. A lot of form-building friction comes from repeatedly jumping between builder, preview, submissions, settings, logic tabs, etc. Keeping the workflow in-context makes those small iterative changes much lighter.
On the state side: we don’t rely purely on raw chat history. The system also works with the underlying form structure/state after edits, so the conversation stays grounded in the latest version of the form rather than only remembering prior messages.
Report
as a claude's fan i do love this :) creating and analyzing forms is no easy and this is perfect for that. i wonder if it would give a detailed and analyzed dashboard based on the inputs.
Replies
Jotform
while the idea is nice, and jotform itself is great, I don't realize how you come up with this need.
Were users asking for working directly in claude or is just a new distribution channel?
Jotform
@alxrda Fair question, it’s not just about Claude as a distribution channel.
We’re seeing a shift where users increasingly want to interact with software conversationally instead of clicking through menus and setup steps. Forms are actually a perfect fit for that, since most people think in terms of outcomes, not configurations.
So the idea was less “users asked for Claude specifically” and more “users want faster, AI-native workflows,” and Claude is a great environment for that experience.
@aytekintank got it. Do you have this approach built within jotform? like an agent/chat like experience to create/manage forms - reports, everything?
Jotform
@alxrda Yes, we’ve actually been moving in that direction across Jotform as well with products like Jotform AI Agents, Jotform AI and other AI-powered workflows.
The Claude App is more about bringing that conversational experience directly into environments where users already spend time and work naturally.
@aytekintank got it. Thanks, good luck!
The "copy any design" angle is bold how does it handle dynamic or interaction-heavy sites? Curious if it captures animations and hover states or mostly static layout.
yesterday i spent 30 mins on a multilingual contact form generating realistic test data. invalid Polish phone formats that pass length checks but fail country-code regex were what kept slipping through (libphonenumber catches it cleanly, but it's overkill for a contact form). with conditional branches test-data setup eats half the session.
Jotform
@webappski Honestly this is exactly the kind of workflow pain we wanted to reduce with the Claude App.
A lot of the time goes into testing edge cases, conditional logic, and realistic submissions rather than building the form itself. Being able to generate, edit, and test conversationally makes those iterations much faster.
Forms-in-a-chat-window is the right shape because the brittle part of form-building was never the fields — it was the loop: build, preview, find an edge case, dig back to the right field, repeat. Collapsing that into a conversation kills the tab-switching latency, and the implicit memory of the conversation context turns "add validation to the phone field" into a one-line ask instead of a five-click navigation.
Where I keep landing on these AI-in-existing-tool products is that the win shows up in the everyday flow, not in the marquee demo. I've been building a small AI-powered weekly meal-planning PWA called DishRoll on the side, and the same pattern holds: the value isn't "generate a 7-day plan" (that's a demo); it's "swap Thursday for something high-protein after my workout shifted" mid-week. Curious how Jotform handles state continuity across a long-running form-build conversation — do you expose the form-graph back to the model after each edit, or rely on the chat history as the source of truth?
Jotform
@samir_asadov Really appreciate this perspective, and totally agree that the real value shows up in the iteration loop, not just the initial “generate a form” moment.
That’s actually a big part of why we approached it conversationally. A lot of form-building friction comes from repeatedly jumping between builder, preview, submissions, settings, logic tabs, etc. Keeping the workflow in-context makes those small iterative changes much lighter.
On the state side: we don’t rely purely on raw chat history. The system also works with the underlying form structure/state after edits, so the conversation stays grounded in the latest version of the form rather than only remembering prior messages.
as a claude's fan i do love this :) creating and analyzing forms is no easy and this is perfect for that. i wonder if it would give a detailed and analyzed dashboard based on the inputs.