Trash Digest Notifications

Trash Digest Notifications sends scheduled email digests for content that has been moved to Trash. It groups trashed content by taxonomy-based notification email addresses and can also notify administrators when no trash activity occurred during a scheduled period.

This module is designed for teams that need recurring oversight of deleted or trashed content, especially when review responsibilities are organized by department, taxonomy term, or compliance workflow.

Features

• Sends scheduled digest emails for nodes moved to Trash.
• Groups trashed items by taxonomy term notification email addresses.
• Supports daily delivery or a custom interval-based schedule.
• Sends fallback notifications when no content was trashed during the reporting period.
• Includes a one-click test digest to verify email delivery and configuration.
• Uses state-based scheduling so environment-specific timing can differ between local, staging, and production sites.

Post-Installation

After installing and enabling the module, go to /admin/config/content/trash-digest-notifications to configure how digest emails are sent.

From the configuration page, you can:

• Choose the delivery frequency.
• Set the daily run time, if using a daily schedule.
• Define a fallback email address for empty-trash notifications.
• Send a test digest to confirm that outbound email is working.

The module does not create a new content type, media type, or text format. It works in the background by reading trashed node data, checking taxonomy term email fields, and sending grouped digest emails on its configured schedule.

This module is best used on sites where Trash usage is already part of the editorial workflow. For scheduled delivery to work reliably, your site cron should be configured correctly and outbound mail must be functional.

Additional Requirements

This project requires more than Drupal core.

• Trash module — required, because this module reads content that has been moved to Trash.
• Node — required, because digest notifications are based on trashed nodes.
• Taxonomy — required, because recipient grouping is driven by taxonomy-based notification email fields.
• A working mail system — required for outbound digest delivery.

No external API, third-party service, or front-end library is required by the module itself. However, mail delivery must be configured correctly in the target environment.

Recommended modules/libraries

The following contributed modules can improve reliability or administration experience:

• Mail System — helps control which mail backend Drupal uses for outgoing messages.
• SMTP Authentication Support — recommended when the site needs authenticated SMTP delivery for more reliable email sending.
• Admin Toolbar — makes it easier for administrators to reach the module’s configuration page.

These are not required for the module to function, but they can make setup and ongoing administration easier.

Additional Information

Trash Digest Notifications is intended for sites where content review responsibilities are distributed across categories, teams, or departments. By collecting trashed content into scheduled digests, it helps reduce alert fatigue while still keeping stakeholders informed.

Because scheduling is stored in state, administrators should review settings independently in each environment after deployment. This is especially useful when development or staging environments should not send production-like digest emails.