Notifications that tell the right people, not everyone
Slack, Discord, Telegram, Teams, Lark, email, Gotify, ntfy, Pushover or a custom webhook — each channel subscribes to the events it actually needs, so alerts stay signal instead of noise.
There are two ways to fail at notifications. Send too few, and issues sit for a week because nobody knew. Send everything to one channel, and people mute it in a fortnight — after which you are back to sending too few, just with extra steps.
The fix is not a smarter digest. It is letting each destination subscribe only to what it is responsible for.
The channels
Pogpin delivers to Slack, Discord, Telegram, Microsoft Teams, Lark, email, Gotify, ntfy, Pushover and custom webhooks. The last one matters more than the length of that list: a webhook is the escape hatch for anything not on it — your own bot, an internal dashboard, a workflow tool, or a tracker you still run.
Per-event routing
Each channel picks its own events: a new pin, a comment, an @mention, a status change, a priority change, an assignee change, and more. That is what makes the difference between an alert and a nag.
A shape that works for most teams:
| Destination | Subscribes to | Why |
|---|---|---|
#project-feedback in Slack |
new pins | the team sees incoming work without opening the board |
| A private channel or DM | @mentions, assignee changes |
it is addressed to a person, so it should reach that person |
| The client’s shared channel | status changes to Done | they hear what shipped, not every internal step |
| Custom webhook | everything | your own pipeline decides what to do with it |
Two things fall out of this. Nobody has to mute a channel to stay sane, and the client channel stops leaking internal churn.
It works the same from every surface
A pin left on a PDF page, a video frame or an image raises the same events as a pin left on a website — same statuses, same board, same routing. So a design review on a deck and a QA pass on staging both land where the team already watches, without a second integration to configure.
Webhooks: what you actually get
A custom webhook receives the raw event, so you can build on top of it: forward serious pins into a heavyweight tracker, page someone when a launch-blocking issue appears, or write your own digest. Pogpin shows a payload preview — destination, headers, payload and the template tokens available — so you can see the exact shape before you write a line of code, instead of triggering test events blindly.
Releases go out the same way
Notification channels are not only for pins. When you publish a release from the changelog, it fans out to the same channels — see release notes nobody has to write. The loop closes: the client reports a bug in a review link, and hears in their own channel that it shipped.
Setting it up
- Add a channel in the project’s notification settings and connect it.
- Choose its events. Start narrow — new pins for the team channel, mentions for people.
- Check the payload preview if it is a webhook.
- Revisit after a week. If a channel is being ignored, it is subscribed to too much.
The step-by-step is in route pins to Slack, Discord and webhooks.