> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dapta-forms/forms.md). # Dapta Forms: Overview Dapta Forms is a free, open-source form builder at forms.dapta.ai. Build conversational forms, quizzes and lead capture flows, score answers, route people to the right ending, and send every response Dapta Forms is a free, open-source forms platform made by Dapta. You sign in with your Dapta account at [forms.dapta.ai](https://forms.dapta.ai), build a form in a visual editor, publish it and share one public link. Every answer lands in your workspace, and you can push it to your CRM, a webhook or an email the moment it arrives. There are no plans, seats or limits to unlock. Dapta Forms is free for everyone with a Dapta account, and the code is open source on GitHub.
The Dapta Forms Home screen with the left menu, three stat tiles and four shortcut cards

Home: your forms at a glance, with shortcuts to create a form, branding, integrations and analytics.

*** ## Who it is for Dapta Forms is built for marketers, sales teams and founders who need more than a contact form and less than a developer project: * **Lead capture and qualification.** Ask a few questions, score the answers, and show a booking calendar only to the people who fit. * **Quizzes and assessments.** Give points to options and map score ranges to different results. * **Surveys and feedback.** Collect structured answers and export them to CSV or your analytics stack. * **Event and intake forms.** RSVPs, new-customer questionnaires, support intake, anything with a short list of questions. You do not need to write code. Every setting described in these docs lives in the visual editor. *** ## What you can build | Capability | What it means for you | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Two layouts** | **Slides** shows one question per screen, like a conversation. **One page** shows every question on a single page with one **Submit** button. | | **14 question types** | Name, Email, Phone, Single choice, Multiple choice, Dropdown, Short text, Long text, Website, Slider, File upload, Message, Reveal screen and Scheduler (book a meeting on your calendar). | | **Logic** | Show or hide questions based on earlier answers, jump ahead, end the form early for people who do not qualify. | | **Scoring and outcomes** | Give points to options and slider ranges, then map score ranges to different thank-you messages, redirects and bookings. | | **Partial submissions** | Save answers as soon as someone shares their email, even if they never reach the end. | | **Design and branding** | Themes, colors, fonts, logos, cover screen, progress style, share card, and a workspace-wide brand kit. | | **Connect** | Send each submission to **HubSpot**, a **Webhook** you control, or notification emails. Track with Google Tag Manager, Meta Pixel and PostHog. Let respondents book through **Calendly**. | | **Submissions and analytics** | Read every response, filter partial vs completed, download CSV, and see the funnel and question-by-question drop-off. | | **Publish and share** | One public link, an embed snippet for your website, an auto-generated share card and an optional public page listing your forms. | *** ## What respondents see Your public form is a fast, mobile-first page that follows the visitor's light or dark mode (unless you fix a background color), auto-detects Spanish or English for its buttons and messages, and works with the keyboard: **Enter** moves to the next question.
A published Dapta form on desktop showing a single choice question with four options and a progress bar

A published form in the Slides layout. Respondents pick an option and the form moves on.

Read [What respondents see](/dapta-forms/respondent-experience.md) for the full walkthrough. *** ## How it fits with Dapta AI Dapta Forms uses the same login and the same workspaces as the Dapta app (app.dapta.ai). When you sign in to Forms you land in a workspace you already belong to, with the same members and roles. The app switcher at the top of the left menu jumps between **Dapta Agents** and **Dapta Forms**. Forms is where leads come in; Dapta Agents is where voice and text agents follow up. A typical flow: a visitor fills out your form, the submission is pushed to HubSpot or a webhook, and your agents or sales team pick it up from there. > **💡 Tip:** The only Forms feature tied to a Dapta AI subscription is the vanity slug in your public URL. Everything else in Dapta Forms is free. *** ## Open source Dapta Forms is published under the MIT license at [github.com/Dapta-Tech/dapta-forms](https://github.com/Dapta-Tech/dapta-forms). You can self-host it, read the public API reference, or contribute. See the [Developers](/dapta-forms/developers.md) section. ## What's next * [Key Concepts](/dapta-forms/key-concepts.md): the vocabulary used across these docs. * [Getting Started](/dapta-forms/getting-started.md): sign in, build your first form in five minutes, and tour the dashboard. * [Building Forms](/dapta-forms/builder.md): every editor feature, one page each. * [Connect & Integrations](/dapta-forms/connect.md): HubSpot, webhooks, emails and tracking. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.dapta.ai/dapta-forms/forms.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.