Microsoft Teams Channel Alerts
Post operational and customer alerts into a chosen Microsoft Teams channel.
What it adds
A Teams destination for selected app events, with explicit tenant, team, and channel selection and reliable delivery.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Store credentials server-side, refresh them ahead of expiry, and when a refresh fails, disable the destination and tell an operator inside the app exactly which connection needs reauthorising.
-
5
If a Slack brief is also applied to this app, share its event-selection and routing layer and let this brief own only Teams formatting and delivery. Two independent alert configurations will drift and double-post the same event.
Edge cases it handles
8
Edge cases it handles
8- Tenant, team, and channel must each be chosen explicitly. A guessed default posts customer data into whichever channel happened to be first in the list.
- Payloads over the provider's size limit are rejected outright. Truncate deliberately with a link to the full record rather than discovering the ceiling during an incident.
- Credentials expire, and the account that authorised them may leave the organisation. Refresh proactively, and on failure disable the destination with an operator-visible reason instead of retrying silently forever.
- An ambiguous delivery failure, such as a timeout after the request was accepted, must be deduplicated on the event identifier, or the same incident is announced twice.
- User-supplied text must be escaped before it is placed in a rich card, so a message cannot inject formatting, an image, or a link the sender never wrote.
- Rate limits and transient provider failures need bounded backoff, and delivery must never block the user action that generated the event.
- Everyone in the channel sees the alert. Exclude anything the whole membership should not read, and prefer a link to the record over the record's contents.
- A channel that has been deleted, or that the app has lost access to, must disable itself and surface in the app rather than accumulating failed jobs.
Definition of done
9
Definition of done
9- Tenant, team, and channel are selected explicitly at setup and confirmed with a test message.
- Messages stay within provider size limits, truncating with a link rather than failing.
- Credentials are stored server-side and refreshed before they expire.
- A failed refresh or lost channel access disables the destination and tells an operator why.
- An ambiguous delivery failure never results in a duplicate post.
- User-supplied text cannot alter card formatting or inject links.
- Alert delivery never blocks the user action that produced the event.
- 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
Postmark Transactional Email
Postmark Transactional Email
Send transactional email through Postmark on the right stream, with bounces tracked.
What it does
A Postmark delivery path that separates message streams, honours suppression, and retains provider identifiers for diagnostics.
How it works
- 1 Put Postmark behind the app's existing mail layer as one adapter, so no calling code constructs a provider-specific payload. This entry is an alternative to the other transactional email integrations, not an addition — pick one adapter and keep the mail layer identical.
- 2 Classify every outbound message as transactional or broadcast and bind that classification to the matching message stream at the mail layer, so the choice is made once and cannot be got wrong at an individual send site.
- 3 Send from the app's background-job system and persist the provider's message identifier on the record the moment it comes back, so a support question about one email can be answered without guessing.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/postmark-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.