What Is Resend? The Email Layer Your Automations Actually Need
A plain-English intro to Resend — what makes it different from other email services, how it fits in the automation stack, and why transactional email matters.
When I built SendJob — the job dispatch system I use to run my field service automation business — email was the last thing I thought carefully about. I assumed I’d just hook up Gmail or use whatever SMTP server came with my hosting. That was a mistake I paid for in spam folder complaints and undelivered job confirmations.
Resend fixed that. And once I understood why transactional email is its own category entirely, a lot of things about building reliable automations clicked into place.
Here’s what Resend actually is, why it exists, and how it fits into the stack.
What Resend Is
Resend is a developer-first transactional email API. That description has two parts that both matter.
Developer-first means the product is designed for builders. The API is clean, the documentation is good, and the dashboard gives you real information — not just marketing fluff. There’s a node package, solid REST API coverage, webhook events for delivery status, and React Email support for building templates. You’re not fighting the tool to do basic things.
Transactional email means it’s built specifically for system-generated emails — the kind that your automation triggers on behalf of a specific user action. Confirmations. Receipts. Job summaries. Password resets. Welcome emails. These are the emails your software sends automatically, not the newsletters you blast to your list.
For business owners who don’t write code: Resend is the service that makes sure the emails your automation sends actually arrive in the inbox instead of the spam folder, that you can see whether they were delivered, and that your domain doesn’t get flagged by Gmail or Outlook for looking suspicious.
For builders: clean REST API, excellent deliverability infrastructure, React Email support for responsive cross-client templates, webhook events so you can react to bounces and complaints, and a dashboard that tells you exactly what happened to every email you sent.
Transactional vs Marketing Email — This Distinction Matters
This is the most important concept in email infrastructure, and most people don’t learn it until they’ve broken something.
Transactional email is triggered by a specific user action or system event:
- Job confirmation sent when a new job is created
- Payment receipt sent when a customer pays
- Password reset sent when a user requests it
- Dispatch notification sent when a tech is assigned
Marketing email is sent based on business intent rather than user action:
- Weekly newsletter
- Promotional offer
- Re-engagement campaign
- Announcement blast
These two categories of email have different deliverability rules, different legal requirements, and different infrastructure needs. Resend is for transactional email. Mailchimp, ConvertKit, and Klaviyo are for marketing email.
Here’s why this matters: if you use a transactional email service like Resend to send bulk marketing emails, you will destroy your deliverability. Email providers like Gmail track sending patterns. A sudden blast of 5,000 promotional emails from an address that normally sends receipts and confirmations triggers spam filters and can get your domain flagged.
Keep them separate. Use Resend (or an equivalent) for your system-triggered emails. Use a proper marketing platform for your newsletters and campaigns. These are different products solving different problems.
Why You Need a Proper Transactional Email Service
Here’s what actually happens when you try to handle automated emails without a purpose-built transactional service:
Gmail caps outbound volume. Free Gmail accounts are limited to 500 emails per day. Google Workspace accounts get 2,000. If your automation sends job confirmations, dispatch notifications, and payment receipts for a busy day of service calls, you can hit that ceiling faster than you think.
Emails go to spam. If you’re sending from a generic server without proper authentication records, inbox providers don’t trust you. Your customer’s job confirmation — the one they need to know what time the tech is showing up — ends up in the spam folder. They miss it. They call frustrated. That’s a business problem, not just a technical one.
You can’t track delivery. When you send email through an unmonitored SMTP server, you have no idea whether the message was delivered, bounced, or opened. When a customer says “I never got the confirmation,” you have no way to verify whether that’s true or which end the problem is on.
Your domain gets flagged. Sending patterns that look automated or high-volume from a domain without proper SPF, DKIM, and DMARC records will eventually get your domain added to spam blocklists. Once you’re on those lists, getting off them is painful.
A proper transactional email service like Resend handles all of this. Deliverability infrastructure, authentication records, bounce handling, and a dashboard where you can see exactly what happened to every email you sent.
What This Looks Like in SendJob
In SendJob, there are four email-sending moments in every job’s lifecycle. All of them are triggered automatically by n8n, all of them go through Resend:
New job received — When a customer submits a job request, n8n creates the job record in Supabase and immediately fires an email to the dispatcher confirming a new job came in, with the customer details and job description attached.
Job confirmed to customer — Once the dispatcher assigns a tech and confirms the appointment, n8n sends the customer a confirmation email: tech name, appointment window, what to expect.
Tech assignment notification — At the same time, the assigned tech gets an email with the job details, customer address, and any notes from the dispatcher.
Payment receipt — After the job is complete and the customer pays via Stripe, n8n triggers Resend to send a payment receipt with the job summary and amount charged.
Four distinct emails, four distinct business moments, all automated. None of them are marketing. All of them are transactional. Resend handles every one of them.
If any of these emails failed — went to spam, bounced silently, or never sent — that’s a real operational problem. Job confirmations build customer trust. Payment receipts are a legal expectation. Tech assignment emails are how the work gets done.
Where Resend Fits in the Stack
Resend is the outbound email layer. Here’s how the pieces connect:
n8n is the orchestration layer. It decides when to send an email, who to send it to, and what content to include. It queries Supabase for the relevant data and builds the email payload.
Supabase is where the data lives — customer email addresses, job details, payment amounts. n8n pulls from Supabase to populate the emails it sends through Resend.
Resend handles the actual sending infrastructure — SMTP authentication, deliverability, bounce tracking, open tracking, and the DNS reputation that makes inbox providers trust your emails.
You don’t send emails directly from n8n to Gmail. n8n tells Resend “send this email to this address with this content,” and Resend handles everything downstream from that instruction.
This separation of concerns is clean and intentional. n8n doesn’t need to know about SPF records. Resend doesn’t need to know about job statuses. Each tool does its one job.
Resend vs the Alternatives
There are several legitimate transactional email services. Here’s an honest comparison:
SendGrid — The most widely used option. It’s been around the longest, has every feature you could need, and has deep integrations with almost every platform. It’s also showing its age. The dashboard is cluttered, the pricing has gotten more complicated, and the developer experience doesn’t feel as clean as newer tools. It’s a solid choice, but not the most pleasant one.
Postmark — Excellent deliverability, arguably the best in the industry. Clean product. Separate streams for transactional and broadcast email, which is smart design. The downside: it’s more expensive than Resend, especially on lower volumes. If deliverability is your top concern and you’re willing to pay for it, Postmark is worth considering.
Mailgun — Powerful and developer-focused. Good API, reliable infrastructure. The UI has improved but still feels complex relative to the simpler alternatives. Pricing can get expensive at scale.
AWS SES — Extremely cheap. Like, fractions of a cent per email cheap. But the setup complexity is significant — you’re dealing with IAM roles, SES policies, and AWS’s generally hostile UX. For a large operation where cost is a real concern, it makes sense. For getting started quickly on a new project, it’s not the right call.
Brevo (formerly Sendinblue) — Combines transactional and marketing email in one platform. Good option if you want to keep everything in one place and you’re running a smaller operation. The all-in-one approach has trade-offs in deliverability compared to a specialist like Resend or Postmark.
Resend — Newer than all of the above. Launched in 2023 and has earned its reputation quickly in the builder community. The developer experience is the best of any option on this list — the API is clean, the docs are excellent, and the dashboard actually tells you useful things. The free tier is genuinely generous. React Email integration is a real differentiator for teams building custom templates.
My honest take: for a new project, Resend is the easy call. The DX is excellent, the pricing is fair, and the deliverability is solid. I wouldn’t migrate an existing SendGrid or Postmark setup just to switch — but if you’re starting fresh, start with Resend.
What It Costs
Resend’s pricing is simple and fair:
Free tier: 3,000 emails per month, 1 custom domain, 100 emails per day sending limit. For a small operation or during development and testing, this covers a lot of ground.
Pro ($20/month): 50,000 emails per month, multiple custom domains, no daily sending limit. This is where most small-to-medium automation setups will land. For SendJob running at normal volume — a few dozen jobs per day — the free tier was enough for a long time. Pro becomes the right move when you’re scaling.
Business ($90/month): 100,000 emails per month, priority support, advanced analytics. For higher-volume operations or agencies running multiple clients.
At $20/month for 50,000 emails, the Pro tier works out to $0.0004 per email. For an automation that sends 4 emails per job, you’re paying less than $0.002 per job in email costs. It’s not a meaningful cost driver at any reasonable business scale.
Domain Setup and Deliverability — The Non-Optional Part
The most important thing you will do with any transactional email service is verify your domain. This is not optional, and it’s not something you can defer until later.
Verifying your domain means adding DNS records to your domain that prove to email providers that you authorized Resend to send email on your behalf. There are three records you need to care about:
SPF (Sender Policy Framework) — Specifies which mail servers are allowed to send email from your domain. Without this, receiving mail servers have no way to verify your emails are legitimate.
DKIM (DomainKeys Identified Mail) — Adds a cryptographic signature to every email you send. The receiving server checks this signature against your DNS record to verify the email wasn’t tampered with in transit.
DMARC (Domain-based Message Authentication, Reporting & Conformance) — Tells receiving mail servers what to do when SPF or DKIM checks fail. It also enables reporting back to you about authentication failures.
Resend generates all three records for you and shows you exactly where to add them in your DNS provider. The process takes about 10 minutes. Without it, your emails will land in spam. The basics guide walks through the exact steps.
Ready to set up your email layer? Getting Started with Resend →