Drupal is a registered trademark of Dries Buytaert
Search API Solr 4.4.0 Minor update available for module search_api_solr (4.4.0). Page Manager 8.x-4.0 Major update available for module page_manager (8.x-4.0). Trash 3.1.0-beta2 New beta version released for module trash (3.1.0-beta2). Commerce AutoSKU 3.0.1 Minor update available for module commerce_autosku (3.0.1). Custom Field 4.0.10 Minor update available for module custom_field (4.0.10). Alternative login ID & display names 2.0.12 Minor update available for module alt_login (2.0.12). EntityReference UUID 3.0.1 Minor update available for module entity_reference_uuid (3.0.1). LocalGov Publications Importer 1.1.1 Minor update available for module localgov_publications_importer (1.1.1). Configuration Override Warn 8.x-1.6 Module config_override_warn updated after 10 months of inactivity (8.x-1.6). Table Alternate Rows Module table_altrow crossed 1,000 active installs.

Push Framework Templates

1 sites No security coverage
View on drupal.org

This module enhances the Push Framework by providing a content-aware templating system for push notifications. It allows you to customize the message content based on the type of content that triggered the notification, with support for tokens and per-channel overrides for different delivery methods.

Extends the Push Framework module with a content-aware templating system for push notifications. Where Push Framework handles delivery across channels (email, SMS, web push, etc.), this module lets you control what the notifications actually say based on the content that triggered them.

Requirements

Configuration

Templates are managed at Administration > Configuration > Push Framework Templates (/admin/config/push-framework-templates).

Creating a template

Each template has:

  • Title: A human-readable name for the admin list.
  • Event key: The lookup key that determines when this template is used (see below).
  • Subject and Body: The notification text, with support for tokens.
  • Per-channel overrides: Optional subject and body for specific delivery channels (email, SMS, etc.). If no override is set for the active channel, the default subject and body are used.

Event keys and template resolution

The event key defines how specific a template is. When a notification is dispatched, the module tries to find a matching template in this order, using the first match it finds:

  1. {entity_type}__{bundle}__{topic} (most specific)
  2. {entity_type}__{topic}
  3. {topic} (least specific, catch-all)

For example, when a new article node is created, the lookup order is:

  1. node__article__create
  2. node__create
  3. create

This means a generic create template acts as a fallback for all content types unless a more specific one is defined.

Supported tokens

Templates support standard Drupal tokens as well as the following tokens provided by this module:

Token Description [user:display-name] The notification recipient's display name [push-object:label] The entity label (title) [push-object:type-label] The human-readable bundle name [push-object:author] The display name of the entity author [push-object:url] The canonical URL of the entity [push-object:parent-label] The parent entity label (for comments) [push-object:parent-url] The parent entity URL (for comments) [site:name] The site name

If the Token module is installed, a token browser is available directly in the template form.

Per-channel overrides

Some channels have different formatting requirements. A push notification to a mobile device may need a much shorter subject than an email, for example. Each template can have a separate subject and body per channel. The override section in the form lists all currently enabled channel plugins and lets you opt in to a custom text for each one.

Activity

Total releases
2
First release
Jun 2026
Latest release
1 month ago
Releases (12 mo)
2 ▲ from 0
Maintenance
Active

Releases

Version Type Release date
1.x-dev Dev Jun 11, 2026
1.0.0 Stable Jun 11, 2026