
Argent alerts by email
Argent Strategic Intelligence sends alerts and budget owner notices through your own mail relay. Mail only leaves encrypted: a relay that cannot encrypt the connection gets nothing.
What Argent sends by email
Email reaches people who do not sit in a chat tool: budget owners, auditors, finance.
| Event | When it fires |
|---|---|
Budget threshold budget.threshold | A spend budget crosses 50, 75, 90 or 100 percent of its ceiling. One alert per budget, per period, per level. |
Agent budget alert budget.agent_alert | One agent's own budget crosses 70, 90 or 100 percent, when an operator turned that alert on for the agent. It fires once per crossing. |
Skill approval requested skill.approval_requested | An agent loaded a skill version nobody has reviewed, and, with auto-submit turned on, Argent sent it for approval. A skill is a packaged set of instructions an agent pulls in. Its text is never included. |
Agent note mention agent.note_mention | Someone @mentioned colleagues in a note on an agent. The alert names the agent, the author, the people mentioned and the owner, never the note text. |
Audit chain break audit.chain_break | Only for an admin who subscribed under Alert me on a break: mailed to that admin's own address, never to this channel's To list. |
Budget owner notice budget.owner_notice | Opt-in only. An admin changed a budget and ticked "tell the owner". The reason text is never included. |
Leave the event list blank and the channel carries every event except the opt-in owner notice. Name any events and it carries only those. An event name Argent does not know is rejected when you save.
Two more ways email is used:
- Tell the owner. When an admin saves a budget and ticks "tell the owner", Argent emails the agent's owners from the directory. The notice never carries the reason text, is rate limited per tenant, and never blocks or undoes the budget change.
- Alert me on a break. A SuperAdmin, TenantAdmin or Auditor can subscribe to the audit verifier's findings (a chain break, a missed verification schedule, a trust-anchor mismatch) by email. Each alert is sent once.
How it connects
Argent hands each message to the SMTP relay you name and requires STARTTLS.
STARTTLS is the standard way to encrypt an SMTP connection (RFC 3207).
- Pick the relay that should send the alerts and the sender address.
- Store its credential in the tenant vault as
username:password, or leave it empty for a relay that needs no login. - In the Argent console, open Integrations > Notifications, add Email and enter the relay, sender and recipients.
- Tick the live-send option and press Test. Argent sends one sample alert marked
TEST -through the same path a real alert takes, so you see it arrive. Without the live-send option, Test checks the configuration only.
Wiring many tenants? argentctl integrations apply reads one JSON document, stores the secrets in the tenant vault, then creates, connects and tests each channel. It can be run again safely, has a --dry-run and never prints a secret. argentctl integrations hosts prints the outside hosts the document needs, so the firewall can be opened precisely.
What you configure
| Setting | What goes in it |
|---|---|
| SMTP relay | host:port of your mail relay. |
| From | The sender address. |
| To | One or more plain addresses. No display names or comments, so an address cannot smuggle in a second recipient. |
| Credential | A reference to username:password in the tenant vault. Empty means no login. |
| Events | Blank for every event except the owner notice, or the exact events this inbox should get. |
There is no clear-text setting. STARTTLS is always required.
What lands in the inbox
One message per send to all the recipients, with a subject that says what happened.
- The subject reads like
Argent: Budget at 90%: Payments team. A test readsArgent: TEST - ..., so nobody mistakes it for a real alert. - Names are resolved by Argent before the mail leaves. When a name cannot be resolved it is left empty, never guessed.
- The body lists the details and ends with the event type and id.
Delivery and guard rails
Mail leaves encrypted and authenticated, or it does not leave.
- STARTTLS required. A relay that does not offer it is refused and nothing is sent, because the message and the login would cross the network in clear text.
- No silent downgrade. When a credential is configured and the relay does not offer a login, Argent refuses rather than mailing unauthenticated. A credential is only ever sent inside the encrypted connection.
- No header injection. Every header value is checked for line breaks and control characters. A value that carries one is refused, not cleaned, so text inside an alert can never add a header or a recipient.
- Bounded. One send has 20 seconds end to end. Budget, skill and note emails are tried once; audit-break emails for subscribed admins are queued and retried until delivered or parked as failed.
- Secrets are references. The SMTP credential lives in the tenant vault. Argent's configuration holds only a reference to it. It is resolved when the channel connects and is never stored in configuration, written to a log or shown back in the console.
- Outbound guard. Every connection is checked at dial time. Addresses on the Argent host itself and cloud provider metadata addresses are refused. A receiver on a private network is reachable only when your operator adds it to the deployment's outbound allowlist (
ARGENT_CONNECTOR_EGRESS_ALLOWLIST). A tenant admin cannot open that by typing an internal address into a form.
Where it fits
The alerts come from the parts of Argent that hold money, skills, owners and evidence.
- AI Spend Caps and the goal Budget and Token Spend: the budgets behind every threshold alert.
- Audit and Accountability and One-Click Audit Evidence: the signed record the verifier watches.
- Threat Defense: skill review, the source of skill approval alerts.
- Agent Identity and Ownership: every agent has a human owner, the person these alerts reach.
Other alert channels: Slack, PagerDuty, Signed webhook. Approvals that need a ticket go to ServiceNow or Jira Service Management.
Need a channel that is not listed? Request a connector from the Integrations catalog in the console. See every integration or book a demo.
Want this running on your own use cases?
Book a demo