---
title: Channels
description: How Trigv channels work — slugs, routing, subscriptions, and dashboard management.
---
# Channels

Channels organize alerts — send to `billing`, `ci`, or `general` and only people subscribed to that channel get the push.

## How it works

<ol>
  <li>You pick a channel when sending an alert (in Zapier, the dashboard, or the API).</li>
  <li>Trigv delivers to devices subscribed to that channel in the mobile app.</li>
  <li>Your API key controls <em>who can send</em>; the channel controls <em>who receives</em>.</li>
</ol>

## Step 1 — See your channels in the dashboard

<ol>
  <li>Sign in at <a href="https://app.trigv.com">app.trigv.com</a>.</li>
  <li>Click <strong>Channels</strong> in the sidebar.</li>
  <li>Every workspace starts with a <code>general</code> channel.</li>
</ol>

## Step 2 — Create a channel (optional)

<ol>
  <li>On the Channels page, click <strong>Create channel</strong>.</li>
  <li>Enter a name — e.g. <code>Deploys</code> or <code>Sales</code>.</li>
  <li>Trigv generates a slug (e.g. <code>deploys</code>) — use this slug when sending alerts.</li>
</ol>

## Step 3 — Subscribe on your phone

<ol>
  <li>Open the Trigv app.</li>
  <li>Go to channel settings (or subscriptions).</li>
  <li>Turn on the channels you want alerts for.</li>
  <li>If you're not subscribed to a channel, events still ingest but <code>target_device_count</code> may be zero.</li>
</ol>

## Using channels in integrations

Include the slug in your alert payload:

```
{
		"channel": "billing",
		"title": "New subscription",
		"level": "success"
}
```

## Good to know

- Channel slugs are not secret — protect access with your API key.
- Use different channels to separate CI, sales, and personal automations.
- You can mute a channel in the app — alerts still sync to your feed silently without deleting the channel.
