This allows Hubitat to send email notifications through a notification device using a Google Apps Script webhook / HTTP POST.
I built this as a free alternative for people who do not want to rely on paid messaging services such as SendGrid, Mailgun or SMTP relays just to send basic Hubitat email alerts.
It uses Gmail via Google Apps Script, with recipient groups controlled in the script and a shared token between Hubitat and the webhook.
Note: Google Apps Script limits consumer Gmail accounts to 100 recipients per day. That means one alert sent to 3 recipients counts as 3, not 1. For most home automation alerting, that should still be plenty if the rules are not too noisy.
GitHub link below and full noddyguide in the readme.
I believe that one can always register a secondary 'Alternate Gmail Account' specifically for Home Automation alerts if they feel that their personal gmail account might exceed the 100 recipients per day limit.
I found @gordon.thelander integration much easier to succesfully setup, as least for a non-programmer like me. I followed the HE instructions but never could get it to work. With Gordon's it was much simpler , for me anyway.
Great - call out Kurt, I have added the following comment to the readme;
Important Note
Google imposes daily sending limits on Gmail accounts. When using this gateway, a standard Gmail account is typically limited to approximately 100 recipients per day. The limit applies to recipients, not messages. For example, sending one email to ten recipients counts as ten recipients against the daily quota.
For most Hubitat use cases, 100 recipients per day is unlikely to be an issue unless the automation is particularly chatty or sending to multiple recipients for every event. That said, if someone is concerned about consuming quota on their personal Gmail account, there is nothing preventing them from creating a dedicated Gmail account specifically for home automation alerts. In fact, that can be a good practice as it separates automation traffic from personal email and makes it easier to manage notification volume independently.
Ah, this is great - I did not know it existed, just looked it up and saw it was released a few weeks ago with 2.5.0.153.
I was trying to solve the same problem, but for external alerts to these providers, Habitat’s native Email Notification driver is clearly the better default option.
The main differentiator for my Notification Gateway is that it is not really just an email sender. Because Hubitat calls a Google Apps Script endpoint, you control the backend logic. That means you can add custom routing, recipient groups, formatting, filtering, throttling or escalation logic if required.
So I would now position this as a lightweight HTTP notification broker rather than a replacement for Hubitat’s native email driver.
Hopefully it is useful for anyone who wants that kind of broker pattern.
