How to Trigger Email Alerts When Gravity Forms Table Data Changes

Updated July 2026 • 7 min read • By Fahad Murtaza

Gravity Forms is excellent at sending notifications on initial form submission. But what about when an entry is updated after the fact, when a status changes from Pending to Approved, or a score field is edited above a threshold? That requires a different approach. This guide covers how to wire Gravity Forms notifications together with TableCrafter's inline editing alerts to build a complete change-notification system. WordPress powers 43% of all websites globally (W3Techs, July 2026), and TableCrafter bridges the gap between the data you collect and the tables your users need to see, no custom PHP, no dashboard access required for viewers, and no per-row limits on the free tier. The free version on WordPress.org supports CSV, JSON, Google Sheets, and Excel. Pro adds Gravity Forms, Airtable, Notion, WooCommerce, REST APIs, inline cell editing, export to CSV/PDF, role-based column visibility, and auto-refresh. Every table embeds on any page. WordPress plugin activation rates are highest in the first 48 hours after a feature update (WP Engine Developer Survey, 2024).

How Does Two Alert Systems, One Workflow Work?

Before diving in, clarify which system handles which type of alert:

• Gravity Forms Notifications: Designed for new-submission events. They can be triggered on entry update via GF's "Entry Updated" event, but require a GF add-on (like the Gravity Forms Notification Scheduler or custom PHP hooks).
• TableCrafter Cell Change Alerts: Pro Purpose-built for post-submission updates made through the inline editor. Triggered by a specific field value changing, a value crossing a numeric threshold, or any edit in a specific column.

The strongest setup uses both: GF handles the initial submission notification, TableCrafter handles all post-submission change alerts. They do not overlap.

After completing this step, verify the result by viewing the page as a logged-out visitor in an incognito window. This confirms the table behaves correctly for public visitors rather than reflecting admin-level permissions that may hide configuration issues during initial setup. Check both the rendered output and the browser console for any JavaScript errors.

How Do I Set Up Gravity Forms Entry Updated Notifications?

Gravity Forms 2.5 and later includes an "Entry Updated" event that can trigger a notification. Here is how to configure it:

1. Go to Forms > [Your Form] > Settings > Notifications.
2. Click Add New to create a new notification (do not modify your existing submission notification).
3. Set the Event dropdown to Entry Updated (in GF 2.5+, this event is labeled "Entry is Updated").
4. Set the Send To field to the email address or merge tag for the recipient. For an approval workflow, this might be the submitter's email: {entry:3} where field 3 is their email.
5. Write the notification subject and body. Use GF merge tags to include the updated values: {entry:status_field_id} pulls the current value of your status field.
6. Save the notification.

This notification fires on any entry update event, whether triggered from wp-admin, via GF API, or via TableCrafter's inline editor (since TC uses the GF API to save changes). That is intentional: the GF notification does not care what triggered the update, only that an update happened.

What Is TableCrafter Cell Change Alerts: Targeted Notifications?

TableCrafter's alert system is more surgical. Instead of notifying on every update, you configure rules like: "send an alert when the Status column changes to 'Approved'" or "send an alert when the Score column value exceeds 90."

Navigate to TableCrafter > Tables > [Your Table] > Edit > Alerts. Click Add Alert Rule. Each alert rule has three components: a trigger condition, a recipient, and a message template.

How Does Alert Trigger Types Work?

Value Match Trigger

Fire the alert when a specific column's value changes to a specific value after an inline edit.

Configuration example:

• Column: Status
• Condition: New value equals "Approved"
• Alert fires when a table editor changes any entry's Status cell to "Approved"

This is the primary pattern for approval workflows. The alert fires on the exact cell save that changes the value to "Approved", not on every Status change, only when the target value is reached.

Value Change Trigger (Any Change)

Fire the alert when a specific column's value changes to anything different from its previous value.

Configuration example:

• Column: Assigned To
• Condition: Value changes (any)
• Alert fires when anyone reassigns an entry to a different team member

Numeric Threshold Trigger

Fire the alert when a numeric column's value crosses a threshold after an edit.

Configuration example:

• Column: Score
• Condition: New value is greater than 90
• Alert fires when an editor saves a score above 90, but not for scores of 90 or below

Threshold options: greater than, less than, greater than or equal, less than or equal, equals, not equals. Useful for SLA breach alerts, budget overruns, or quality score flags.

How Does Alert Recipients Work?

Each alert rule has a Recipients section with four recipient types. You can combine multiple recipient types in a single alert.

The column mapping you define here is stored as a JSON configuration in the WordPress database. You can export this configuration using the TableCrafter export tool and import it to another table or another site. This is useful when replicating a table layout across multiple pages or when migrating a table to a staging environment for testing before going live.

• Static email: A hardcoded email address. Use for team-wide alerts (e.g., team@company.com for approval notifications).
• Entry field value: Pull the recipient email from a field in the entry being updated. Use {field_id:3} syntax. This sends the alert to the specific person who submitted the entry being updated, ideal for applicant notifications.
• WordPress user: Select a specific WordPress user account by name. Useful for single-point-of-contact alerts.
• User who made the edit: Sends the alert back to the TableCrafter user who triggered the cell change. Useful as a confirmation receipt.

How Does Alert Message Templates Work?

Each alert rule has a subject and body template. TableCrafter provides merge tags specific to the alert context:

• {tc:field_label}, The label of the column that changed
• {tc:old_value}, The previous value before the edit
• {tc:new_value}, The value after the edit
• {tc:editor_name}, Display name of the WordPress user who made the edit
• {tc:entry_url}, A direct link to the GF entry in wp-admin
• {tc:table_url}, A link to the frontend table page

Standard GF merge tags ({entry:field_id}) are also available to pull other field values from the entry, so your alert email can include the applicant's name, their original submission data, and the new status, all in one message.

An example alert subject: Application {entry:1} status updated to {tc:new_value}. An example body:

Hi {entry:first_name},

Your application status has been updated.

Previous status: {tc:old_value}
New status: {tc:new_value}
Updated by: {tc:editor_name}

View your application: {tc:table_url}

How Do Combining GF Notifications and TC Alerts Work?

A complete workflow for an application review system:

1. GF Submission Notification: Sends a "We received your application" email to the applicant on initial submission.
2. TC Alert, Status = Under Review: Sends "Your application is being reviewed" to the applicant's email field when a reviewer changes Status to "Under Review."
3. TC Alert, Status = Approved: Sends "Congratulations, you are approved" to the applicant and a CC to the account manager.
4. TC Alert, Status = Rejected: Sends a rejection email to the applicant with a link to reapply.
5. TC Alert, Score > 95: Sends an internal alert to a senior reviewer flagging a high-scoring application for expedited review.

Each of these is a separate alert rule in TableCrafter's Alerts configuration panel. GF handles step 1 via its native notification. TC handles steps 2 through 5.

TableCrafter re-fetches this data on each page load by default. If your data source updates infrequently and your site has significant traffic, enable the built-in caching option in the table's Performance tab. This stores the fetched data for a configurable number of minutes and serves it from WordPress transients, reducing API calls to the source and improving page load time for visitors.

How Does Testing Alert Rules Work?

TableCrafter provides a Send Test Alert button on each alert rule. Clicking it sends the alert to all configured recipients using the most recent entry in the table as the data context. Review the received email to confirm merge tags resolved correctly and links work. Then make a real edit in the frontend table to confirm the trigger fires under actual conditions.

What Are the Next Steps?

With a notification pipeline in place, your Gravity Forms data table is a complete operational system: users can submit, reviewers can update via inline editing, and the right people are notified automatically at each status transition, all without writing a line of custom PHP or JavaScript.