Telegram Bot Notifications
Deliver alerts and summaries to a Telegram user, group, or channel through a bot.
What it adds
A Telegram delivery channel that sends selected app notifications to a destination each user has proven they control.
What your agent is told to do
5
What your agent is told to do
5-
1
Add Telegram as a destination on the app's existing notification preferences rather than as a standalone feature, so a user's per-event choices, quiet hours, and unsubscribe controls apply to it unchanged.
-
2
Establish the destination by having the user start a conversation with the bot and present a short-lived code the app issued, then bind whatever chat that arrives from. Never let a user type a raw chat identifier into a form.
-
3
Keep the bot credential encrypted at rest and resolved only on the server at send time. It must not appear in configuration exposed to the browser, in logs, or in error reports.
-
4
Send from the app's background-job system with retries and backoff, and treat the throttling response as a signal to wait rather than to keep hammering.
-
5
Escape formatting markup in every value interpolated into a message. Content the app renders safely in HTML will break or misformat a Telegram message if it is passed through untouched.
Edge cases it handles
8
Edge cases it handles
8- A manually entered chat identifier can point at a stranger's conversation. Bind the destination only from a chat the user demonstrably initiated with a code the app issued and that expires quickly.
- Formatting markup in user-supplied text will either corrupt the message or cause the send to be rejected outright. Escape it for whichever formatting mode the message uses, and be consistent about which mode that is.
- A bot removed from a group, blocked by a user, or stripped of posting permission will fail permanently. Recognise these as terminal, stop retrying, mark the destination inactive, and prompt the user to reconnect.
- A send that times out may have succeeded. Carry a stable identifier per notification and record what was delivered, so a retry does not send the same alert a second time.
- The bot token is a full account credential. It must be encrypted at rest, redacted from every log and stack trace, and rotatable without redeploying.
- Messages have a length ceiling. Truncate long summaries at a readable boundary and link back into the app rather than sending a rejected payload.
- A group destination means everyone in that group sees the notification. Warn the user before binding a group, and never route personal or account-sensitive content to one.
- When Telegram is unreachable, the triggering action must still complete and the user must be able to see in the app that the notification is pending or failed.
Definition of done
8
Definition of done
8- A destination can only be bound from a chat the user initiated with a short-lived code.
- Telegram appears as a destination inside the existing notification preferences, honouring per-event choices.
- Bot credentials are encrypted at rest and absent from logs and client assets.
- Interpolated user content cannot break message formatting or cause a rejected send.
- Blocked bots, removed group memberships, and missing permissions mark the destination inactive without endless retries.
- Retried jobs never deliver the same notification twice.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Firebase Cloud Messaging
Firebase Cloud Messaging
Deliver push through Firebase with registration tokens that stay valid as devices change.
What it does
A Firebase-backed push channel with server-side token lifecycle management, consistent payload handling across platforms, and safe handling of the routes a notification opens.
How it works
- 1 Store one record per device registration, tied to the account signed in at the time, the platform it came from, and when it was last confirmed working, and let one account hold many of them.
- 2 Send from the app's existing background-job system with the provider credentials held server-side, and treat every send as a job that can be retried rather than work done inline during a request.
- 3 Decide, per notification type, whether the payload is meant to be displayed by the platform or handled by the app, and keep that decision the same on every platform. The same event behaving as a visible alert on one platform and a silent update on another produces bugs nobody can reproduce.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/firebase-cloud-messaging
OneSignal Push Notifications
OneSignal Push Notifications
Send push notifications to the right devices, with user preferences respected.
What it does
A push delivery path through OneSignal covering subscription registration, audience targeting, per-channel preferences, and delivery outcomes recorded against the app's own records.
How it works
- 1 Find the events the app already notifies on by email or in-app, and treat push as another channel for those same events rather than a separate notification system with its own triggers.
- 2 Record the link between a push subscription and an account on the server, established at sign-in and severed at sign-out, so a device that changes hands does not keep receiving the previous user's notifications.
- 3 Hold the provider credentials server-side and send every message from the app's existing background-job system, so a slow or failing provider never blocks a web request.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/onesignal-push-notifications
Mailgun Transactional Email
Mailgun Transactional Email
Send transactional email through Mailgun without losing bounce and complaint state.
What it does
A Mailgun delivery path bound to the correct region and sending domain, with durable suppression and event handling.
How it works
- 1 Put Mailgun behind the app's existing mail layer as one adapter. It is an alternative to the other transactional email integrations, not an addition; whichever adapter is in place, the template contract and suppression handling above it are unchanged.
- 2 Bind the region and sending domain in server-side configuration and validate at startup that they are consistent. A credential issued in one region will simply not work against another, and the failure looks like an authentication problem rather than a configuration one.
- 3 Check the suppression state for an address before a message is queued, not after the provider rejects it, so bouncing and complaining addresses stop consuming send attempts.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mailgun-transactional-email
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.