AI Studio
AI Studio teaches NiteWtch how to read your vendor alert emails. Steps: 1) Create a profile → 2) Connect a route → 3) Build alert types & validate → 4) Publish. Live alerts use published alert-type snapshots, not AI on every email.
Official workflow
- Create a profile for one vendor or email format.
- Connect an inbound route (the address your monitoring tool emails).
- Use the wizard to build alert types, validate (free), then enable types on the profile.
- Publish the profile when validation looks correct.
Guides
- AI Studio units — AI Studio units measure billed actions in the studio (simulate, discover, suggest, generate)—not every ingested email. Trial tenants hit a hard stop at the limit; paid tenants can continue with metered overages.
- Profiles — A profile is a saved ruleset for one kind of email (one vendor or format). Publish when testing looks good. Rules JSON is optional to view under Advanced.
- Inbound routes — NiteWtch assigns each route a unique alert address (alert-{your org id}-0001, 0002, … at your regional domain). That address picks the profile and creates an alert source—use Alert Sources to choose who gets called.
- Validate (test hub) — Production-fidelity test using the same engine as live ingest. Validate is free; optional AI compare costs 1 unit and is labeled reference-only.
- My alert types — Reusable alert-type definitions (classifier + fields). Attach them to a profile, then publish so live mail uses the same rules you validate here.
- Build alert types — Upload or paste a sample, let AI propose fields, generate one alert-type document, and save it to your library. No regex editing required.
- Training (optional) — Optional. Import many real emails to refine a profile before publish. Skip until your first profile works with one sample.
- Field glossary — Quick meanings for curation and rule mapping while you work in the studio.
In-app copy is sourced from the same content module as these pages.