Notification Integration Plugins
AVideo can notify external chat services after a new video is published. These plugins send metadata to a webhook or bot; they do not upload the video file itself.
| Plugin | Connection |
|---|---|
DiscordNotify |
Discord incoming webhook; can also set bot name/avatar/footer image. |
SlackNotify |
Slack incoming webhook. |
SlackBot |
Slack bot token and channel subscriptions; requires the current bot scopes shown by Slack/plugin. |
- Create the webhook or bot in the official Discord/Slack administration interface.
- Limit it to the intended server/workspace and channel.
- Copy the HTTPS webhook URL or bot token into the matching AVideo plugin.
- Publish a disposable test video and confirm the message and link.
- Check what happens for unlisted, private, scheduled and failed uploads before production use.
Webhook URLs and bot tokens are credentials. Anyone who obtains one may be able to post as the integration. Never put it in a screenshot, public issue, browser JavaScript or video description.
No message appears: confirm the video reached the event/status expected by the plugin, then inspect AVideo logs and provider delivery/audit logs.
The same video is announced twice: check whether more than one notification plugin or retrying worker is enabled.
The link opens a denied video: external chat users still need the normal AVideo permission, group, password or purchase. A notification does not bypass access control.
A token was exposed: revoke/rotate it at Discord or Slack immediately and update AVideo.
Provider APIs, scopes and rate limits change. Use their current official dashboard rather than copying old scope names from a screenshot.
| Plugin | Added value |
|---|---|
| Notifications | Manages supported e-mail, push, and site notifications. |
| UserNotifications | Stores and displays notices inside AVideo. |
| Socket | Provides real-time delivery for supported features. |
