Skip to main content

Notifications

The notifications system lets you automate workflows, build audit trails, and get real-time alerts for any change that happens in nullplatform — from new deployments to parameter approvals.

Notifications are fully configurable: you decide where they go, what they contain, and when they’re sent.

💡 Tip: Notifications integrate seamlessly with other platform features like deployments, parameters, and telemetry, making it easy to observe, control, and automate everything from a single source of truth.

How it works​

Every notification follows the same flow:

  1. An event occurs — a CRUD operation, approval request, or telemetry update triggers an internal event.
  2. Filters decide whether the event should generate a notification.
  3. Channels deliver the resulting event to notification systems such as Slack, webhooks, or your agent.
  4. Event payloads define the JSON structure sent to each destination.

This architecture enables deep integration with your organization’s tools and infrastructure.

Key components​

Channels – Where notifications go​

Channels define the destination for notification data.
You can route events to:

  • Slack for team alerts and approvals.
  • HTTP Webhooks to trigger custom automation logic.
  • Agent to execute actions inside your own infrastructure.
  • GitHub / GitLab / Azure to integrate approvals and deployment events with your CI/CD workflows.

Filters – Which notifications are sent​

Filters control what gets sent to each channel.
They use MongoDB query syntax to express conditions like:

"filters": {
  "$or": [{ "action": "scope:stop" }, { "action": "scope:delete" }]
}

With filters you can:

  • Send approval requests only for certain namespaces.
  • Exclude “deployment:create” events from general audit notifications.
  • Target alerts by entity, team, or environment.

Event payloads: What the notification contains​

Each notification carries a structured JSON payload describing the triggered event.
This payload mirrors nullplatform’s public API responses, so you can parse and enrich it easily in external systems.

You can inspect, list, or resend notification events for debugging or replaying failed deliveries through the Notification Events API.

Common use cases​

  • Approval workflows — Automatically post approval requests to Slack or a webhook endpoint.
  • Auditing — Keep a complete record of entity changes and API interactions.
  • Custom automations — Execute actions in your infrastructure via Agent channels.
  • Monitoring — Stream deployment or telemetry data to external observability tools.

Managing notifications​

You can create and manage notifications through:

  • UI: Go to Platform settings → Notifications.
  • CLI: Use np notification. (See our CLI docs)
  • API: Use the Notification API.

Best practices​

  • Start with organization-wide channels to ensure coverage.
  • Use specific filters per team, namespace, or application to avoid noise.
  • Test your configuration using resend events before going live.

Next steps​