Create Alert Channel
create_alert_channelCreate a place for alerts to be delivered: a webhook, an email list, or Slack.
This provisions a real outbound effect. Once a rule points at this channel, alert content leaves the platform to wherever you named — for a webhook, an HTTP POST to that URL. The payload carries the alert title (which is a span's error message, so it can contain model output), its labels, counts, and a sample of trace ids.
Needs the channels:manage capability.
name: a label for the channel, 1 to 120 characters.
channel_type: webhook, email, or slack.
url: for a webhook — the https URL to POST to.
recipients: for email — 1 to 20 addresses.
slack_channel_id: for Slack — a channel id from the connected Slack workspace.
Slack must be connected in the console first.
enabled: whether it starts receiving deliveries. Defaults to true.
workspace: optional workspace id, name, or org-name/workspace-name when the
same name occurs in two of your orgs (defaults to your default).
Example:
Send my alerts to this webhook.
{ "name": "create_alert_channel", "arguments": {
"name": "ops webhook", "channel_type": "webhook",
"url": "https://hooks.example.com/rius"
} }Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | ||
| name | Yes | ||
| enabled | No | ||
| workspace | No | ||
| recipients | No | ||
| channel_type | Yes | ||
| slack_channel_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |