Channel: send messages
Several services in one channel
Several tools send to the same channel, each with its own name and key.
A channel doesn't have to belong to exactly one tool. Your "Server" channel can get alerts from the uptime monitor, the backup script and your CI. Each of these tools is a service in the channel, with its own name and its own key.

Server
Today, 3:12 AM
Backup script
Backup done
All 4 databases backed up, 2.3 GB.
Today, 9:41 AM
Uptime Kuma
api.example.com is not responding
No health check since 9:38 AM. Last status: 502.
When a service, when its own channel
| Own channel | Service in a channel | |
|---|---|---|
| In the list | one entry per tool | one entry for all |
| Push, sound, quiet hours | adjustable per tool | apply to the whole channel |
| Key | one per channel | one per service, removable individually |
| Good for | tools that have nothing to do with each other | several tools on one topic: server, shop, smart home |
Add a service
- Open the channel and tap the avatar or name at the top.
- Under Services, tap Add service.
- Choose how the tool sends: via Slack, Discord, ntfy or with your own code.
- Give the service a name, for example "Uptime Kuma". It will appear above its messages.
- Packlets shows the key or the finished address. Enter it in your tool. As soon as the first message arrives, Packlets shows Connected!. With Send test message from here you can check right away.
As with the channel, you only see the key this one time.
Sending
A service sends just like a channel, only with its own key. All calls accept it: POST /v1/push and the addresses for Slack, Discord and ntfy.
curl https://api.packlets.app/v1/push \
-H "Authorization: Bearer $PACKLETS_KEY_BACKUP" \
-H "Content-Type: application/json" \
-d '{"title": "Backup done", "text": "All 4 databases backed up, 2.3 GB."}'Then this happens:
- The message appears in the channel, with the service's name small above it.
- If the message has no
title, the push uses the service's name as the title. - The channel's activity log shows the service's name in front of each call.
- In the settings, each service shows when it last sent something.
Buttons and webhook
A channel has exactly one webhook URL. When someone taps a button or uses an element in a service's message, the event goes to this address, signed with the channel's key, not the service's. The event doesn't name the service. Your receiver recognizes the message by the message_id that the service got back when sending.
If a tool should react to buttons itself, give it its own channel with its own webhook URL.
Limits
| What | Limit |
|---|---|
| Services per channel | 20 |
| Calls | All services of a channel share the channel's limit: 60 per minute. Plus 300 per minute for your account. |
| Channel type | Channels only. An app has no services. |
Remove a service
In the channel's settings under Services, tap the service and confirm. Its key and addresses stop working immediately. Its earlier messages stay in the channel, with its name. The channel's key and the other services keep working.