फ़ॉर्म

लोग आपकी साइट, फ़ॉर्म के अपने पेज या पॉप-अप पर जो फ़ॉर्म भरते हैं: हर जवाब व्यक्ति पर एक इवेंट है, फ़ील्ड से जुड़ी प्रॉपर्टी लिखता है और ईमेल से व्यक्ति को पहचानता है।

The forms list

Forms sit under Engage. Each row is one form with its status, its views, submissions and conversion over the last 30 days, and when it was last edited; the head counts the forms against the plan. New form names a form and opens it with one required email field, so a form identifies the person from its first response.

Building a form

A form opens on its own page. Build holds three panes: the steps and their fields on the left, the form as a visitor sees it in the middle, and the chosen field’s settings on the right. A field is short or long text, email, phone, number, a dropdown, a single or multiple choice, a checkbox, a date, a file upload or a hidden value, and a text block can sit between fields. A field saves to a person property or to a property of one of the person’s companies; a field with no property is kept on the response only. A field shows when an earlier answer equals a value, is one of several or is answered at all, and a field saving a property can ask something else instead once the person already holds that property.

Edits stay a draft until Publish: the live version never changes while someone fills it, and the head says when the draft holds unpublished changes.

Settings and style

Settings choose what follows a response (a thank-you message or a page to go to), an optional follow-up email to the submitter with {{key}} placing an answer, the members told of each response, the consent to process data and the communication consents each with its notice, a refusal of free email addresses, and whether fields the person already answered are left out. Every response is also guarded by a hidden field, a minimum fill time of three seconds, a proof-of-work challenge the browser solves, and limits of 10 responses per address per form and 600 per form each hour.

Style sets the font, the six colours, the corner radius and the width beside a live preview. Each colour pair shows its measured contrast as it is typed, and a pair under the 4.5:1 that text needs is refused with its ratio.

Sharing

Share opens a side panel with the form’s three placements: a page of its own at /f/{projectKey}/{formId} on the edge or on one of the project’s verified domains, a script tag that draws the form where it is pasted, and a pop-up that opens after a delay, a scroll depth or when the visitor leaves the page, once per visitor in each period. The script tag reads data-form and data-key, and the pop-up adds data-popup (delay:5, scroll:50 or exit) and data-period-days.

Responses and numbers

Responses lists each response newest first with the person, the page it came from and its answers; it exports every response as CSV, and a manager deletes one, which leaves the properties it already wrote on the person. Analytics totals views, starts, submissions and conversion over the last 30 days with views and submissions by day. Each response is a $form_submitted event on the person that writes the mapped properties and identifies the person by email, so an anonymous visit joins the person it becomes.

The plan sets how many forms a company keeps (1, 10, 50 or unlimited) and how many responses its forms take each month (100, 2,000, 20,000 or unlimited); past the monthly cap a form says it is not taking responses until the month turns or the plan grows. File upload fields come with Scale and up, and the "Powered by Prodantix" line leaves the form on Enterprise. The phone lists each form with its numbers and its responses.

Where this meets the API

On GraphQL the list is crmForms, crmForm reads one, crmFormSubmissions reads its responses a page at a time, and crmFormTotals and crmFormAnalytics give the numbers; writing is createCrmForm, updateCrmForm, publishCrmForm and archiveCrmForm, with deleteCrmFormSubmission removing a response, and every change arrives on the crmFormChanges subscription (GraphQL reference). REST serves the same under /v1/projects/{projectId}/forms, and the MCP tools are prodantix.forms.list, prodantix.forms.get, prodantix.forms.submissions, prodantix.forms.totals, prodantix.forms.analytics, prodantix.forms.create, prodantix.forms.update, prodantix.forms.publish, prodantix.forms.archive and prodantix.forms.delete_submission. A visitor’s browser reads the published form from /v1/forms/{formId} on the edge and submits to /v1/forms/{formId}/submissions, uploading files to /v1/forms/{formId}/files.