Description
Stop Sending Notification Emails That Dump Every Field in One Unreadable Block
The {all_fields} merge tag in Gravity Forms is convenient, and it is also blunt. It prints every field, in the same layout, with pricing tables, empty values, and internal fields included. Admins end up with cluttered notifications, and customers get confirmation emails that look nothing like the rest of the business. Gravity Forms All Fields Template changes that by putting the output of the merge tag under your control. You choose how it renders, which fields appear, and what gets left out, without rewriting your forms or hand-building every email.
Three things set it apart from a generic email tweak: selectable templates (default, form-specific, or custom), modifier-based filtering directly inside the merge tag, and support for excluding individual inputs and Nested Forms children. All of it hangs off the merge tag you already use.
Core Capabilities Overview: Control the Merge Tag Output in One Place
The Gravity Forms All Fields Template WordPress plugin works at the level of the merge tag itself. Instead of replacing notifications or building a separate email system, it intercepts what {all_fields} would print and lets you decide the structure. That keeps your existing notifications, confirmations, and any other place the merge tag appears intact.
You can start with the bundled default templates, point a single form at its own template, or write a fully custom one. There is also a no-template option for cases where you want the original Gravity Forms behavior back on a specific form. Because the choice is made per form or per tag, one site can run several output styles side by side.
Filtering is the other half. Modifiers appended to the merge tag decide which fields are included or excluded, so a staff notification can show everything while a customer receipt shows only what the customer needs to see.
Feature Breakdown: What You Can Shape and How
Choose the Template That Fits the Form
- Default templates give you a cleaner starting point immediately after activation.
- Form-specific templates let a registration form, a quote request, and a support form each present data in its own way.
- Custom templates let developers write markup that matches a brand’s email design.
- No template restores standard Gravity Forms output where you do not want changes.
Template locations are filterable through the gwaft_template_paths filter, which means you can register your own directory, for example one inside a theme or a custom plugin, and keep template files under version control alongside the rest of your code.
Hide Pricing Fields and the Order Summary
The nopricingfields modifier removes product and pricing fields from the output, including the Order Summary label that normally accompanies them. This matters for forms that mix order data with general information. A fulfillment team may want quantities and options, while an internal notification about a lead has no use for a price table. The modifier has been refined to keep the label from lingering when combined with other modifiers.
Filter Fields With the Modifier Syntax
The :filter modifier limits output to specific fields, and it can target specific inputs within a field, such as one part of a multi-input Name or Address field. Modifiers containing underscores are parsed correctly, so custom modifier names can stay readable. The :exclude modifier works in the opposite direction, removing the fields or inputs you name. It can also drop the description text of a Consent field, a small detail that keeps legal copy out of notifications.
Nested Forms Support
Gravity Forms Nested Forms produce child entries that the standard merge tag handles poorly. This plugin supports them directly, and the :exclude modifier can remove specific child fields from a Nested Form field. A parent form that collects team members, for instance, can list names and roles in the email while omitting phone numbers or internal notes captured in the child form.
Filter and Exclude Through a Custom Function
When modifiers are not expressive enough, you can pass the decision to your own PHP function. That handles conditional logic such as hiding a field when another field has a certain value, or showing fields based on the entry’s user role. Signature field images are handled correctly when filtering is in use.
Real-World Applications
Customer Receipts That Look Like Receipts
A store using Gravity Forms for custom orders can send customers a tidy confirmation using a custom template, while the internal notification keeps the full detail. Hiding the pricing block on the internal fulfillment email is a one-modifier change.
Agencies Managing Many Client Sites
Agencies can keep a library of template files, register a shared path with gwaft_template_paths, and reuse the same branded output across client projects. Each form can still override the default when a client has special requirements.
Multi-Step Applications and Registrations
Long forms with many sections often produce notifications nobody reads. Filtering lets a reviewer’s email contain only the fields needed for a decision, while an archival copy keeps everything. With Nested Forms, an event registration listing several attendees can show each attendee’s essentials without clutter.
Privacy-Conscious Workflows
Excluding sensitive inputs, or Consent descriptions, from emails reduces how much personal data travels through inboxes. The entry in the database remains complete; only the message changes.
How It Works Under the Hood
The plugin hooks into the processing of {all_fields} and checks which template applies. It looks for a form-specific template first, then a custom one, and falls back to the defaults. Modifiers on the merge tag are parsed next, and the field list is reduced accordingly before the template renders it. Custom functions run in the same stage, so they can adjust the final list.
Templates are ordinary PHP files, which makes them straightforward to read, copy, and modify. Because the plugin is released under the GPL, you are free to study the code, adapt it for a project, and extend its behavior using the available filters. Nothing is locked behind an opaque layer.
The plugin also fits alongside other Gravity Forms add-ons that touch entry data, since it changes presentation of the merge tag rather than the data stored in the entry.
Frequently Asked Questions
Does this change the data stored in Gravity Forms entries?
No. It only alters what the {all_fields} merge tag prints. Entries in the database keep every value. Hidden or excluded fields are simply left out of the rendered notification or confirmation.
Can different forms use different templates?
Yes. You can assign a form-specific template to one form while others use a default or custom template. A form can also opt out entirely with the no-template setting.
How do I hide prices from an email?
Add the nopricingfields modifier to the merge tag. It removes pricing fields and the Order Summary heading, so the email shows submitted information without the cost breakdown.
Can I leave out specific child fields of a Nested Form?
Yes. The :exclude modifier accepts child fields within a Nested Form field, so you can keep names in a notification and drop details you do not want repeated there.
What if the built-in modifiers do not cover my rule?
Use the custom function option for filtering or excluding. Your function can apply any logic PHP allows, such as checking another field’s value, and the plugin applies the result to the output.

