Index of /download/extras/NotifyTwilio

Icon  Name                              Last modified      Size  Description
[PARENTDIR] Parent Directory                                       -   
[TXT] README.html                       2026-07-05 17:03  3.5K  
[   ] NotifyTwilio-v26186.zip.sha256    2026-07-05 17:03   90   
[   ] NotifyTwilio-v26186.zip           2026-07-05 17:03   15K  
[   ] NotifyTwilio-v26186.tar.gz.sha256 2026-07-05 17:03   93   
[   ] NotifyTwilio-v26186.tar.gz        2026-07-05 17:03   11K  
[TXT] LICENSE.html                      2026-07-05 17:03  1.1K  
[TXT] CHANGELOG.html                    2026-07-05 17:03  156

NotifyTwilio Reactor Add-on

The NotifyTwilio Reactor add-on enables notification via Twilio Messaging.

This extension is experimental as of July 5, 2026.

Installation

To install:

  1. Download a release package;

  2. Unzip/de-tar the package into your ext subdirectory. Your ext subdirectory is typically at the same level as your Reactor config directory, or may be within your config directory. You may create the ext directory if it does not already exist.

    Linux:
    tar -C -xzf
    zip: cd && unzip

    Windows: open the ZIP archive and copy-paste the NotifyTwilio folder to your

  3. Install the dependencies by running npm run deps in the ext/NotifyTwilio directory. Docker users will need to do this from within their running container like this:

    docker exec -it reactor /bin/sh
cd /var/reactor/ext
npm run deps

  4. Copy the template notifier configuration from config_example.yaml into your config/notification.yaml file and update the configuration values with your Twilio account information and notification preferences (details below). Be sure to copy only the Twilio: section as indicated by the comments in example file.

  5. Restart Reactor. After restart, Twilio will be be shown as a new target for Notify actions in Reactions.

Configuration Details

You can create any number of notification profiles for this target, but the default profile must always be provided.

The account_sid and auth_token must be defined in your default profile. These values come from your Twilio account. You may optionally define them in other profiles; if not defined by other profiles, they will be inherited from default.

The from profile value sets the message sender, and is also derived from your Twilio account. This value must be set in the default profile. Other profiles will inherit the default profile's value if they don't configure them.

The to value is optional in all profiles and designates the default recipient for messages. Notifications that do not specify a recipient in the action will use this default. If not configured on a profile, it will be inherited from the default profile. If not configured on the default profile, the from value will be used.

Use with NotifyRouter

NotifyTwilio can be a target for NotifyRouter routes. Currently, the only overridable parameter allowed in a NotifyRouter target is to (the recipient override field).

Support

For support, please post (respecting the posting guidelines) in the Multi-System Reactor category of the SmartHome Community.