Postmark Transactional Email
Send transactional email through Postmark on the right stream, with bounces tracked.
What it adds
A Postmark delivery path that separates message streams, honours suppression, and retains provider identifiers for diagnostics.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Consume delivery and bounce feedback on a verified endpoint and maintain a suppression state per address that every send checks before queueing.
-
5
Do not send transactional mail to an address the provider has marked inactive just because the app still has it on a user record. Reconcile the app's view with the provider's suppression state and surface the problem to the user instead.
Edge cases it handles
8
Edge cases it handles
8- Sending a broadcast on the transactional stream, or the reverse, degrades deliverability for everything else. Bind the stream to the message classification centrally rather than passing it in at each call site.
- An address the provider has deactivated after repeated bounces or a complaint will silently stop receiving mail. Detect the inactive state, show the affected user that their address is not receiving mail, and give an operator a way to reactivate after the address is corrected.
- Delivery and bounce webhooks arrive on a public endpoint and can be replayed. Verify their authenticity before trusting them, and apply them idempotently so a repeated event does not double-count a bounce or overwrite newer state.
- A job retried after a timeout may resend an email that already went out. Key each send on a stable identifier so the retry reconciles rather than duplicating.
- Provider message identifiers are the only reliable way to trace a specific email in a support conversation. Store them alongside the message record and keep them for as long as support needs them.
- Transactional mail must not be gated on marketing consent. A receipt or a password reset goes to someone who has unsubscribed from everything else.
- Non-production environments must not reach real recipients. Suppress delivery or redirect every message to a fixed internal address by default outside production.
- When the provider is degraded, the triggering action must still succeed, the message must stay queued for retry, and no log line should carry the credential or the full body.
Definition of done
8
Definition of done
8- Every message is classified and sent on the stream matching its classification, decided in one place.
- Provider message identifiers are stored on every sent message record.
- Bounce and delivery webhooks are authenticated and idempotent.
- Suppressed or inactive addresses are skipped before queueing and surfaced to the user.
- Retried jobs never produce a duplicate email.
- Non-production environments cannot deliver to real recipients.
- 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.