Forms

What this area does

Contacts Forms is your submission operations view:

• A forms list with totals and recent activity.
• Search and sorting for finding forms by name, Form ID, page, activity, or submission volume.
• Placement links, connection summaries, and an archive for forms you no longer want in the active list.
• An analytics tab for form performance trends.
• A per-form submissions table with CSV export.
• Submission grouping based on the stable Form ID used by the published form widget.

Forms shown here come from published Form Widget widgets.

Review form performance

Submission details behavior

• Search the submissions currently loaded in the table. Sort the submitted date, name, email, and other available field columns by selecting a column heading. Load more rows before searching when you need to include older submissions.
• When a submission is tied to a contact, clicking that row opens the contact slideout on the Activity tab with submission context.
• Form submissions tied to contacts are available from the contact activity feed.
• If a submitted email matches a contact that was previously removed from the active list, Hiveality restores that contact instead of creating a duplicate or dropping the submission.
• Columns are generated from the form field schema.
• Extra unmapped keys are shown in the detail drawer.
• Submission details can include the submitted page, source identifier, and available visit attribution such as campaign tags, referrer, and landing path.
• If a published form was edited after earlier submissions, Hiveality still uses the rendered field labels from the submission so valid entries are not blocked by older field definitions.

Build and publish forms

• Create forms in Form Widget.
• Publish page updates from Drafts and Publishing.
• After publish, new forms and submissions appear in Contacts Forms.
• In the Form widget's Submission settings, turn on Email Notification when a team inbox should receive each submission. Hiveality can prefill the recipient and subject from your current email settings, and you can still customize them before saving.
• The recipient field stays available while notifications are off. Enter a valid address before turning notifications on. A page, shared layout, or popup cannot be published with an enabled notification that has no valid recipient; turn the notification off explicitly when it is not needed.
• Notification emails use duplicate prevention and a short retry when it is safe to retry. Hiveality also keeps the delivery outcome with the submission so failed notifications are easier to review.
• Connected form reads distinguish a confirmed delivery from an unconfirmed send, bounce, complaint, suppression, or failed attempt by checking recent submissions. This makes an accepted message less likely to be mistaken for one that reached the inbox.
• A team notification is sent after the visitor's submission is stored. If the notification address or email delivery needs attention, the saved submission and its follow-up automation are not changed into a failed form response.
• Browser autofill, extensions, or page timing can fill hidden spam-check fields or omit interaction signals. Hiveality treats those browser-only signals as advisory and continues normal field, consent, website, and rate-limit checks, reducing false rejections of valid submissions.
• A public form does not stay stuck while its browser spam check prepares. If that check does not finish promptly, Hiveality continues with its server-side validation and submits the visitor's entry without requiring another click.

Review an eligible missed notification

When a saved submission records a notification failure before any delivery was attempted, its detail view can show Review notification. Enter the intended team address and review the sender, reply-to address, subject, original submission time, and complete message. Nothing is sent during the preview.

Choose Confirm and send notification only after checking the details. This sends one delayed team notification; it does not resubmit the form, create another contact, or rerun tags, lists, or automations. If delivery may already have been attempted, Hiveality keeps the recovery action unavailable so the team can check email-delivery records without risking a duplicate.

Connected form management

Connected assistants and API-key workflows can read and update forms after review.

• Read one form with its submission totals, current settings, duplicate-name warnings, recent notification health, and the pages or pop-ups where it appears.
• Update a form name, Form ID, field list, tags, lists, submit button text, thank-you message, redirect, or notification email settings.
• When a connected workflow sends tag or list names instead of IDs, Hiveality resolves existing names for the website and can create missing tags or lists before saving the form connection.
• When a form appears on a page or pop-up, Hiveality writes the same settings into the embedded Form widget and refreshes the live view. The edit remains in place after the page or pop-up is saved again.
• When a notification recipient is changed through a connected workflow, Hiveality warns if the address uses a domain that has no mail server. A mailbox-specific problem is reported after an actual delivery or bounce result is available.
• Renaming a Form ID also updates matching Form Submitted flow triggers so follow-up automations keep running.
• If several imported or copied forms share one record, a connected workflow can split one page onto a new Form ID. Existing submissions stay with the original form, and new submissions from that page use the new form.
• Deleting a form preserves submissions by default. If submissions must be removed too, export or review them first and confirm the removal explicitly.
• If a deleted form is still embedded on a page or pop-up, Hiveality warns that saving that surface can recreate it until the widget is removed.

Automations

Use Flow Triggers with the Form Submitted trigger to run follow-up automations after submissions.

Check form connections

The Forms list shows where each form appears. Select a page label to open that page in the builder, or open the connection badge to review linked pages, tags, lists, flows, and redirects without opening the form first.

In the form widget settings, the Connections panel summarizes what is tied to the current form:

• Pages where the form is embedded.
• Tags and lists added after submission.
• Direct flows that start from the form.
• Redirects that run after submit, including missing destination warnings.

When you edit submit actions before saving, the panel previews the updated connections so you can see what will happen before publishing.

You can also ask Agent Bee questions like "What happens when someone submits this form?" to review the same form connections from chat.

Archive forms

Archive an unused form to remove it from the active list without deleting its submission history. Archived forms appear in the collapsed

Archived section at the bottom of the Forms list and can be restored at any time.

Archiving does not remove a Form widget from a published page. Review the form's placement and connection badges before archiving, then edit and publish the page if visitors should no longer be able to submit it.