Aptiro can tell you about ten 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, a review falling overdue, a website form submission, and three from outreach: your tasks for the day, a contact replying, and a meeting being booked. Slack and email are configured separately in Settings > Integrations, each with its own set of toggles, so a team can send high-score triggers to Slack and leave the rest to email, or any other mix.

In the app
The bell in the app bar lists the latest notices for you. A team lead can opt in to notices for accounts owned by people on teams they lead. Slack and email are unchanged.
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.
Under the same Slack panel, Team brief channel is optional. When set, Aptiro posts the Monday team brief there once, from 08:00 once the team's brief is ready. The post follows the message detail you chose for the shared Slack channel: where that is summary, or where the brief could include money or pay wording, it shows only how many items need attention and a link, not the items themselves. It uses the team view only, never a member's private items. Each person can still turn their own Monday brief email and Slack direct message off from the notifications bell.
Select Disconnect to remove that connection. Aptiro always forgets the stored token on this side, and keeps the channel and the event choices, so reconnecting does not make you set them again. When Slack accepts the revoke, the confirmation says the token was revoked. When it does not, Aptiro is still disconnected here, and the message asks you to remove the Aptiro app from your Slack workspace, because access could not be revoked and may still be live there.
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 first-scan email to owners
You do not need any of the above to hear about your first scan. When your
very first scan finishes, every owner of your account gets an email from
Aptiro itself, sent from noreply@aptiro.io: what the scan found, your
highest-scoring triggers and a link straight to the run. It arrives even if
you have not set up SMTP, because a brand new account has not had the chance
to.
It is sent once, on the first scan your account finishes, and never again. A scan that fails outright does not count, so the next one that works sends it instead. Every later run is yours to route, through Slack or your own email settings above.
To stop it before your first scan runs, switch off Email owners when a scan finishes under Account owners in the Email section and save.
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 counts as at risk (you are told when a saved score first falls below it; the mark on the account stays a hand mark only), 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.