Email Notifications — Transactional Alerts and Reports
What does the Email Notifications integration do?
Email delivers ZopNight's transactional messages straight to users with no app or webhook to configure: admin cloud-alert emails, membership and role changes, and export links that expire after 1 hour. Email is not a subscribable notification channel; each user switches individual email events on or off under Settings > Notifications > Emails.
ZopNight uses email for the messages that must reach people even when chat is quiet: cloud alerts to organization admins, membership and role changes, team updates, scheduled report deliveries and export links. Every user controls per-event opt-outs; organizations on enterprise plans can route mail through their own SMTP sender for domain-aligned delivery.
Template-driven sends and one-hour signed links
Transactional email is template-driven and sent through ZopNight’s delivery service. Admin alert emails accompany critical cloud alerts (credential expiry, permission loss, sync failures) independent of chat channels. Recommendation shares and CSV/report exports arrive with signed links that expire after one hour. Custom SMTP senders (host, port, credentials, from-address) are provisioned per organization by ZopNight staff and validated with test sends.
Nothing to install, just toggle event groups
Nothing to install. To manage preferences: Settings > Notifications > Emails, toggle each event group. For custom SMTP delivery, contact support with your SMTP host, port and sender identity.
Alerts, lifecycle notices and expiring export links
Admin cloud-alert emails. User, role and team lifecycle notices. Report and export delivery with expiring links. Recommendation sharing by email. Per-event opt-outs. Optional tenant SMTP sender.
One layer of control
Email has no channel subscription of its own. Subscribed events go to the chat channels (Slack, Microsoft Teams, Google Chat and Custom Webhook). Email follows each user’s preferences under Settings > Notifications > Emails, where each email event can be switched off, so when someone gets no email, their own preferences are the first place to look.
Where it fits
Email is the right choice for the transactional messages listed above, such as admin cloud alerts, membership changes and export links. Budget and anomaly alerts are routed to chat channels or a webhook (org admins get a budget email only when no channel is set up), so reach anyone outside Slack through a webhook into your own tooling.
Limits worth knowing before you connect
Email is not a general alert-broadcast channel — chat channels (Slack, Teams, Google Chat, webhook) carry the full event stream. Self-service SMTP configuration is not exposed to customers.
Email Notifications integration: common questions
Someone on a subscribed channel is getting no email. Why?
Email is not a subscribable channel, so channel subscriptions never send email. Each user receives only the email events switched on under Settings > Notifications > Emails, so check that person's own email settings.
Can I configure my own SMTP server?
Not self-service. Custom SMTP senders (host, port, credentials and from-address) are provisioned per organisation by ZopNight staff and validated with test sends.
How long does an emailed export link stay valid?
One hour. Report and CSV export links, and shared recommendations, arrive as signed URLs that expire after that.