
Argent alerts to any webhook
Argent Strategic Intelligence sends its alerts as JSON to any HTTPS endpoint you run, so your own automation can act on them. Add a signing key and every delivery proves it came from Argent.
What Argent sends to your endpoint
The same alerts the other channels carry, as structured JSON your code can act on.
| 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 when an admin picks this webhook under Alert me on a break. |
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.
Alert me on a break. A SuperAdmin, TenantAdmin or Auditor can also subscribe a webhook to the audit verifier's findings (a chain break, a missed verification schedule, a trust-anchor mismatch). Those deliveries retry with doubling backoff for about an hour before they are parked as failed.
How it connects
Argent sends one HTTPS POST per alert to the URL you give it.
- Stand up an HTTPS endpoint that accepts a JSON POST.
- Optional but recommended: create a signing key and store it in the tenant vault.
- In the Argent console, open Integrations > Notifications, add Webhook, enter the URL and point it at the signing key.
- 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 |
|---|---|
| URL | Your endpoint. It must be https://: plain HTTP would expose the alert and let anyone on the path alter it. |
| Signing key | Optional. A reference to the shared HMAC key in the tenant vault. |
| Events | Blank for every event except the owner notice, or the exact events this endpoint should get. |
What your endpoint receives
A flat JSON body: `type`, `id` and `timestamp` (RFC 3339, UTC) at the top, then a body for that type.
- Switch on
typeand ignore anything you do not recognise. New event types can then be added without breaking an endpoint written a year ago. - Key on
idto process each alert once. A retry of the same alert carries the same id. - Every money field ships twice: the exact integer in micro-dollars for anything that computes, and a ready string such as
$847.25for anything that displays, formatted by the same rule as the console. - Names are resolved by Argent, with ids alongside. A name that cannot be resolved is left empty, never guessed.
| Header | What it carries |
|---|---|
X-Argent-Event-Type | The event type, so you can route without parsing the body. |
X-Argent-Timestamp | The delivery time in Unix seconds. |
X-Argent-Signature | v1= and a hex HMAC-SHA256 digest, when a signing key is set. |
How to verify a delivery
The signature covers the timestamp and the exact body bytes, so a captured delivery cannot be replayed later with a fresh timestamp.
- Read the raw request body before parsing it. Re-serialized JSON produces different bytes and a correct alert would fail.
- Reject the delivery if
X-Argent-Timestampis outside your replay window. Argent's reference verifier uses five minutes. - Compute HMAC-SHA256 (RFC 2104) with your signing key over
<timestamp>.<raw body>, hex-encode it, and compare it with the value afterv1=using a constant-time comparison.
Argent signs again on every retry, so a retry minutes later still passes a five-minute window.
Delivery and guard rails
One alert path, built so a bad endpoint cannot hurt anyone else.
- Retried: network errors, timeouts, server errors (5xx), too-many-requests (429) and request-timeout (408) replies. Each means the endpoint has not judged the alert yet. Up to three attempts, 10 seconds each, spaced out at random so a struggling endpoint is not hit by every retry at once.
- Not retried: any other 4xx, such as 401, 403, 404 or 422. The endpoint has looked and refused, so a rotated secret or a deleted endpoint shows up at once instead of hiding behind retries.
- Same event, same id: every retry of one alert carries the same event id, so a duplicate is detectable.
- Never in the way: alerts go onto a bounded queue. One endpoint that hangs can never stall budget checks for any other team, and a dropped alert is counted in the
argent_notify_deliveries_totalmetric that your Prometheus and Grafana stack can alert on.
- Secrets are references. The signing key 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.
- Budget owner notices: when an admin saves a budget and ticks "tell the owner", Argent can copy a shared webhook channel, without ever blocking or undoing the budget change.
Other alert channels: Slack, PagerDuty, Email (SMTP). 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