Firebase Cloud Messaging
Deliver push through Firebase with registration tokens that stay valid as devices change.
What it adds
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.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Treat the destination carried in a notification as untrusted input. Resolve it to a route on open and re-authorise the recipient against the current record before showing anything.
-
5
If the app also carries the OneSignal push brief, do not run both as independent senders. One of them owns registration, preference filtering, and deduplication for the whole app, and the other is removed or reduced to a delivery transport underneath it.
Edge cases it handles
8
Edge cases it handles
8- The provider will reject tokens that have been rotated, revoked, or belong to a reinstalled app. Remove or replace those registrations on the error rather than leaving them to fail on every future send.
- One person may use several devices, and one device may be used by several people. Keep registrations distinct per device, and reassign rather than duplicate when a new account signs in on a device already registered.
- A notification tapped hours later may point at a record that has since been deleted, moved, or revoked. The open path must check access at that moment and fall back to a sensible screen instead of trusting the link it was given.
- Retried background jobs and repeated provider callbacks must not produce a second notification. Key each send on the event and the registration so a replay is recognised and discarded.
- Send failures come in two kinds: permanent ones that mean the registration is dead, and temporary ones that mean try again later. Retry only the second kind, with increasing delays, or a provider outage will empty the device table.
- Lock-screen previews expose whatever is in the payload. Keep sensitive detail out of the visible portion and let the app fetch it after the user has unlocked and authenticated.
- When the provider is unavailable, the rest of the app must continue working and the user should still see the event in the app's own notification surface.
- Time-sensitive notifications need an expiry so a queue drained after an outage does not deliver a batch of stale alerts at once.
Definition of done
9
Definition of done
9- Registrations are stored per device with the owning account and platform, and many per account are supported.
- Tokens rejected as permanently invalid are removed on the failure, while temporary failures are retried with backoff.
- A given event and registration pair produces one notification even when jobs or provider callbacks repeat.
- Display versus silent handling for each notification type is identical across platforms.
- Opening a notification re-checks permission on the target record before rendering it.
- Provider credentials exist only on the server and never in client-visible code.
- A provider outage degrades to in-app notifications with no user-visible errors elsewhere.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Slack Channel Alerts
Slack Channel Alerts
Send the events a team actually needs into a Slack channel without flooding it.
What it does
Operator-configured routing of selected app events into Slack channels, with grouping, throttling, and reliable delivery.
How it works
- 1 List the events genuinely worth interrupting a team for — failed payments, high-value signups, error thresholds, approvals waiting — and make each individually selectable per channel. An all-or-nothing firehose gets muted within a week and then nobody sees the one that mattered.
- 2 Run the connection through the provider's authorisation flow, then confirm the workspace and channel at setup by posting a test message the operator has to acknowledge. Store the resulting credential server-side only.
- 3 Write each message so it stands alone: what happened, to whom, when, and a link back into the app. Optional fields that are absent must be omitted cleanly rather than rendering as empty labels.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/slack-channel-alerts
Microsoft Teams Channel Alerts
Microsoft Teams Channel Alerts
Post operational and customer alerts into a chosen Microsoft Teams channel.
What it does
A Teams destination for selected app events, with explicit tenant, team, and channel selection and reliable delivery.
How it works
- 1 Make the destination explicit at setup: the operator picks the tenant, then the team, then the channel, from lists the app fetched under that operator's own authorisation. Do not accept a pasted destination identifier as configuration.
- 2 Confirm the connection by posting a test message the operator acknowledges, and record which account authorised it so anyone can see whose credentials the integration depends on.
- 3 Keep every message inside the provider's payload and card size limits. Truncate long user content at a defined boundary and link back to the full record, rather than letting an oversized post be rejected silently.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/microsoft-teams-channel-alerts
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.