---
title: "Echobell Direct: Personal Webhook Alerts Without Channel Setup"
date: 2026-03-05
description: "Echobell Direct gives you a personal webhook URL for instant notifications from scripts, CI jobs, and automation tools — no channel or template setup required. Here's how to use it."
author: Nooc
authorAvatarLink: /images/avatars/nooc.webp
authorLink: https://nooc.me
---

[Echobell Direct](/en/docs/direct) is a personal alerting mode that skips channel setup entirely. You create a Direct key, get a webhook URL, and POST a `title` + `body` to receive an instant notification on your device. No subscribers, no templates, no routing configuration.

This guide covers what Direct is, how to set it up, and when to use it instead of Channels.

## What is Echobell Direct?

Each Direct key generates a unique webhook URL (`/d/{token}`). Send a request to that URL and the notification arrives on your device immediately.

Use Direct when you need:

- Personal notifications from scripts, cron jobs, or CI pipelines
- Custom title and body per request rather than fixed templates
- Fast setup without configuring a full channel

If you need shared notifications, reusable templates, or conditional delivery, use [Channels via Webhooks](/en/docs/webhook) instead.

## Setup in 3 steps

### Step 1: Create a Direct key

Open Echobell, tap **Direct** in your channel list, and create a key. Name it after the service it belongs to (e.g. `CI Server`, `Cron`, `AI Tasks`).

### Step 2: Copy your webhook URL

Each key has a URL in the format:

```text
https://hook.echobell.one/d/YOUR_KEY_TOKEN
```

Treat this URL as a secret — anyone with it can send you notifications.

### Step 3: Send your first notification

```bash
curl -X POST https://hook.echobell.one/d/YOUR_KEY_TOKEN \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Deploy failed",
    "body": "api-service failed health check",
    "notificationType": "time-sensitive",
    "externalLink": "https://dashboard.example.com/deploys/123"
  }'
```

Full field reference: [Direct API](/en/docs/direct)

## Urgency levels

Direct supports `notificationType` so you can match urgency to the event:

- `active` — regular updates
- `time-sensitive` — important alerts that break through Focus mode
- `calling` — critical incidents (requires active premium subscription; falls back to time-sensitive otherwise)

See [Notification Types](/en/docs/notification) for full behavior details.

## Adding context to alerts

Include `externalLink` in the request body to attach a URL to the notification — useful for linking directly to a deploy log, dashboard, or pull request.

For AI agents and long-running async tasks, Direct is a straightforward way to get notified when the job completes rather than polling manually. See also: [WebhookMCP + Echobell](/en/blog/get-notified-with-webhook-mcp).

## Direct vs Channels

| | Direct | Channels |
|---|---|---|
| Audience | Personal only | Shared with teammates |
| Templates | Per-request content | Reusable, fixed templates |
| Setup time | Under a minute | Requires channel configuration |
| Conditions | Not supported | Supported |

Use Channels when alerts need to reach multiple people or when you want consistent formatting across a service. [Template docs](/en/docs/template) · [What is Echobell](/en/docs/what-is-echobell)

## Security practices

- Store Direct tokens in environment variables or a secrets manager, not in code
- Create one key per service so you can revoke individually
- Rotate tokens immediately if a URL may have leaked
- Reserve `calling` for true incidents — overuse causes alert fatigue

## FAQ

**Is Direct only for developers?** No. Anyone with a tool that can send HTTP requests can use it.

**Does Direct support GET requests?** Yes, but POST with JSON is recommended.

**What happens if my subscription lapses and I use `calling`?** It falls back to `time-sensitive` automatically.

---

Start with the [Direct guide](/en/docs/direct). When your workflow grows to need collaboration or templating, [Channels](/en/docs/webhook) are a straightforward next step.

## Related

- [Direct API docs](/en/docs/direct) — full field reference and examples
- [WebhookMCP + Echobell](/en/blog/get-notified-with-webhook-mcp) — notifications for AI task completion using Direct
- [How to bypass iOS Focus Mode](/en/blog/how-to-bypass-ios-focus-mode-for-critical-alerts) — choosing the right notification urgency
- [Zapier webhook notifications](/en/blog/zapier-webhook-notifications-to-phone) — non-developer automation workflows
- [Notification types](/en/docs/notification) — Normal, Time Sensitive, and Calling behavior