Email Alert Digest vs. Instant Alerts in TableCrafter: Which to Use

Updated July 2026 • 6 min read • By Fahad Murtaza • By Fahad Murtaza

TableCrafter's email alert system keeps your team informed whenever data in your tables crosses a configured threshold. Alerts fire instantly, one email per rule crossing. There is no digest batching mode. For periodic data summaries, a separate Scheduled Export feature delivers a CSV snapshot on a daily, weekly, or monthly WP-cron schedule. This guide explains how instant alerts work, what the Scheduled Export feature offers as a complement, and how to configure each from the TableCrafter admin. 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. 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 with a [tablecrafter] shortcode or the native Gutenberg block. In a 2024 study of business WordPress sites, 68% of teams needed non-admin users to update form data at least weekly (WP Engine Survey, 2024).

What Are TableCrafter Email Alerts?

Pro Email alerts are a Pro tier feature that fires notifications when a row changes inside a TableCrafter table. Because TableCrafter writes edits back to Gravity Forms via GFAPI::update_entry_field(), every inline edit, bulk column-fill, or row duplication is a traceable event that can trigger a notification.

Alerts are configured as rules on a table. Navigate to TableCrafter → Tables, open any table, and find the Email Alerts tab in the table builder. Each rule specifies one recipient address, a field to watch, an operator and threshold value (>, <, =, >=, <=, or contains), and a subject line template. An alert fires the first time a field value satisfies the rule after an inline edit, bulk fill, or row duplication. It does not re-fire on every subsequent edit once the threshold is already met. To notify multiple people for the same condition, create one rule per recipient, since each rule accepts a single address. There is no digest mode in the current release; alerts are always instant.

What Is Instant Alerts: Real-Time Notification for Time-Sensitive Data?

With instant alerts, TableCrafter sends one email per change event, immediately after the edit is confirmed via wp-admin/admin-ajax.php. The email lands in the recipient's inbox within seconds of the cell being saved.

Instant alerts are the right choice when:

• A field change has downstream consequences that require human action, for example, a status badge flipping from Pending to Approved that should trigger a call or shipment.
• Your table has low edit frequency. If only a handful of rows change per day, instant alerts stay manageable and give recipients immediate context.
• You are tracking sensitive data (payment status, driver assignment, access flags) where delayed awareness is a business risk.
• Different recipients need to be notified for different columns, TableCrafter supports column-scoped alerts, so a finance contact can receive instant alerts only when a cost column changes.

What Is Digest Alerts: Batched Summaries for High-Volume Tables?

A digest alert mode that batches change events into hourly or daily summary emails does not currently exist in TableCrafter. Threshold alerts always fire instantly, one email per rule crossing, the moment an edit is saved.

For periodic data summaries, TableCrafter offers a separate Scheduled Export feature Pro. Scheduled Export is configured independently from alert rules and sends a CSV file of the table's current data on a WP-cron schedule: daily, weekly, or monthly. The export can include a CSV file attachment and covers all rows the recipient's role is permitted to see. This is the closest current analog to a digest: it does not notify on individual changes, but it gives a recipient a regular snapshot of the full dataset on a predictable schedule.

Scheduled Export works well when:

• Recipients are managers or stakeholders who need a weekly data review rather than real-time interruptions.
• Your table sees high-frequency edits from field teams and per-edit alerts would overwhelm inboxes.
• You need an audit trail delivered automatically without requiring recipients to log into WordPress.
• You want to feed a downstream system or spreadsheet on a regular cadence by attaching the current CSV.

How Do I Configure Each Mode in the Table Builder?

In the Email Alerts tab, each alert rule has a single recipient. Here is a representative instant alert for a dispatcher who needs to know when a load status changes to Cancelled:

Table: Load Tracker Q3
Recipient: dispatch@company.com
Watch field: Status
Operator: =
Threshold: Cancelled
Subject: [TableCrafter] Load #{entry_id} Cancelled

To notify a second recipient for the same condition, add a second rule with the same field, operator, and threshold but a different recipient address:

Table: Load Tracker Q3
Recipient: manager@company.com
Watch field: Status
Operator: =
Threshold: Cancelled
Subject: [TableCrafter] Load #{entry_id} Cancelled

For the Scheduled Export feature, navigate to TableCrafter → Tables → Edit → Scheduled Export tab and configure:

Recipient: weekly-summary@company.com
Frequency: weekly
Attach CSV: Yes
Subject: [TableCrafter] Weekly Load Tracker Export

These two features, threshold alert rules and scheduled export, run independently on the same table. You can have both active simultaneously.

How Does Comparing the Two Modes Side by Side Work?

TableCrafter has two distinct email delivery mechanisms. Instant threshold alerts fire the moment a field value crosses a configured condition. Scheduled Export delivers a periodic CSV snapshot on a WP-cron schedule. They serve different needs and are configured separately. Choosing between them depends on whether you need a human to react to a specific change immediately, or whether you need a regular data feed for review or downstream processing.

You can activate both on the same table. A dispatcher receives instant alerts when a load status changes to Cancelled, while a finance contact receives a weekly CSV covering all loads regardless of status. The two features share no configuration and fire entirely independently of each other.

Practical recommendations by use case

For driver or field-team management tables, use instant alerts scoped to the status or assignment column. A dispatcher receives a notification within seconds when a driver marks a load as Delivered or Cancelled. For a periodic overview of all activity, configure a daily Scheduled Export to the supervisor's inbox, that covers rows that changed without a threshold crossing (mileage updates, notes, timestamps).

For project or task tracking tables where team members edit throughout the day, instant alerts scoped to a specific status column (for example, Status = Blocked) keep project managers aware of blockers in real time. For a weekly team retrospective, a Monday morning Scheduled Export provides the full dataset without per-edit noise.

For approval or review workflows where a status badge change (e.g., Draft → Ready for Review) should immediately notify a reviewer, instant alerts on the specific status column are the right choice. Scope the alert to that column only so that minor field corrections in other columns do not generate noise. Duplicate the rule if two reviewers both need notification.

For e-commerce or order management tables, instant alerts on high-value status transitions (e.g., Status = Refunded, Amount > 500) catch exceptions immediately. A weekly Scheduled Export to the finance team provides the complete order record without overwhelming them with individual order alerts.

How Does Troubleshooting Email Alerts Not Sending Work?

If alerts are configured but not arriving, work through these checks in order:

• SMTP configuration: TableCrafter sends alerts through WordPress's wp_mail() function. If your WordPress installation lacks a reliable SMTP plugin (WP Mail SMTP, Postmark, SendGrid, etc.), emails may silently fail. Install and configure an SMTP plugin first.
• Nonce and capability errors: All TableCrafter edits go through wp-admin/admin-ajax.php with nonce validation. If an edit fails the capability check (e.g., a user lacks the role permission for that table), no change is recorded and no alert fires.
• Scheduled Export timing: The Scheduled Export feature relies on WordPress cron (wp-cron). Threshold alert rules do not use cron; they fire synchronously when the inline edit AJAX call completes. If your Scheduled Export is not arriving, verify that wp-cron is running. On low-traffic sites or sites where DISABLE_WP_CRON is set to true, cron events will not fire until a page visit triggers them. Use a plugin like WP Crontrol to inspect scheduled events and confirm the export event is queued.
• Spam filters: Alert emails originate from your WordPress site's sending address. Add a dedicated "From" address in your SMTP plugin and ensure SPF/DKIM records are set for your domain.
• Column scope mismatch: If you scoped an instant alert to a specific column and edited a different column, no alert fires by design. Double-check the column mapping in the Email Alerts tab.