Connection alerts

A paired messenger account can silently drop. Automata emails the people who manage a connection when it disconnects, so you find out before an AI client starts failing.

How alerts are detected

Two mechanisms work together:

• Webhooks give fast alerts. Automata registers a per-connection webhook with Evolution and the Telegram bridge. Each delivery is treated as a prompt to re-read live state, not as trusted state.
• An hourly sweep is the backstop. It runs inside the web process and re-checks every connection, so a missed webhook delays an alert by up to an hour rather than losing it.

An alert is recorded only after the email is actually sent. A broken SMTP configuration delays alerts instead of dropping them, and a deployment with no SMTP host computes alerts without delivering them.

Configure mail

Set the NUXT_SMTP_* variables and NUXT_MAIL_FROM on the web service. Use NUXT_SMTP_TLS=false for STARTTLS on port 587, and true for implicit TLS on 465. The sender must be an address your provider accepts. The full list is in Configuration.

The same mail settings deliver organization invitations.

Operational rules

• Set NUXT_WEBHOOK_SECRET so webhook requests carry and verify the shared x-webhook-secret header.
• Make sure NUXT_WEBHOOK_URL is reachable from Evolution; the Telegram bridge derives its callback from NUXT_PUBLIC_APP_URL.

Test it locally

Run a mail catcher, then trigger the sweep by hand. The steps are in Local deployment. For missing or duplicate emails, see Troubleshooting.