Smart Form Builder by Dragwyb can send an email to an administrator, send a confirmation to a visitor, or do both after a successful submission. Configure these actions inside the form editor. SMTP transport is configured separately under the plugin’s settings.
Add an email action to a form
- Open Smart Forms → Forms and edit the form.
- Open the Submission toolbar, then expand Data Handling.
- In After Submissions Actions, select Send Admin Email for an administrator notification, Send User Email for a visitor confirmation, or both.
- Configure the controls shown for each selected action and click Save in the editor header.
Configure the recipient and message
Both email actions provide the Send To (Email), Subject Line, and Message Body controls. The section label identifies which action you are editing: Admin Email Notification or User Confirmation Email.
- Send To (Email): the administrator action defaults to the WordPress site’s administration email address. The user confirmation action defaults to an empty recipient and needs a valid email address. You can use the supported field dynamic-tag syntax to obtain the visitor’s email from a submitted field.
- Subject Line: the source-configured default is New Submission: [Form Name]. In version 1.3.6, the square-bracket text is not a registered dynamic tag, so it may remain literal in the subject. Replace it with the subject text or supported dynamic tag you want, then verify the actual received subject.
- Message Body: the source-configured default is {all_fields}. This placeholder inserts the non-empty submitted fields with their labels. The action also supports field placeholders such as {name} using the form’s field key, while the dynamic-tag system supports tokens such as {field:field_id}, {form_id}, {post_id}, {post_title}, and {site_title}.
Build useful notification messages
- Send the administrator only the submission details needed to follow up.
- For visitor confirmation, use a clear subject and a concise message that confirms receipt without promising a response time you cannot meet.
- Use {all_fields} when the message should include all non-empty submitted fields. Use a field-specific placeholder when only one value is needed.
- Make sure the user-email recipient field is present on the form and validates as an email address.
Test notifications and understand limitations
Submit a test form with representative values. Check the administrator inbox and the visitor address used for the test, including spam or junk folders. If the email does not arrive, first confirm that the relevant action is selected and saved, then follow Configure SMTP Delivery and Why are form submissions not sending email?.
- One recipient per action: although the recipient control description mentions comma-separated addresses, the current action code validates the recipient with is_email(), which expects a single address. A comma-separated recipient list is therefore not reliable in version 1.3.6; use one recipient per action.
- Actions run after successful validation: normal submission actions are processed when the submission has no errors. Error logging is handled separately when an error is recorded and the action is selected.
- Email sending is not the same as inbox delivery: a successful send request does not guarantee that the recipient’s mail provider will place the message in the inbox. Confirm receipt with a test address.
For a broader overview of which actions can run after a submission, see Configure Form Submission Actions.
Screenshot to add: Submission toolbar showing Admin Email Notification and User Confirmation Email recipient, subject, and message controls