Channel Routing: Scoped Notifications Per Team

import { Steps } from ‘@astrojs/starlight/components’;

Channel Routing

Large organizations have multiple teams managing different parts of their cloud infrastructure. Channel routing lets you send scoped notifications to different Slack or Teams channels — each team sees only the costs, anomalies, and recommendations relevant to them.

How it works

You create channel configurations in the Xplorr console. Each config maps a Slack or Teams channel to a scope:

Scope type	What it filters	Example
All	No filter — full org data	`#cloud-costs` gets everything
Accounts	Specific AWS/Azure/GCP accounts	`#platform-team` gets only the production AWS account
Tags	Cost allocation tag filters	`#data-team` gets resources tagged `team:data`
Services	Specific cloud services	`#infra-alerts` gets only EC2, EKS, and RDS

Each channel config also controls which notification types it receives:

Digest — daily cost summary
Alerts — alert rule triggers
Anomalies — cost spike notifications
Budgets — budget threshold alerts
Recommendations — new optimization suggestions

Setting up channel routing

Go to Settings → Integrations → Channel Routing in the Xplorr console.
Click Add Channel and select the Slack or Teams channel.
Choose the scope type and configure the filter:
- For Accounts: select one or more cloud accounts from the dropdown
- For Tags: enter tag key-value pairs (e.g., team:platform)
- For Services: select services (e.g., EC2, RDS, S3)
Toggle which notification types this channel should receive.
Set the channel’s timezone (used for digest scheduling).
Click Save. You can test it with the Send Test button.

Default channel

One channel per org can be marked as the default. The default channel receives all notifications that aren’t routed to a more specific channel. If no channels are configured, notifications fall back to the org’s webhook URL (if set).

Examples

Multi-team setup

Channel	Scope	Notifications
`#cloud-costs`	All	Digest, Weekly Summary
`#platform-alerts`	Accounts: `prod-aws`, `prod-gcp`	Anomalies, Alerts, Budgets
`#data-team-costs`	Tags: `team:data`	Digest, Recommendations
`#finance-review`	All	Weekly Summary only

Single-team setup

If you only have one team, just configure one channel with scope “All” and enable all notification types. This is equivalent to the basic Slack webhook setup, but with richer interactive messages via the Bot API.

API

Channel configs can also be managed via the API:

GET    /api/v1/channels          — List channel configs
POST   /api/v1/channels          — Create a channel config
PATCH  /api/v1/channels/:id      — Update a channel config
DELETE /api/v1/channels/:id      — Delete a channel config
POST   /api/v1/channels/:id/test — Send a test notification

All endpoints require admin role.

Daily Cost Digest — What gets sent to each channel
Notifications — Email and Slack notification preferences
Team Management — Roles and per-account access control