Resend Transactional Email
Send application email through Resend with verified domains and tracked delivery.
What it adds
A Resend delivery path with domain verification gating production sends, controlled attachments, and recorded delivery events.
What your agent is told to do
5
What your agent is told to do
5-
1
Put Resend behind the app's existing mail layer as one adapter. This entry is an alternative to the other transactional email integrations rather than a companion to them; the mail layer, template contract, and suppression handling stay the same whichever adapter is in place.
-
2
Gate production delivery on a verified sending domain. Until verification is confirmed, keep the app in a mode that redirects or suppresses delivery rather than sending from an unverified address into spam folders.
-
3
Send from the app's background-job system, keyed on a stable per-message identifier, and store the provider's identifier on the record as soon as it is returned.
-
4
Resolve attachments server-side from the app's own storage, enforce a size ceiling before the job is queued, and re-check that the recipient is entitled to the attached file at send time.
-
5
Consume delivery and bounce events on a verified endpoint and maintain suppression state that every future send checks before queueing.
Edge cases it handles
8
Edge cases it handles
8- Sending from an unverified domain lands mail in spam and damages the domain's reputation. Treat verification as a precondition for production delivery, and show its state clearly to an operator rather than letting it fail quietly.
- Attachments have a size ceiling and are resolved from files the app controls. Check the size before queueing so an oversized file fails visibly at composition, and re-check access at send time so a file the recipient has lost permission to is not attached anyway.
- Asynchronous send jobs retried after a timeout will otherwise deliver the same email twice. Key each send on a stable identifier and reconcile the retry against the existing record.
- Provider identifiers and webhook events are what make a delivery question answerable. Store the identifier on the message record and process events on a verified, idempotent endpoint, since events can be replayed and can arrive out of order.
- Development and staging must never reach real recipients. Default those environments to suppressing delivery or redirecting every recipient to a fixed internal address, and do not rely on a data set being fake.
- Transactional email must not be conditioned on marketing consent, and marketing email must not be smuggled through this path to reach people who unsubscribed.
- Credentials and full message bodies must be absent from logs and error reports, because a captured reset link or one-time code is a live credential.
- When the provider is unavailable, the triggering action must still succeed, the message must stay queued, and the app must tell the user the email is on its way rather than claiming delivery.
Definition of done
9
Definition of done
9- Production delivery is blocked until the sending domain is verified, and verification state is visible to operators.
- Attachments are resolved server-side, size-checked before queueing, and access-checked at send time.
- Every message record carries the provider identifier.
- Delivery and bounce webhooks are authenticated, idempotent, and update suppression state.
- Retried jobs never send the same email twice.
- Non-production environments cannot deliver to real recipients.
- No log or error report contains credentials or full message bodies.
- 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.