Alerts — notifications & actions

Notifications

An alert’s destination controls how raised instances are surfaced.

"destination": {
  "frequency": "DAILY",
  "mediums": ["EMAIL"],
  "recipientIds": ["<user-uuid>"]
}

Field	Meaning
`frequency`	How often to notify: `IMMEDIATELY`, `HOURLY`, `DAILY`, `WEEKLY`, `MONTHLY`.
`mediums`	Channels: `EMAIL`, `SMS`, `WHATSAPP`.
`recipientIds`	Users to notify (by id).

Only EMAIL is active today; SMS and WHATSAPP are reserved for future use. An empty recipientIds means no explicit recipients are attached yet.

Actions from an alert

From a raised alert instance, you can launch an inventory plan directly — turning a signal into action:

Action	Launches
`restock`	A restock plan.
`rebalance`	A rebalance plan.
`markdown`	A markdown plan.

This closes the detect → classify → automate / act loop: tagging rules classify, alerts detect and notify, and from the alert you either act manually (these actions) or let a workflow react automatically to the same tags.

API integration

API recipes

Platform & data model

Decision layer (reference)

Operations & infrastructure

Ingestion specs (reference)

Workflows (reference)

Tagging rules (reference)

Alerts (reference)

Alerts — notifications & actions

Notifications

Actions from an alert

​Notifications

​Actions from an alert

Notifications

Actions from an alert