Create a new alert configuration
Creates a new alert with rules, scope, and destination configuration. Requires Bearer token authentication.
Authorizations
Static internal-ops token used by the data platform and internal cron jobs (e.g. zombie-run sweep). Validated via requireBearerToken inside the handler against a service-specific environment variable.
Body
Human-readable alert name
1Organization ID the alert belongs to
1Tag-based conditions that determine which entities trigger this alert (at least one required)
1Restrict alert evaluation to these brand IDs; omit for all brands
Granularity at which the alert is evaluated (e.g. VARIANT, PRODUCT, BRAND)
SHOP, BRAND, PRODUCT, VARIANT, INVENTORY_ITEM Restrict alert evaluation to entities in these collection IDs
Optional free-text description of the alert's purpose
How often the alert is evaluated (DAILY, WEEKLY, etc.)
IMMEDIATELY, HOURLY, DAILY, WEEKLY, MONTHLY Whether the alert is active and will be evaluated; defaults to true
Notification channels for delivery (e.g. EMAIL, SLACK)
Restrict alert evaluation to these product IDs; omit for all products
User IDs that should receive alert notifications
Restrict alert evaluation to these store IDs; omit for all stores
How multiple tag rules are combined: AND requires all tags, OR requires any tag
AND, OR Restrict alert evaluation to entities matching these taxonomy filters

