Overview
How HireFlow sends candidate email, and the two things that sound alike
HireFlow can email candidates automatically as they move through a pipeline — screening invites, interview details, offers, rejections — using templates you write once and reuse across every job.
Two pieces make that work, and their names sit uncomfortably close together:
| HireFlow Email | Resend | |
|---|---|---|
| What it is | Email you compose inside HireFlow | Your own Resend account |
| Where you find it | Intelligence → Email | Settings → Integrations |
| What it gives you | A template library, merge fields, version history | The delivery pipe, plus access to templates and automations you built in Resend |
The rule that ties them together: however you author an email, HireFlow delivers it through your own Resend account. Mail goes out from your domain, signed by your DNS records, with your sending reputation — not HireFlow's.
Before anything can send
Four things have to be in place. All of them live on Setting up Resend:
- Resend is connected with a Full-access API key.
- A sending domain is verified in your Resend account.
- A sender identity is chosen on that verified domain.
- A delivery provider is selected in Intelligence → Email → Setup.
A fifth step, registering the delivery-events webhook, isn't needed to send — but without it you never find out what happened to anything you sent. See Delivery and tracking.
On a HireFlow hosted by NeuronHire, steps 1 and 2 are configured at the platform level and aren't yours to change.
Automations skip quietly until setup is complete
If no verified sending domain is configured, email automations do not fail loudly — they skip. A candidate moves into the stage, nothing arrives, and the pipeline carries on as normal. It's worth confirming your setup before you rely on an automation for anything that matters.
Who can set this up
Creating and editing email templates and automations requires the owner, admin, or hiring manager role. Recruiters can move candidates through stages and trigger the automations that already exist, but cannot change what those automations send.
Connecting Resend itself is an admin task, like every other API-key integration. See Roles and organizations.
Where to go next
Setting up Resend
API key, domain verification, and choosing your sender address
Email templates
Write reusable templates with merge fields, preview them, and roll back changes
Email automations
Send automatically on stage entry, and choose where the content comes from
Delivery and tracking
See what was sent, what was opened, and how unsubscribes are handled