This module integrates Drupal's messaging system with GC Notify to send emails. It allows you to configure GC Notify as a message notifier, sending messages to GC Notify for delivery. An optional queue worker helps manage sending rates for large applications.
This module provides integration between Drupal messaging (message, message_subscribe, message_notify) and the GC Notify service. It creates a new message notifier called "GC Notify" that can be selected on the configuration form for message_subscribe. The configuration allows for direct posting to the GC Notify rest interface and from there the message will be sent via email.
The module also has a QueueWorker that can be enabled to allow throttling by introducing a wait time between servicing queued items before sending them to GC Notify.
Collaboration on the is module is greatly appreciated.
Set-up is a bit interesting because of how messaging works, but once you do it it is not that bad. Basically, it is:
- enable message, message_subscribe, message_notify and message_gcnotify (also recommend ultimate cron if using queues)
- message_subscribe module provides a great example module of potential hooks that you would use to start the messaging process
- configure your messaging template(s), add a reference field for the node that has changed requires notifications to go out
- add a field for email body to your template, use manage display to set p0 to subject and p1 to body.
- Add a message with tokens in the subject and body
- configure message_subscribe to use the GC Notify notifier
- Following the instruction on GC Notify to set up your account and create a template with ((subject)) as the subject and ((body)) as the body so that Drupal can do the heavy lifting for multilingualism and token replacement.
- configure this module with the url, template ID and API key from GC Notify. Select 'use queue' if you have a large application that requires throttling.
I will add more configuration details as the project progresses.