Autoresponder

Autoresponders let you automatically send a follow-up email to the person who submitted your form: a thank you message, confirmation, download link, or anything else you’d like them to receive right away.

Note

Autoresponder emails are available on Business and Volume plans.

How autoresponders work

• When a new submission is received and passes validation, Forminit triggers your Autoresponder action for that form.
• The To address is taken from a form field and must be an email-type form block variable (for example {{sender.email}} or {{your-email-address}}).
• You can customize the sender, reply-to, subject, email body, and optional attachments.
• Autoresponders are configured per form, so each form can send a different style of confirmation.

Prerequisite

Your form must include at least one email field (for example a sender block with email, or a standalone email block) so Forminit knows where to send the autoresponse.

Configuring an autoresponder

1. Open the form in your Forminit dashboard.
2. Go to Settings → Actions.
3. Activate or edit the Autoresponder action.

From

Sender email address of the autoresponder emails

• By default, autoresponder emails are sent from notifications@forminit.com.
• To send from your own domain (e.g. hello@yourdomain.com), connect SMTP under Account → SMTP.
• Once SMTP is configured, you can pick your custom sender address from the From field in the autoresponder action.

This keeps your confirmation emails fully on-brand and helps with deliverability.

To

Recipient of the autoresponder. Must be an email-type form variable.

• The To field only accepts form variables that resolve to an email block in your form.
• Typical examples:
  • {{sender.email}} using the sender block’s email property
  • {{your-email-address}} using a standalone email block called your-email-address
• At send time, Forminit reads the value from that field in the submission and sends the autoresponse to that address.

This ensures autoresponder emails always go to the actual submitter and not a hard-coded inbox.

Reply-to

Set the address that replies should go to.

• Controls where replies to the autoresponder email are sent.
• Best practice is to put your or your team’s inbox here, not the submitter:
  • Reply-to = support@yourdomain.com
  • Reply-to = hello@yourdomain.com

When the submitter clicks Reply in their email client, their message goes directly to you or your team.

Subject

Email subject line. Supports form variables.

• You can mix static text with:
  • Form block variables (e.g. {{sender.fullName}})
  • Form constants (e.g. {{@form_name}}, {{@submission_id}})
• Example subjects:
  • Thanks for contacting {{@form_name}}
  • We received your request (ID: {{@submission_id}})
  • Your booking request for {{@form_name}}

Tip: Include {{@submission_id}} (or another unique value) to keep each autoresponse in its own thread instead of being grouped together.

Email body (Editor)

The autoresponder email body is edited using a WYSIWYG editor.

You can:

• Write a custom message with headings, text, lists, and links.
• Insert form block variables (e.g. {{sender.fullName}}, {{text.message}}) to personalize the content.
• Insert form constants such as:
  • {{@form_name}} form name
  • {{@date}} submission date
  • {{@submission_id}} unique submission ID
  • {{@referer}} referrer URL the form was submitted from
  • {{@location}} sender location as City / Country (e.g. London / United Kingdom)

Typical use cases:

• Welcome or thank-you messages
• “We received your request” confirmations with a summary of key information
• Short instructions on next steps (booking, support, shipping, onboarding, etc.)

Attachments

Attach files you wish to send to the form submitter. Maximum total file size: 25 MB.

You can attach one or more files that will be included with every autoresponder email.

Common use cases:

• Booking / event flows: attach a calendar invite (.ics) so the submitter can add the event to their calendar.
• Lead magnets / downloads: send a PDF guide, whitepaper, or e-book after a content download form.
• Onboarding: include a “Getting started” PDF, checklist, or product manual.
• Offers: send a coupon, voucher, or proposal document.

If the total attachment size exceeds 25 MB, the email may fail to send with those files, so keep attachments small enough for reliable delivery.

Best practices

• Always use a form email field for “To”. Use {{sender.email}} or another email block variable so the autoresponse always goes to the correct person.
• Set Reply-to to your team inbox. For example, support@yourdomain.com, so when submitters reply, it reaches a real human.
• Keep it short and clear. Confirm what they submitted, what happens next, and how to contact you.
• Use attachments thoughtfully. Add real value (calendar invite, PDF guide, onboarding material) while staying under the 25 MB limit.