Add a destination
1
Open Notification destinations
Switch to the organization you want, open the account menu, and choose
Notification destinations.
2
Choose a delivery type
Click Create on Email, Slack, Discord, or Webhook.
3
Enter the connection details
Give the destination a recognizable name. For Slack, pick a channel from the
dropdown (see Connect Slack below). For the other types,
enter an email address, a Discord webhook URL, or a generic webhook URL.
4
Create and test it
Click Create destination, open its action menu, and choose Test. A
successful test confirms that TinyAnalytics can reach it.
Connect Slack
Connecting a Slack workspace lets you choose a channel from a live list, and lets one connection serve as many channels as you need.1
Add TinyAnalytics to Slack
On Notification destinations, click Add to Slack, choose your workspace, and
approve the requested permissions. TinyAnalytics asks only for what it needs to list
channels and post messages — it cannot read your conversations.
2
Invite the bot to the channels you want
In Slack, run
/invite @tinyanalytics in each channel you plan to notify. The channel
picker marks channels the bot has not joined, and messages to those channels will fail
until you invite it.3
Create a Slack destination
Click Create on Slack, name the destination, and pick a channel. Private channels
appear with a lock icon if you can see them in Slack.
Disconnecting a workspace
Disconnect a workspace from the Slack workspaces card. You must first remove or repoint any destinations still using it — TinyAnalytics will tell you which ones.Using a Slack incoming webhook instead
If Add to Slack is not available — for example on a self-hosted instance without a Slack app configured — Slack destinations use an incoming-webhook URL instead. Create the webhook in Slack, then paste the URL into the destination.Correction (August 2026). Earlier versions of TinyAnalytics showed an optional
Channel field on Slack webhook destinations, and this page described it. That field
never worked: Slack ignores a channel sent with an incoming-webhook message, so
notifications were always delivered to the webhook’s own channel. The field has been
removed. If you had filled it in, your notifications were going to the webhook’s channel,
not the one you typed — check that it is the channel you expect, and use Add to Slack
if you need to route to a different one. No configuration is needed to pick up the fix.
Where each destination is used
Scheduled reports use their own organization-member recipient list and are not connected to notification destinations.
Manage existing destinations
The Active destinations table shows each destination’s name, type, connection detail, and status. Open the action menu to:- Disable or Enable delivery without deleting the configuration.
- Test an enabled destination.
- Edit its name, connection details, or Slack channel.
- Delete it permanently.
Who can manage destinations?
Organization members can read the destinations available to features they can access. Only organization owners and admins can create, edit, enable, disable, test, or delete them. Webhook credentials are masked for members who cannot manage the organization.Verify
Open the destination’s action menu and choose Test. The setup is complete
when TinyAnalytics reports Test notification sent and the message arrives
at the configured email address, Slack channel, Discord channel, or webhook.
For a Slack destination, confirm the message arrives in the channel named on the
destination row. If the test reports that the bot is not in the channel, run
/invite @tinyanalytics there and test again.Related
Workflows
Trigger notifications from pageviews, events, errors, and autocapture.
Analytics alerts
Notify your team when a metric crosses a threshold.
Uptime monitoring
Open incidents after repeated endpoint failures.
Roles & permissions
See what organization owners, admins, and members can manage.