Send transactional emails or SMS for app-triggered communications: receipts, password resets, OTPs, order confirmations, shipping notifications, system alerts. Single recipient, immediate delivery, no campaign or approval needed. Use when: "transactional email", "receipt email", "password reset email", "send notification email", "order confirmation", "OTP email", or "system email".
Send Transactional
Help the user send or set up transactional emails/SMS — immediate, single-recipient messages triggered by application events.
Understand the Use Case
Common transactional email types:
- Password reset: OTP or magic link
- Order confirmation: Receipt with order details
- Shipping notification: Tracking info
- Welcome/verification: Account activation
- System alert: Service status, security notice
- Invoice/receipt: Payment confirmation
Design Approach
Quick Send (Plain Text)
For a one-off send from Claude over MCP, use nitro_send_message:
channel: "email"
to: "user@example.com"
subject: "Your order #1234 is confirmed"
body: "Thank you for your order..."
Branded Template
For on-brand transactional emails:
- Create a template with
nitro_manage_templatevia the composition contract (composition_mode: "intent"→ fill the returnednext_call→ persist withcomposition_mode: "draft"; see the compose-email skill) - For a one-off MCP send, call
nitro_send_messagewithtemplate_id - For application-triggered production sends, wire
POST /v1/my/messagesorns.messages.sendusingtemplate_id
Live sends require an idempotency_key — reuse the same stable key on retry to
prevent duplicate delivery.
Merge Variables
Use the data field for personalization:
data: { order_id: "1234", customer: { name: "Alice" }, amount: "$49.99" }
Reference in templates/body as {{ data.order_id }}, {{ data.amount }}, or
nested paths like {{ data.customer.name }}.
Key Differences from Marketing Email
| Marketing | Transactional | |
|---|---|---|
| Audience | Lists/segments | Single recipient |
| Requires subscription | Yes | No |
| CAN-SPAM footer | Required | Skipped |
| Unsubscribe link | Required | Not needed |
| Delivery | Campaign workflow | Immediate |
| Tracking | Opens/clicks tracked | Opens/clicks tracked (engagement tracking stays enabled) |
Do not model transactional sends as MCP flows. Use nitro_send_message for one-off MCP sends, normal flow email steps for lifecycle automation, and API/SDK transactional sends for application events.
For Developers
Help developers integrate transactional emails into their apps:
API Integration
POST https://api.nitrosend.com/v1/my/messages
Authorization: Bearer nskey_live_...
Idempotency-Key: verification-user-123-attempt-1
Content-Type: application/json
{
"channel": "email",
"to": "user@example.com",
"subject": "Your verification code",
"body": "Your code is: 123456",
"data": { "code": "123456" }
}
SDK Integration
import { Nitrosend } from '@nitrosend/sdk'
const ns = new Nitrosend('nskey_live_...')
await ns.messages.send({
channel: 'email',
to: 'user@example.com',
subject: 'Your verification code',
template_id: 42,
data: { code: '123456' }
}, 'verification-user-123-attempt-1')
Dry Run
Always offer to do a dry run first:
nitro_send_message or POST /v1/my/messages with dry_run: true validates without sending.
Idempotency
Every live send must have a stable idempotency key. Reuse it only for an exact
retry of the same recipient and payload; use a new key for a different logical
message. MCP uses idempotency_key, the REST API uses the Idempotency-Key
header, and the Node SDK accepts the key as the second argument to
messages.send.
Nitrosend Sender Readiness
Before the first live email, inspect brand_subdomain in
nitro_get_status. If preparation is required, use
nitro_manage_domains(operation: "prepare_brand_subdomain"), poll until it
is ready, then select it explicitly. A first authenticated send may return
sender_identity_provisioning; that response is retryable, but no message was
stored or queued. Retry with the same idempotency key only after readiness and
selection.
Related skills
- Downloads
- Security audit
- Pass
- Last updated
- 3w ago
- Current version
- v1.0.0
- License
- MIT-0
