Get an email for every submission

A joiner quoting kitchen fitting work does not sit watching the Submissions tab. The enquiry has to reach him while he is on site, and the mail app on his phone is where it will actually be seen. Every form can send you an email the moment a response lands.

The switch belongs to one form rather than to your account, and it is already on for every form you create. That is worth knowing in both directions: the form you built to test an idea will email you as readily as the one taking real work.

Open the form and click Settings, the third of the four tabs across the top — Fields, Submissions, Settings, Danger. Settings then divides into five sub-tabs of its own: General, After Submission, Notifications, Encryption, Integrations.

Notifications holds two switches. "Email me on new submissions" is the one that sends the email. "Form is accepting submissions" sits directly beneath it and decides whether the form takes responses at all, so leave that alone unless you mean to close the form to new replies.

The subject line reads "New Submission:" followed by the form's title, which is what a mail rule can file on when several forms are running at once. The body lists the answers one per line, field label first, then the date and time the response arrived. A View submission button at the foot opens that response in formformform.

Only answered questions appear. A question left blank writes no line at all, so a short email is not a truncated one — it means the visitor skipped the optional questions. A field that conditional logic had hidden is left out on the same grounds.

Notifications go to the email address on your account — the address you sign in with. There is no per-form recipient box and no CC list, so every form you own reports to the same inbox.

You change it under Settings, Profile: the "Email address" field on the Profile information panel, then Save. That address is also your login, so moving it moves your sign-in with it. To put a response in front of a colleague, forward it, write a mail rule on the subject line, or send the submission onward with a webhook.

A File Upload answer does not travel in the email. Its line carries the upload's internal reference rather than the filename, and the file itself is never attached. Click View submission and the upload is waiting there as a card with its name, type and size, a Download button, and a preview if it is an image.

An encrypted form still emails you. Subject and timing are unchanged, but in place of the answers the body says the submission is encrypted and cannot be shown in email. Open it and unlock it with your private key to read it.

Email suits a form that takes a handful of responses and needs a person to act on each one. Past that the inbox becomes the bottleneck. A webhook posts each submission to a URL you choose as it arrives, and the Zapier integration fires a New Submission trigger that can create the row, card or message you actually wanted — one direction only, form to app, never a sync back the other way.

Both are set up under Settings, Integrations, and neither one switches the email off. Leave it on if you still want a copy for yourself, or turn it off and let the automation carry the response.