Notifications

Email notifications

Get notified when submissions arrive. Route different forms to different email addresses. Reply to visitors directly from your inbox.

How notifications work

Every accepted (non-spam) submission triggers an email notification. ContactFire picks the recipient address using the precedence chain described below.

Notifications are sent from [email protected]. The Reply-To header is set to the visitor's email address if their form includes an email field — so you can reply directly from your email client.

Account notification email

The fallback recipient for all notifications. Set it once in Settings → Notifications. If you leave it blank, ContactFire falls back to your account email.

  1. Open your dashboard and go to Settings
  2. Click Notifications
  3. Enter the email address that should receive all form notifications
  4. Click Save

Per-form recipients

Route submissions from a specific form to a different email — useful for routing a "Sales enquiry" form to your sales team and a "Support" form to your helpdesk.

  1. Open Form Studio
  2. Select the form
  3. Click Settings (top toolbar)
  4. Under Notifications, enter the recipient email
  5. Click Save
Per-form recipients override all token-level and account-level settings for that form.

Token recipient overrides

Assign a custom recipient to an embed token or API key. All submissions using that token go to the specified address — regardless of your account notification setting.

To set a token recipient override:

  1. Go to Embed Tokens or API Keys
  2. Click the token you want to configure
  3. Under Notification email, enter the recipient address
  4. Click Save

Reply-to email

When ContactFire sends a notification email, it can set the Reply-To header to the submitter's email address. Hit reply in your email client and your message goes straight to the visitor — no copy-paste required.

Auto-detection

If you name your email field something common — email, emailAddress, reply_to, userEmail, and about 25 other variations — ContactFire detects it automatically. No config needed.

<!-- Auto-detected — no config needed -->
<input type="email" name="email" placeholder="Your email" />

Configure a specific field

If your field has a non-standard name, set Reply-To Field Name explicitly:

  • Per form: Form Studio → Settings → General → Reply-To Field Name
  • Per embed token: Embed Tokens dashboard → token settings → Reply-To Field Name
  • Per API key: API Keys dashboard → key settings → Reply-To Field Name

Priority by submit route

POST /api/form/submit

Embed token replyToField → API key replyToField → auto-detect

POST /api/public/forms/:formId/submit

Form replyToField → auto-detect

If a replyToField is configured but the submitted value is not a valid email address, the Reply-To header is omitted entirely — there is no fallback to auto-detection in that case.

Weekly digest

Prefer a summary over individual emails? Enable the weekly digest in Settings → Notifications. You get a single email each Monday covering all submissions from the prior week.

Digest contents
  • Total submissions per form
  • Spam count
  • Most recent 5 submissions per form
  • Link to your full inbox

Recipient precedence chain

When a submission arrives, ContactFire walks this chain and sends the notification to the first address it finds:

1
Per-form notification recipient
Set in Form Studio → Settings → Notifications
2
Embed token recipient override
Set on the embed token used to submit
3
API key recipient override
Set on the API key used to submit
4
Account notification email
Set in Settings → Notifications
5
Account email
Your login email address
Previous: Spam filtering Next: Live form monitoring