Route pins to Slack, Discord and webhooks

Pogpin is the front door for feedback. Notification channels push the moments that matter out to where your team already watches — without turning a chat channel into a firehose.

Add a channel

Open your notification settings and add a channel. Pogpin delivers to a broad set of providers out of the box:

Slack · Discord · Telegram · Microsoft Teams · Lark · Email · Gotify · ntfy · Pushover · custom webhook

Most are a paste-in webhook URL (Slack, Discord, Teams, Lark, Gotify, ntfy, custom); Telegram and Pushover use their own token setup; email delivers to an address. Webhook URLs are validated server-side to block requests at internal network addresses, so a mistyped or malicious URL can’t be used to probe your infrastructure.

Route by event, not firehose

The point of channels is selective routing — each channel subscribes only to the events you choose:

• issue.created — a new pin was dropped
• issue.comment_added — someone replied on a pin
• issue.comment_mentioned — you were @mentioned
• issue.status_changed · issue.priority_changed · issue.assignee_changed
• document.comment_added — a comment on a published doc
• changelog.published — you shipped a release note

A quiet, useful setup might send issue.created for high-priority pins to #bugs in Slack, route issue.comment_mentioned to each person’s Telegram, and leave everything else inside Pogpin until someone triages it.

Build your own with a custom webhook

Need something we don’t have a native channel for? Add a custom webhook channel and Pogpin will POST the event payload to your endpoint. Use it to trigger CI, sync to an internal warehouse, or forward into a tool of your own — the same per-event routing applies, so you only receive what you subscribe to.

Tip: start with one Slack route for new pins and one mention route. Add more only when you feel a gap — over-wiring channels on day one is the fastest way to notification fatigue.