live-notify
Bridge togo live agent replies to the notifications system — Slack, Discord, web-push, FCM, Pusher, mail — via one live.Channel. For togo-framework/live.
Extends live
togo install togo-framework/live-notify- ai-agents
- discord
- golang
- live-agents
- notifications
- plugin
- slack
- togo
Readme
togo-framework/live-notify
Bridge togo live agent replies out through the notifications system — one bridge, zero per-provider live drivers.
Install
Usage
live-notify registers three live egress channels — slack, discord, and notify — that route an agent's reply through the togo notifications system. A conversation on one of these channels is delivered by the existing notifications-* driver, so there's no per-provider live code to write.
Blank-import this bridge alongside the notifications channel driver(s) you want:
Then set a conversation's channel and provide the driver's webhook env:
- Set a conversation's
channelto"slack"or"discord"to deliver each agent reply through that notifications channel. - Set it to
"notify"to fan out to every channel listed inLIVE_NOTIFY_CHANNELS(CSV), e.g.LIVE_NOTIFY_CHANNELS=slack,discord. - Configure the underlying driver as usual —
SLACK_WEBHOOK_URLfornotifications-slack,DISCORD_WEBHOOK_URLfornotifications-discord, etc.
Any registered notifications channel works the same way — notifications-webpush, -fcm, -pusher, -mail — with no extra live code. If the notifications plugin isn't installed, delivery is a no-op.
See docs/usage.md for an end-to-end example.
💎 Premium sponsors — ID8 Media · One Studio