Form builder and submissions
Open Forms from the portal menu and choose the form you need. The page has Builder, Embed, and Submissions tabs. Saving a draft, previewing it, and publishing it are different actions.
The forms catalog is available at /crm/integrations/forms, and a specific form can be opened directly at /crm/integrations/forms/:formId. The card contents and available actions depend on your form read and management permissions.
Builder
Set the internal name and code, default locale and supported locales, title, description, and submit label. Add fields, reorder them, and set type, label, and required state. Enter translated labels for each selected language and review them before publishing.
When a Preset is available, it only applies an initial set of fields and settings to the current draft. Review its fields, required state, and CRM mapping before saving. Preview shows errors or warnings; it does not publish the form, so complete all checks before Publish.
Appearance controls include theme, mode, density, radius, and accent color. Preview renders the local draft only; Save applies the changes.
CRM routing
Choose a pipeline, then an available stage and custom-field mapping. Stages can be empty until a pipeline is selected. Submit a synthetic request after changing routing and verify the owner and CRM result; do not hide a CRM error by resubmitting blindly.
Origins and anti-spam
Specify which sites may embed the form and enable the available anti-spam and submit-frequency controls. Never enter secrets or real addresses.
Lifecycle
Forms move through draft, published, and archived states. Publish enables external submission, Unpublish removes it, Archive removes it from the working list, and Restore brings it back. Before publishing, check languages, required fields, consent, CRM routing, and anti-spam. Preview is not publication.
Embed
The Embed tab provides the form code. Copy it only to a trusted site where embedding is allowed. Keep code, private links, and internal identifiers out of public materials; use a masked synthetic example for demonstrations.
Submissions
Refresh Submissions and review each visible status. An empty or partial list is not proof that older submissions do not exist. Accept confirms initial review, Retry CRM retries a failed CRM transfer, and Spam removes a suspicious request from the work queue. Check the updated status after every action. If a CRM transfer fails, give the owner the form and submission details from the available work context without copying unnecessary personal data. Retry does not automatically create a new submission.
Empty, loading-error, missing-permission, and CRM-transfer-failure states are different. An empty list is not proof that the public form is unavailable.
Screen permissions and limits
The area requires administrator access or form-management permission. A user without read access sees a denial; without manage access they cannot save, publish, archive a form, or change a submission status. If older submissions are not visible, use your organization’s approved reporting process.
Safety and localization
Do not publish real contacts, credentials, private links, or customer submissions. For Arabic RTL, verify page direction and labels before publishing the form. Avoid monetary demo fields unless the currency clearly matches the selected locale.
Related pages