Skip to content
Webhooks and Destinations

Webhooks and Destinations

Availability: Email destinations are available on every plan. Slack, Discord, and Microsoft Teams destinations require Starter or higher, and custom webhooks require Professional or Agency.

A destination is a place Shortn can send events — a Slack channel, a Discord channel, Microsoft Teams, a custom webhook, or an email address. Destinations are created at the workspace level and used by reports and alerts to deliver messages.

Destination types

TypeWhat it doesPlan
EmailSend to one or more email addressesAll plans
WebhookPOST to a custom webhook URLProfessional+
SlackPost to a Slack channel via incoming webhookStarter+
DiscordPost to a Discord channel via webhookStarter+
Microsoft TeamsPost to a Teams channel via webhookStarter+

Which types you can add depends on the workspace owner’s plan. See plans.

Add a destination

Workspace owners, administrators and collaborators can manage destinations.

  1. Go to Reports and choose Destinations.
  2. Choose Add destination.
  3. Give it a Name and choose the Type and the workspace.
  4. For Slack, Discord, Microsoft Teams, or a custom webhook, paste the Webhook URL. For email, enter one or more addresses, separated by commas.
  5. Optionally pick one or more Teams. Leave it on No team (Workspace-wide) to make the destination available to the whole workspace.

The destination is then available to pick when you create a report or alert. A destination limited to teams can only be used by reports and alerts for those teams; see which links a report or alert covers.

Test a destination

Choose Send test message on a destination to check that it works. Shortn sends a short test message and tells you whether it was delivered, or why not. You can send one test every 30 seconds per destination.

To see how a whole report or alert looks in its destinations, use Send test on the report or alert.

Custom webhooks

A webhook URL must use https:// on the standard port (443) and point to a public address; private and internal addresses are refused.

Shortn sends each message as an HTTP POST with a JSON body and Content-Type: application/json. Any 2xx answer counts as delivered; anything else, or no answer within 10 seconds, counts as a failed attempt (see delivery).

Webhook requests aren’t signed. Treat the URL as a secret: use one that’s hard to guess, for example with a random token in the path, and don’t share it.

Last updated on