How to Send Your First Transactional Email with Loops
Loops is an email platform for SaaS: transactional emails (password resets, receipts) and marketing campaigns (newsletters, onboarding sequences) from one template editor. You send transactional mail via a REST call to https://app.loops.so/api/v1/transactional with your template ID and contact data.
It fits the gap between Resend (transactional only, developer-first) and ConvertKit (marketing only, creator-first). If your product sends both, using one platform keeps unsubscribes and contact properties consistent.
How do you get set up?
- Create an account at
loops.soand add your sending domain. - Add the DNS records — SPF, DKIM, and a DMARC record. Verification usually clears in 10-30 minutes; if it stalls past an hour, you probably have two SPF records, which is invalid.
- Wait for domain approval. New domains go through a short review; sending reputation starts at zero.
- Create a transactional template under Templates → New.
- Copy the template ID from the URL — that ID is what your code uses.
The DNS step is where 80% of the setup time goes. If you use Google Workspace, your SPF record already exists and you must append Loops’ include rather than create a second record.
How do you send from code?
A plain POST, no SDK required:
curl -X POST https://app.loops.so/api/v1/transactional \\
-H "Authorization: Bearer YOUR_KEY" \\
-H "Content-Type: application/json" \\
-d '{"transactionalId":"clxxxx","email":"a@b.com",
"dataVariables":{"resetUrl":"https://...","expiresIn":"30 minutes"}}'
dataVariables map to {{resetUrl}} style placeholders in the template. Any variable you reference but do not send renders as a blank string — not an error. Test the template with the Send test button before you trust it in production, or you will ship a password reset email with an empty link.
Node, Python and PHP SDKs exist if you prefer wrapped calls.
What are the rate limits and free tier?
- Free: 1,000 contacts, unlimited sends to those contacts.
- Paid: from $49/month for 5,000 contacts, scaling up.
- Transactional API rate limit: 10 requests per second per account.
That last one bites during a batch operation. If you send 500 welcome emails in a loop, throttle to 10/s or Loops returns 429 and your loop drops the failures silently unless you check the status code.
Note the pricing model: contacts, not emails. Sending 20 onboarding emails to 1,000 contacts costs nothing extra. Different from ConvertKit, which charges by subscriber tier similarly but limits broadcasts.
Is it good for marketing too?
Reasonable, with caveats. Campaigns support drag-and-drop blocks, loops (no pun), segments and A/B subject tests.
What it lacks: a proper visual automation canvas. Sequences are linear — trigger, wait, send, wait, send — and branching exists but is more limited than Customer.io or Klaviyo. For a 30-person SaaS with a three-email onboarding flow, that is enough. For a lifecycle-marketing team running 20 branches, it is not.
Deliverability tooling is basic: you get bounce and complaint data, not inbox placement tests. Pair it with a third-party seed test if your volume is above 50k sends a month.
What about the transactional/marketing split?
This matters legally. Transactional emails (receipts, security notices) bypass marketing consent. Loops keeps them as separate template types with separate suppression rules — a user who unsubscribes from marketing still gets their password reset.
Verify that behaviour on your own list before launching. Getting it wrong means either missing a password reset or emailing someone who opted out of marketing, and both end up in a support ticket.
Where Loops loses
- No SMTP relay option. Your post-create hook has to call the API, which is fine for a Node backend and awkward if you are on a platform that only speaks SMTP.
- Self-hosted or EU-only data residency is not offered. Check their DPA if GDPR data location is a constraint.
- Template versioning is thin. Editing a live transactional template applies immediately. No draft staging.
Key Takeaways
- Verify the sending domain with SPF, DKIM and DMARC first — this is most of the setup time.
- Send transactional mail with a POST to
/api/v1/transactional, using the template ID anddataVariables. - Missing variables render blank, not an error — send a test before every template change.
- Transactional API rate limit is 10 requests/second; throttle batch sends.
- Pricing is per contact, not per email; free for 1,000 contacts.
