Enter app

Deliver the whole submission to an inbox

A window installer quotes from a short brief: rooms, measurements, a deadline. The team works out of a shared inbox and does not want a spreadsheet in the loop. The submission itself should be the message.

Steps
4
Plan
Pro
Output
Email to inbox
Mode
The Builder
The scenario
A small installer with a shared quotes@ inbox. Everything is triaged by reading and replying; nobody logs in to a dashboard during the day.
What you end up with
Each quote request arrives as a formatted message in the inbox you choose, carrying every submitted answer.
You need
  • Gmail sending connected in Account › Google
  • A Pro workspace — Email to inbox is a Pro output
  • The inbox address the messages should go to
  1. Setup › Google output

    Understand which email this is

    Webtzm can send you two very different emails, and the console keeps them apart because confusing them wastes an afternoon.

    Compared onEmail to inboxOwner submission alert
    What it isThe form's output — the record itselfA notification that something happened
    What it containsEvery submitted answerMetadata only: which form, when, what state
    Where you set itSetup › Google outputSetup › Submission handling
    Can you have both?Yes — they are independentYes
    One output per form

    A connection has exactly one Google output. Turning on Email turns the Sheet off, so this connection writes no Sheet row, no Doc and no PDF. If you want both a message and a row, that is two forms on the same page, each with its own connection.

  2. Setup › Google output

    Turn on the Email output

    Make the connection with New connection, name it Quote request, and give it its fields in the Builder exactly as in the registration tutorial. Then, under Google output, turn on Email. It needs Gmail sending connected; until it is, the switch says so.

    The Google output section with Email turned on among Sheet, Doc, PDF, Email and JSON, the Drive folder for attachments, the address each submission is sent to, the subject, the message format, a starting template and the message itself with its placeholders. Open full size
    One Google output at a time: turning Email on turns the Sheet off. Everything the message needs is set right under it.
  3. Setup › Google output

    Set the recipient, the subject and the body

    Turning the output on reveals its own settings. This is where the message is composed once, rather than by whoever happens to read it. Each saves when you leave it.

    • Send each submission to — the inbox that receives the record. Use a shared address, not a person's, so it survives somebody's holiday.
    • Subject — build it from the fields you triage by, so the inbox list is readable without opening anything. The subject line is what the shared inbox sorts and searches on.
    • Message — the message itself. Insert placeholder puts any submitted field where the cursor is, and Start from offers ready-made layouts in plain text or HTML.
  4. Analytics

    Publish and confirm

    Copy the generated code onto your page exactly as in the registration tutorial, publish, and send one invented quote request.

    Confirm in two places. The message should be in the inbox, and Analytics should show Delivered against that submission. If the console says Delivered and the inbox is empty, look in spam and check the recipient address — delivery succeeded on Webtzm's side.

When to choose this output, and when not to

Inbox delivery suits work that is done by replying. It is a poor fit for anything you will later want to count, sort or report on, because an inbox is not a table.

  • Choose it when every submission becomes a conversation, and the record's job is to start one.
  • Choose a Sheet row instead when you will ever want to ask how many, from where, or how fast.
  • Choose both — as two forms — when the team replies from the inbox but somebody reports on the numbers monthly.

The difference is not theoretical. Here is one submission as it arrives through each route — the output carries every answer, and the alert carries none:

The form's output — Email to inbox — the record itself
Subject: Quote request from Tom Whitfield

Webtzm submission record
Reference: 7dab7d37-7f65-4002-a8f3-968285618928
Accepted at: 2026-09-07T09:51:07.738Z
Synced at: 2026-09-07T09:51:30.749Z
Timezone: UTC

Name: Tom Whitfield
Email: tom.whitfield@example.com
Job: Replace six sash windows at the front of a Victorian terrace. Single glazed at the moment.
Rooms: 6 or more
Preferred Date: 2026-10-12
The owner alert — Email me for each submission — a notification, not a record
Subject: [Webtzm] New submission — Quote request

Webtzm accepted a new submission for Quote request.
Reference: 7dab7d37-7f65-4002-a8f3-968285618928

No submitted answers are included in this alert.
An inbox is not a backup

Retention shortens how long Webtzm keeps its own copy of what was submitted. With an inbox output there is no Sheet holding the record, so the message is the record. Treat the mailbox accordingly.

Where to go next

Something missing or wrong on this page? Tell support.