Skip to content

Notification integrations

Configure a ti-ny.link notification handler for email, messaging or webhooks. Review channel requirements, connect supported features and test delivery.

Choose where notifications go

A notification handler stores the destination and settings for a notification channel. Create a handler, then select it wherever a feature in your account offers notification-handler controls.

Creating a handler alone does not enable notifications for every link, page or event. Review the notification options on the feature you want to use and test the complete workflow.

Available notification types

The notification-handler setup screen lists these types. Available handlers and the features that can use them depend on your account and plan.

ChannelNotification types listed in setup
EmailEmail
Team messagingSlack, Discord, Microsoft Teams, Google Chat
MessagingTelegram, SMS, WhatsApp
Custom workflowsWebhook, ntfy
Other destinationsX tweet, Internal notification

Check the fields shown for your chosen type before configuring the receiving service. An external account, integration or paid service may be required. A listed channel does not mean its third-party service is included in your ti-ny.link subscription.

Set up a handler

  1. Sign in and open Notification handlers from the account navigation.
  2. Open Create a new notification handler and enter a descriptive Name, such as “Campaign team notifications”.
  3. Select a Notification type and complete the fields shown for that channel. Use the receiving service’s current setup instructions for any required credentials or endpoint.
  4. For Email, complete the ownership confirmation sent to the address. Email ownership must be validated through the confirmation link before it can receive notifications.
  5. Save the handler with Create. Use Test integration when available to check the configured destination. This sends a test; use an address or channel you control.
  6. Open the feature that should send notifications. If it offers handler selection, choose your saved handler and save that feature’s settings.
  7. Trigger a controlled example of the intended action and confirm it reaches the correct destination. A successful integration test checks the connection; testing the feature also checks its notification configuration.

Before using it for a campaign

  • Check availability: review your account’s plan and the notification controls on the specific feature. The options in another account may differ.
  • Choose the audience: use a receiving channel whose members should have access to the notification’s contents.
  • Check both ends: confirm the handler is configured and selected, then check the receiving service for delivery.
  • Plan follow-up: agree who will review notifications and respond. A notification integration does not provide a shared support inbox or ticket-management system by itself.

If a notification does not arrive

Confirm that the intended handler is selected where applicable. For email, check ownership verification and the receiving mailbox’s spam folder. For other channels, check the required values against the receiving service’s instructions and review its access or delivery restrictions.

Use Test integration to help separate connection problems from the settings of the feature that sends the notification. If the connection test succeeds but the real action produces no notification, review that feature’s notification options and the action you tested.

Do not put webhook secrets, access tokens or private notification contents into public screenshots or shared troubleshooting notes.