Email notifications

Choose who is emailed about each submission, how the email is worded, and what arrives when on each plan.

Works on every planUpdated Sep 22, 2026

How notifications work

Storing a submission and emailing you about it are separate steps. A submission is saved and visible in Submissions the moment it is accepted, on every plan. The email follows, as soon as possible on paid plans and in a daily digest on Free. If email ever fails, nothing is lost: the submission is already stored.

Everything in this guide lives on the form's Notifications tab.

Recipients

A recipient is an address that may receive a form's notifications. The address you enter when you create a form is its first recipient. To add another, enter it under Recipients and click Add. We send it a confirmation link, and it shows as Pending until someone clicks it.

PlanRecipients per form
Free1
Pro5
Agency10
Nothing is emailed to an unconfirmed address. Submissions are still stored, just not sent. A form backend that mails anyone it is told to is an open relay, so this rule has no override. If the confirmation went missing, use Resend next to the address. You can resend once every 10 minutes.

Each recipient carries one of three badges:

  • Verified: confirmed and able to receive mail.
  • Pending: waiting for the confirmation click.
  • Suppressed: the address bounced or reported our mail as spam, and we no longer send to it.
Keep the list clean. Remove addresses that never confirm or have been suppressed. If several people need every submission, a shared inbox or group alias as a single recipient is the most reliable setup, and Slack suits a team channel.

Instant or daily digest

How quickly the email arrives depends on the plan:

PlanDelivery
FreeOne digest per form per day, at 9:00
ProOne email per submission, sent as soon as it is accepted
AgencyOne email per submission, sent as soon as it is accepted

The digest arrives at 9:00 in the workspace owner's timezone, which you set under Settings in the sidebar. It covers everything the form received since the last one, with every submission written out in full rather than a count and a link. A form's very first digest is sent as soon as its first submission arrives, so you can see it working during setup. Days with no submissions send nothing.

Only the email waits. The dashboard, webhooks, Slack and integrations all receive a submission immediately on every plan that includes them.

Subject line and Reply-To

Subject line

Under Notification settings, the subject line is a template. Write {{field}} to insert a submitted value, for example New enquiry from {{name}}. Field names match regardless of case, and a field the submission does not contain is replaced with nothing. Subjects are cut at 200 characters. New forms start with New submission from followed by the form name.

Reply-To

Pick the field that holds the submitter's address, and replying to the notification writes back to them. New forms use the field called email. The value is checked on every submission; if it is not a valid address, that email simply has no Reply-To. The list of fields comes from the form's most recent submission, so send a test first.

Digest emails have no Reply-To, since one digest can cover several people.

Turning notifications off

Clear Send email notifications and save. Submissions are still stored, searchable and exportable, and webhooks and integrations keep running. Turn it back on at any time.

If an email does not arrive

  • The recipient is Pending or Suppressed. Check the badges on the Notifications tab.
  • The submission was held as likely spam. Submissions routed to spam review do not notify. Look in the form's spam view; see spam filtering.
  • You are on Free. Your email is in tomorrow's 9:00 digest.
  • Your mail provider filed it. Check spam and promotions folders, and add the sender to your contacts.

Next steps