Download the PHP package rainlab/notify-plugin without Composer

Notification engine

Plugin is currently in Beta status. Proceed with caution.

Adds support for sending notifications across a variety of different channels, including mail, SMS and Slack.

Notifications are managed in the back-end area by navigating to Settings > Notification rules.

Notification workflow

When a notification fires, it uses the following workflow:

1. Plugin registers associated actions, conditions and events using registerNotificationRules
2. A notification class is bound to a system event using Notifier::bindEvent
3. A system event is fired Event::fire
4. The parameters of the event are captured, along with any global context parameters
5. A command is pushed on the queue to process the notification Queue::push
6. The command finds all notification rules using the notification class and triggers them
7. The notification conditions are checked and only proceed if met
8. The notification actions are triggered

Here is an example of a plugin registering notification rules. The groups definition will create containers that are used to better organise events. The presets definition specifies notification rules defined by the system.

Here is an example of triggering a notification. The system event rainlab.user.activate is bound to the UserActivatedEvent class.

Here is an example of registering context parameters, which are available globally to all notifications.

Here is an example of an event preset:

Creating Event classes

An event class is responsible for preparing the parameters passed to the conditions and actions. The static method makeParamsFromEvent will take the arguments provided by the system event and convert them in to parameters.

Creating Action classes

Action classes define the final step in a notification and subsequently perform the notification itself. Some examples might be sending and email or writing to the database.

A form fields definition file is used to provide form fields when the action is established. These values are accessed from condition using the host model via the $this->host property.

An action may choose to provide no form fields by simply returning false from the defineFormFields method.

Creating Condition classes

A condition class should specify how it should appear in the user interface, providing a name, title and summary text. It also must declare an isTrue method for evaluating whether the condition is true or not.

A form fields definition file is used to provide form fields when the condition is established. These values are accessed from condition using the host model via the $this->host property.

Model attribute condition classes

Model attribute conditions are designed specially for applying conditions to sets of model attributes.

An attributes definition file is used to specify which attributes should be included in the condition.

Save to database action

There is a dedicated table in the database for storing events and their parameters. This table is accessed using the RainLab\Notify\Models\Notification model and can be referenced as a relation from your own models. In this example the MyProject model contains its own notification channel called notifications.

This channel should be registered with the RainLab\Notify\NotifyRules\SaveDatabaseAction so it appears as a related object when selecting the action.

The label is shown as the related object, the class references the model class, the relation refers to the relation name. The param defines the parameter name, passed to the triggering event.

So essentially if you pass a project to the event parameters, or if project is a global parameter, a notification model is created with the parameters stored in the data attribute. Equivalent to the following code:

Dynamically adding conditions to events

Events can be extended to include new local conditions. Simply add the condition class to the event $conditions array property.