Alerts and Scheduled Digests

Use SiteTrax.io notifications when you want an email about a new matching detection or a scheduled summary of stored readings. Set them up through a connected assistant, review the exact settings, and confirm before anything is created. A request for a report does not automatically authorize a recurring email.

Choose an alert or a digest

Need	Choose	What it does
Tell me when this identifier is next observed	Detection alert	Watches for a new stored detection matching a supported identifier or filter. A one-time alert completes after the first match.
Keep watching for matching detections	Repeating detection alert	Continues watching until cancelled or expired. Repeat suppression prevents some duplicate emails; it is not an email for every stored row.
Send a regular operational breakdown	Scheduled digest	Emails supported grouped metrics at the chosen local time and on the chosen days.

These are defined notification workflows over SiteTrax.io detections. They do not provide arbitrary automation, a general task scheduler, a custom-recipient mailing service, or a guarantee of real-time physical presence. A new observation means the unit was recorded at that time; it does not prove where it is now.

Before you start

Connect a supported assistant using your active, verified SiteTrax.io account. See Account Access and OAuth.
Check that the intended projects are shared with that account.
Allow read access to list notifications and inspect delivery history. Creating an alert or digest, or cancelling either, also needs notification-management permission.
Use your own verified account email as the destination. The tools do not accept another person's address or an arbitrary distribution list.

Your assistant may request notification permission when you first connect or when you ask to create or cancel something. The timing depends on the client. Permission allows the capability; it does not replace your confirmation of each proposed change.

Create a detection alert

Decide the full identifier or supported condition, the projects to watch, whether it should stop after one match, and when it should expire. Ask the assistant to resolve ambiguous project names and confirm the identifier before proposing the alert.

Using SiteTrax.io, help me prepare a one-time email alert for the next new detection of the container I specify at the project I choose. First confirm the full identifier and project. Then show the exact condition, whether direction is included, one-time behavior, recipient policy, and expiry. Ask for my explicit confirmation before creating anything.

For an arrival or departure alert, ask the assistant to check how gate direction is configured. A heading-based direction filter and a dedicated ingate/outgate project or camera are different ways to define the boundary. Adding the wrong filter can exclude the detections you expect.

After you approve, the assistant should return the saved notification ID and summary. Ask it to list the notification so you can check its status and expiry. Saving an alert confirms its configuration; it does not prove that a matching detection has occurred or that an email has reached your inbox.

Create a scheduled digest

Choose the project scope, grouping, metrics, optional filters, send time, named timezone, weekdays, and expiry. Supported schedules include daily, weekdays, weekends, weekly, or selected weekdays. Specify a timezone such as America/New_York instead of an ambiguous abbreviation.

Using SiteTrax.io, propose a weekday digest for the project I choose, sent at 08:00 America/New_York. Use stored-reading counts grouped by processing status and asset type, with a 30-day expiry. Show the exact project, filters, metrics, schedule, recipient policy, and reporting-window rule. Ask for my explicit confirmation before scheduling it.

Each edition covers the interval since the preceding scheduled edition, starting from creation for the first edition. A Monday weekday digest includes the weekend. Ask to see the stored window in delivery history when comparing two editions.

A count of stored readings is not a count of physical equipment. Distinct identifier metrics also need a clear definition. Ask the assistant to explain the returned measure and any incomplete or bounded result instead of relabelling it as inventory, throughput, or financial savings.

Review, cancel, or replace a notification

Listing notifications and delivery history is read-only. You can ask:

Using SiteTrax.io, list all my notifications with their IDs, types, status, project scope, and expiry. Include recent delivery statuses and the reporting windows for digests. Do not change anything.

Notification status can be active, completed, cancelled, or expired. Delivery history can show queued, sent, failed, or suppressed entries. A sent entry is a service delivery record, not proof that someone opened or read an email. Project access and verified recipient status are checked again when notifications are processed.

To stop one, give its exact notification ID, ask the assistant to show the proposed cancellation, and confirm. The same cancellation tool applies to alerts and digests. To change a saved condition or schedule, review a cancellation and replacement; the current tool set has no general edit command.

Limits and missing emails

Notifications expire after 30 days by default. Ask for the intended expiry explicitly and check the saved value. The current service limit is 50 active notifications per user across alerts and digests; cancel an unused one if you reach it.

If an email does not arrive, first inspect the notification and delivery history. Check expiry, cancellation or one-time completion, filters, current project access, email verification, digest timezone and selected days, and repeating-alert suppression. An event alert needs a new matching detection; a digest needs a due schedule. Then check your inbox filters and contact [email protected] with the notification ID, expected time, and visible status. Never include credentials.