transactional-email

Solid

Adding transactional or alert email, choosing a provider, 'sent twice', 'never arrived': app email sent once, never lost, with one-click unsubscribe.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Transactional email: durable receipts, honest about duplicates **Commit messages durably and name the narrow cases that can duplicate them.** A plain "insert, then call the provider" can lose a message or send it twice, depending on where it crashes. This skill covers durable delivery, unsubscribe, environments and domains. **Apply these mechanics to any provider with an HTTP send API.** They carry to Resend, SES and others; provider differences are stated with their read dates. The identity provider's own email, such as sign-in codes and invitations, is not covered here: it sends that itself. **Distinguish the event, its messages, their receipts and the sender.** An event is what happened: an incident opened, an invoice paid. A message is one email about it to one recipient. A receipt is the durable row saying what became of that message. The sender turns pending receipts into provider calls, wherever it runs. ## What binds 1. **The event and its pending message commit together.** A trigger on the event's table writes an outbox row in the event's transaction. An event never exists without its pending message, and a rolled-back event never sends. Code that inserts the event and "then queues the email" has a crash window between the two. A restricted writer needs a definer trigger: `references/delivery.md § The outbox`. The outbox row is unique per event and kind, so a trigger that fires twice still queues one. 2. **One receipt per message, unique, written before anythi...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

add-transactional-email

Make the email an application owes a person actually arrive: receipts, password resets and sign-in codes, from an authenticated sending domain with SPF, DKIM and DMARC, a return path that accepts bounces, dedupe so a retry does not send twice, and suppression so a bounced or complained address is never mailed again. Use when mail lands in spam or nowhere, when an app has no sending domain, or when someone asks for transactional email.

0 Updated 2 months ago
TrustyCap-Technologies
AI & Automation Listed

email-and-templating

Send transactional email correctly — provider choice (Resend/Postmark/SES), react-email/MJML templating, and SPF/DKIM/DMARC deliverability basics. Use when a task sends email — signup confirmation, password reset, receipt, notification digest. Triggers on email, transactional email, Resend, Postmark, SES, react-email, MJML, SPF, DKIM, DMARC, deliverability.

0 Updated 3 months ago
BenMacDeezy
AI & Automation Listed

transactional-email

Set up, diagnose and unify transactional email across projects — SPF/DKIM/DMARC, MX and inbound mail, Spamhaus/blocklist checks, provider choice (Brevo, Resend, SMTP, Postmark, SES), a single sendEmail() module with one env schema, and per-tenant reputation isolation for multi-tenant SaaS. Use whenever email is being added to a project, when mail is not arriving or landing in spam, when a domain is on a blocklist, or when a product needs to send mail on behalf of its customers.

1 Updated 1 months ago
anginduke-code