When an entry is saved and propagated (send one message)

Sends a notification when an entry has completely finished saving, and propagated across all sites. This trigger fires exactly once per save, regardless of how many sites the entry propagates to.

The event fires after the save transaction has committed and after the new revision has been written, so entry.currentRevision and entry.currentRevision.revisionNotes are accessible in the message body.

Section Filters

This trigger is filterable by sections and entry types and the standard element filters.

Element Filters

Element filters restrict the notification based on lifecycle-state checks against the saved element. Each filter is tri-state: require it to be true, require it to be false, or ignore it. Useful for firing only on first saves, or for skipping drafts and revisions.

Field Conditions

Field conditions restrict the notification based on the element's content, using Craft's native conditions framework. Build a rule set against the element's attributes and field values, and the notification will be sent only when every rule matches.

Must match all conditions

The condition builder evaluates every rule with AND semantics, so each rule must pass for the notification to be sent.

The "has changed" operator

Field rules now include an additional "has changed" operator, alongside the existing standard options.

When the element is saved, the "has changed" operator checks whether the field's value has changed during the save, (regardless of what the new value is). The notification will only be sent when the specified field's value has changed.

Twig variables

The object variable (and its entry alias) is the saved Entry. The pre-save copy is available as original.

{{ entry.title }} was saved by {{ currentUser.fullName }}.

{% if entry.currentRevision %}
    Revision notes: {{ entry.currentRevision.revisionNotes }}
{% endif %}

Caveats

Relationship Issues

If your message template relies on the original variable, please note that any related values (e.g. Matrix Blocks, Assets, etc.) may have changed by the time propagation has completed.

To ensure original relationships are accurate, instead use the event "When an entry is saved (send one message per each site)".

Examples

Show what changed in the title

{% if entry.title != original.title %}
    The title changed from "{{ original.title }}" to "{{ entry.title }}".
{% else %}
    The entry "{{ entry.title }}" was saved.
{% endif %}

Include the revision note when present

{{ entry.title }} was saved by {{ currentUser.fullName }}.

{% if entry.currentRevision and entry.currentRevision.revisionNotes %}
    Note: {{ entry.currentRevision.revisionNotes }}
{% endif %}

Announce only the very first save

{% if original %}
    {% skipMessage "Entry has been saved before." %}
{% endif %}

A brand new entry was just published: {{ entry.title }}