Form Submissions And Notifications
Every form with the database action stores its entries, and every form with the email action sends notifications. This page covers both halves: the Submissions screen where entries are read and exported, and the Notifications tab where the emails are composed. Read it when you are wiring up who gets told about a submission, or looking for an entry you know arrived.
The Submissions Screen
Starting screenFormsSubmissions.
The screen lists stored entries per form. The Forms list itself also carries an Entries column, and its count links straight to that form's submissions, which is the faster route when you are already on the list.
Entries carry a status of Unread, Read or Starred, and the tabs above the table filter by it. Opening an entry marks it as read, so the Unread tab behaves as an inbox. Star the entries you need to return to, and use the delete action for the ones you do not.
Two export buttons sit above the table, Export CSV and Export JSON, and both respect the status tab you are on, so exporting from the Starred tab downloads only the starred entries.
How Notifications Work
Starting screenthe form's edit screen, Form Settings, the Notifications tab.
Notifications are a list, not a single email: press Add Notification for each message the submission should trigger, so the office can receive the full entry while the visitor receives a confirmation. Each notification card holds its own recipients (Send To, with CC and BCC), its envelope (From Email, From Name, Reply-To), the Subject and Message Body, an Email Format of HTML or plain text, and a toggle to attach uploaded files.
A new form arrives with one notification already configured, addressed to the site's admin email with the whole entry as its body, so submissions are never silently unreported. The default recipient can be changed site-wide under Canvas > Theme Options in the Forms tab, and any notification whose Send To is left empty uses it.
Merge Tags
Anywhere in a notification, a merge tag inserts submission data when the email is built. The available tags are listed under the notification cards on the tab itself: {form_title}, {field:name}, {all_fields}, {admin_email}, {site_url}, {date}, {ip}, {user_name}, {user_email} and {referrer}. The two you will use most are {field:name}, which inserts one field's value by its field name, and {all_fields}, which inserts the whole entry. Setting Send To to {field:email} is how a confirmation email reaches the visitor at the address they typed.
Conditional Sending
Turn on Enable conditional sending on a notification card and a Condition row appears: a field name, an operator and an expected value. The notification is sent only when the condition is met, which is how a "Sales" recipient receives only the submissions whose department field says sales. The operators cover equality, containment, comparison and emptiness, and the condition row stays hidden until the toggle is on.
Pitfalls
No email arrives. Check three things in order: the Send Email Notification action is ticked on the Actions tab, the notification's Send To resolves to a real address, and the site can actually send mail. Deliverability is the usual culprit, and the Forms tab of Theme Options carries SMTP settings for exactly that reason.
A conditional notification never sends. The condition names a field by its field name, not its label. Check the Form Field block's field name on the form layout and match it exactly.
An entry shows no form association. Entries collected before forms on a page were told apart are grouped under a legacy key, and the screen labels them as such. New submissions are filed under their own form key.
The export is smaller than expected. Exports follow the active status tab. Switch to the All tab before exporting when you want every entry.