Trusted by modern launch teams

Skip to main content
DevAssistant Docs
Browse documentation
Content6 min read

Forms & submissions

Connect a form to your site’s inbox and test the complete visitor-to-submission workflow.

Where to find it

  1. Project overview
  2. Project areas
  3. Forms

In this guide

A form connected to the correct site definition and a verified test submission in the inbox.

Before you start: On All projects, open the project’s three-dot menu → Overview to reach Project areas. Use a role with forms access.

On this page

Create or choose a site form

A form’s visual layout and its site form definition work together. The definition controls the managed fields and submission behavior. Templates with forms may already include a definition.

Create a form definition, then open its inbox to verify submissions.
  1. 1Form definition. Name the form and configure its notification email.
  2. 2Inbox. Open a form to inspect its submissions.

Create a form definition, then open its inbox to verify submissions.

  1. 1

    Check Forms Inbox

    Open Forms and look under Forms Inbox. Open an existing form if it is the one you intend to use.

  2. 2

    Create a new definition when needed

    Under Create Form Block, enter a Form name and the Notification email that should receive notifications. Choose Create form.

    You should see: The form appears in Forms Inbox. New forms start with name, email, and message fields.

Connect the canvas form

An unbound visual form cannot accept submissions. Check the connection even when the form already looks complete.

  1. 1

    Select the form container

    Open the page containing the form. Select the form itself in Navigator, rather than a single text field or label.

  2. 2

    Choose the site definition

    In the selected form’s controls, find Form → Site form and choose the intended definition. Review the managed fields and any synchronization notice.

  3. 3

    Review visitor-facing behavior

    Check labels, required fields, submit text, and the success/error response. Make sure the visitor can understand both a successful submission and a validation error.

Test the complete flow

Test the rendered form and its inbox together. A button click alone does not verify that a message reached the site.

  1. 1

    Publish staging

    Create a staging release containing the connected form, then open the released page.

  2. 2

    Try an incomplete submission

    Submit with a required field empty. Check that the page explains what is missing and keeps the form usable.

  3. 3

    Submit recognizable test content

    Enter a clearly labeled test name and message. Submit once and confirm the success response.

  4. 4

    Verify the inbox

    Return to Forms → Forms Inbox and open the same form. Locate the test submission and verify its values. Check notification delivery separately if enabled.

Screenshots use a local sample workspace.

Hi there, how can we help?

Help centerSearch our knowledge base of how-to articlesEmail usEmail support at support@devassistant.io