Discord Webhook Alerts
Push product and operational alerts into a Discord channel without exposing the webhook.
What it adds
An outbound Discord destination that receives selected app events as formatted channel messages.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the events already worth announcing internally — signups, failed payments, error spikes, support requests — and let an operator choose which of them route to a Discord destination. Do not fan out every event the app emits.
-
2
Store the webhook target as a server-side secret. It must never reach the browser, a client bundle, a log line, or an error report, because anyone holding it can post to the channel indefinitely.
-
3
Send through the app's existing background-job system so a slow or unreachable Discord never blocks the request that triggered the event.
-
4
Treat every message as carrying untrusted content. Neutralise mention syntax, role and channel references, and link markup in any user-supplied text before it is included.
-
5
Do not build a second notification pipeline. If the app already routes notifications to email or another channel, add Discord as one more destination on that pipeline so preferences, throttling, and audit stay in one place.
Edge cases it handles
8
Edge cases it handles
8- A webhook target must be validated when it is saved, by confirming it accepts a test message, and the validation result must be reported without ever echoing the target itself back to the screen or into logs.
- User-supplied text that contains mention syntax must not be able to notify everyone in the channel. Escape or strip mentions rather than trusting that the content looks harmless.
- Discord enforces limits on message length and on the number and size of structured fields. Truncate on a sensible boundary and link back to the app for the full record rather than letting the send fail.
- A webhook deleted on the Discord side will keep rejecting sends forever. Detect the permanent rejection, mark the destination as broken, stop retrying, and tell an operator in the app.
- A send that times out may still have been delivered. Attach a stable identifier per event and keep a record of what was sent, so a retry after a timeout does not post the same alert twice.
- Discord rate-limits aggressively when a burst arrives. Honour the throttling signal, back off, and queue rather than dropping alerts on the floor.
- A busy hour must not turn into hundreds of near-identical messages. Collapse repeated events of the same kind into a single summary above a threshold.
- When Discord is down entirely, the triggering action must still succeed and the alert must be retried later or visibly abandoned, never silently lost.
Definition of done
8
Definition of done
8- Operators choose which event types route to Discord, and the default is nothing.
- The webhook target is stored server-side and appears in no log, response, or client asset.
- Alerts are delivered from a background job and never delay the originating request.
- User-supplied content cannot trigger a channel-wide or role mention.
- Retries after a timeout do not produce duplicate messages in the channel.
- A deleted or rejected webhook is marked broken, stops retrying, and is surfaced to an operator.
- 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
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
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.