Skip to main content

Channels

Channels define where notifications are delivered. Configure them via the UI, CLI, or API to route events to:

  • Slack: Receive messages in specific channels for approvals or alerts.
  • HTTP Webhooks: Programmatically process events with custom logic (e.g., auto-approve deployments during business hours).
  • GitHub and GitLab: Integrate with your GitHub or GitLab workflows as part of your service provisioning process.
  • Azure: Connect Azure Pipelines to your service provisioning process.
  • Agent: Use this channel to send service actions from nullplatform to your runner.

You can find full examples and detailed request formats for each channel in our API reference.

Manage notification channels from the UI

You can create and configure notification channels directly from the UI to track operations on entities.

Go to Platform settings > Channels and click + New channel.

Slack​

To receive notifications on Slack, you'll need to:

  1. Install nullplatform's Slack application
    Go to https://<your-org-slug>.app.nullplatform.io/integration and click Connect Slack to authorize the application.

  2. In Slack, add the nullplatform application to the channels where you want to receive notifications
    You can do this with the slash command /invite @nullplatform.

  3. Set notification channels for your teams, applications, etc.
    To create a notification channel for Slack, you can use the nullplatform CLI or send a POST request to create a channel.

tip
  • Set up a notification channel for the whole organization to be sure that notifications always reach some channel.
  • If multiple teams need notifications (e.g., different approvers per team), create a separate notification channel for each team by specifying the corresponding NRN.

Example request:

np notification channel create \
   --body '{
   "nrn": "organization=1:account=2:namespace=3:application=4",  // The NRN of the resource where the action will apply.
   "source": [
      "approval"
      ],
   "type": "slack",
   "configuration": {
      "token": "the-slack-token",
      "channels": [
         "my-organization-private-channel"
      ]
   },
   "filters": {
      "action": "deployment:create"
   }
}'

This endpoint returns an ID that you can later use to reconfigure or delete the notification channel using PATCH or DELETE requests.

Once configured, you’ll receive Slack messages to approve or deny requests.

Here's an example:

Slack notification

HTTP webhook (programmatic)​

To have programmatic control over your notifications, you can use HTTP webhooks to allow systems to programmatically respond to approval requests.

This lets you implement custom logic—such as "approve this deployment only if it's business hours and the card is marked as verified by QA".

Configure nullplatform to send POST requests to your custom endpoint using either the our API or the CLI.

Authorization

Embed any token or secret directly in the URL or headers. We currently do not support a refresh token scheme.

np notification channel create \
   --body '{
      "source": ["approval"],
      "nrn": "organization=1",
      "type": "http",
      "configuration": {
         "url": "https://yourdomain.com/your-configured-endpoint",
         "headers": {
            "Authorization": "Bearer the-token"
         }
      }
   }'

After setting up your custom notification channel, you'll start receiving requests like these:

POST https://yourdomain.com/url-you-configured
{
  "id": 123,
  "source": "approval",
  "created_at": "2022-12-19T20:37:42.109Z",
  "notification": {
      "approval_id": 1234,
      "approve_url": "https://api.nullplatform.com/approval/1234/approve?token=the-token",
      "deny_url": "https://api.nullplatform.com/approval/1234/deny?token=the-token",
      "requested_by": {
        "user_id": 1,
        "email": "alex.doe.developer@yourdomain.com",
        "first_name": "alex",
        "last_name": "doe",
        "avatar": null
      },
      "action": "deployment:create",
      "details": {...}
  }
}