OneSignal Push Notifications
Send push notifications to the right devices, with user preferences respected.
What it adds
A push delivery path through OneSignal covering subscription registration, audience targeting, per-channel preferences, and delivery outcomes recorded against the app's own records.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Ask for the browser or device permission at a moment the user has chosen, after they have enabled push in settings, and never on first page load. A denied permission is usually permanent and cannot be re-prompted.
-
5
Do not treat the provider's segments as the source of truth for who should be notified. Decide the audience from the app's own data and preferences, then address the send to specific subscriptions, or overlapping segments will deliver the same event two or three times.
Edge cases it handles
8
Edge cases it handles
8- A shared or borrowed device can accumulate subscriptions for more than one account. Bind a subscription to the account that was signed in when it was created and clear it at sign-out, rather than merging every subscription seen on that device into one user.
- Users who have muted a category, or muted notifications entirely, must be filtered out before the send is composed. Push must obey the same per-channel preferences and quiet hours as email, not bypass them.
- The provider will report subscriptions that have expired, been revoked, or belong to an uninstalled app. Mark those inactive on the next failure rather than retrying them forever, and treat a duplicate registration for the same device as a replacement rather than a second recipient.
- A notification that deep-links into the app must re-check permission when it is opened. The recipient may have lost access to the record, or the record may have been deleted, so the destination needs a graceful fallback instead of an error page.
- The same event reaching a user through two overlapping audiences must be collapsed into one delivery. Deduplicate on the event identifier and the recipient before anything is handed to the provider.
- When the provider is unreachable or rate-limits the send, queue and retry with increasing delays rather than dropping the notification, and stop retrying anything time-sensitive once it is no longer worth delivering.
- Notification content is visible on a lock screen. Keep names, amounts, and message bodies out of the payload unless the user has opted into showing them.
- Some browsers and platforms do not support push at all. The settings screen must say so plainly instead of offering a toggle that silently does nothing.
Definition of done
9
Definition of done
9- Push subscriptions are bound to the account that registered them and are released at sign-out.
- Per-category and per-channel preferences are applied before a send is composed, and muted users receive nothing.
- Expired, revoked, and duplicate subscriptions are marked inactive after provider failures rather than retried indefinitely.
- A single event produces exactly one notification per recipient regardless of how many audiences match.
- Opening a notification for a deleted or now-forbidden record lands on a clear message rather than an error.
- Provider outages and rate limits are absorbed by retries in the background job system with no failed web requests.
- No provider credential is present in anything served to the browser.
- 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
Telegram Bot Notifications
Telegram Bot Notifications
Deliver alerts and summaries to a Telegram user, group, or channel through a bot.
What it does
A Telegram delivery channel that sends selected app notifications to a destination each user has proven they control.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/telegram-bot-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.