Thanks. You’re
paid up.
Sloop Pro, November 12 to December 12, 2026.
- Sloop Pro, monthly
- $24.00
- Tax
- $0.00
- Total
- $24.00
- Paid with
- Visa ending 4242
Email for developers
Draft your app’s email in Cursor, Claude Code or Codex, then review one pull request before it goes live.
Use Nitrosend to set up the email basics for my app:
Read https://nitrosend.com/skills/developers.md and follow it step by step.
1. Connect Nitrosend. Keys go in environment variables, never in code.
2. Find where this app sends email, or should, and show me the plan. Then build what is missing as drafts: sign-in email, receipts and failed-payment notices, the sending domain, bounce and complaint webhooks, and product events.
3. Open one pull request with every code change, and send me a test of every email.
4. Ask me before anything goes live, before you change DNS and before you import contacts.Paste it into Cursor, Claude Code or Codex.On your phone? Email it to yourself
Start with these five, in this order. Already have a welcome email? Your agent checks what exists and builds only what is missing.
Get people into their account in seconds: verification, magic links and password resets.
This link works once and expires in 15 minutes.
Confirm this address and your first project is ready to deploy.
Confirm emailThis link works once and expires in 60 minutes. If you didn’t ask for it, ignore this email and nothing changes.
Reset passwordConfirm every payment, and recover the ones that fail.
90%of recovered payments land within 10 days, industry data
Sloop Pro, November 12 to December 12, 2026.
We’ll try again on November 15. Your projects stay online.
We’ll retry your card on November 20. If it fails, Sloop Pro pauses and your projects move to the free plan. Nothing is deleted.
Update payment methodAuthenticate a sending subdomain so mailbox providers accept what you send.
87.2%of email reaches the inbox, global average
These let Gmail, Yahoo and Outlook confirm our email is ours. Nothing changes on the root domain.
Stop sending to addresses that bounce or complain, on every send path.
0.06%spam complaint rate, industry average
Yesterday’s import added 31 addresses that bounced. They are now suppressed.
Let what a user has done, or hasn’t, decide the next email.
Your project is set up. Push to main and Sloop builds and deploys it.
Read the quickstartBenchmarks: Recurly failed payment recovery data, April 2026; Validity deliverability benchmark, 2026.
Sign-in email and receipts keep the product working. A monthly changelog gives people who opted in a reason to come back. The prompt drafts your first from your merged pull requests.
Paste it into Cursor, Claude Code or Codex in your repo. Your agent reads the code first and asks only what it cannot find.
It shows every place your app sends email, or should, and waits for your yes before it edits a file.
Your agent sends a test of every email and one pull request, then takes live only what you approve.
Your agent connects the Nitrosend MCP server, and your app sends through the REST API or the Node SDK. Transactional email, flows and campaigns share one account, and transactional email runs on its own sending infrastructure.
The skill is a plain text file you can read before you run it.
Read the skill fileThe sender rules below are Google’s, Yahoo’s and Microsoft’s own. The rest of the plan comes from the Email Marketing Bible, the open-source email skill we maintain: 908 sources and 49 practitioners. Read the Email Marketing Bible.
Transactional email infrastructure has to handle sudden spikes in volume reliably.
Lauren Meyer, SocketLabsTo recover a sending reputation, fix authentication first, then the list, then engagement.
Troy Ericson, EmailDeliverability.comFor email layout, a div with a ghost table generally beats real layout tables.
Mark Robbins, Customer.ioWe’ve run email at scale before. George and Ed co-founded SmartrMail, with Kam as CTO. It grew to 12,000 stores and 6 billion emails before Relay Commerce acquired it in 2022.
Yes. Paste the prompt on this page into Cursor, Claude Code or Codex, in your repo. It reads a short skill file, connects the Nitrosend email MCP server, finds where your app sends email or should, builds what is missing as drafts and opens one pull request. In Claude or ChatGPT without your repo, it builds the emails and writes out the code changes.
No. Email that already works keeps running where it is. Your agent builds what is missing on Nitrosend in one pull request, and offers to move the rest as its own commit when you want flows, campaigns and transactional email on one account and domain.
The prompt tells it to build drafts, send tests only to you, and ask before anything goes live, before DNS changes and before importing contacts. Code waits in a pull request until you merge it. For a hard stop on campaigns and flows, turn on Safe Mode in Nitrosend and every send waits for your approval.
Send it within seconds, from a transactional subdomain, with a single-use link that expires within the hour. Give it one job and no promotion, a reply-to address someone reads, and an alert if delivery takes longer than 30 seconds. Those are the Email Marketing Bible’s rules for sign-in email.
No. Google requires one-click unsubscribe only on marketing and promotional email, and excludes transactional messages such as receipts and password resets. SPF, DKIM and DMARC apply to everything once you pass 5,000 emails a day to Gmail, so authenticate the sending subdomain first, then check that your changelog and onboarding email carry the unsubscribe headers.
Free to start: 5,000 emails up front, then 500 free every month. No card needed. Contacts are unlimited on every plan, so a large user table costs nothing to store, and you pay for what you send. Starter is $20 a month for 20,000 emails.
Create your account, paste the prompt into the coding agent you already use, and review the pull request it opens.
Free to start: 5,000 emails up front, then 500 free every month. No card needed.