Set up Slack and email notifications
Aptiro can tell you about six kinds of event as they happen: a new trigger, a trigger that scores above your high-score threshold, a trigger marked actioned, a scan finishing, an account turning at risk, and a review falling overdue. Slack and email are configured separately in Settings > Integrations, each with its own six toggles, so a team can send high-score triggers to Slack and leave the rest to email, or any other mix.
Slack
Select Add to Slack to install the Aptiro Slack app into your workspace. This is a one-time, per-organisation connection: once it is installed, choose the channel Aptiro should post to and switch on the events you want there. Block Kit messages carry the account name, the relevant detail, and a score badge where one applies.
Fill in your SMTP host, port, username and password (SendGrid, Gmail and similar providers all work this way), and a from address. Test Connection sends a real test through those settings and reports success or the error straight away, so you find out before relying on it. TLS is configured separately for STARTTLS (587) or SSL (465), matching whatever your provider expects.
The two thresholds behind the events
At-risk and review overdue are not raised by a scan: they come from Settings > Notifications, where you set the health score below which an account is automatically flagged at risk, and whether overdue reviews (based on each account's review cadence) raise a notification at all. Both checks run once a day alongside the scheduled AI scan.
See also: connecting your first data source covers where the trigger events themselves come from, if you have not set one up yet.