Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Resend's SMTP credentials plug straight into FormBridge's custom SMTP settings, giving your form notifications and autoresponders a modern transactional sender with domain-level deliverability.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Verify a sending domain in Resend, generate an API key to use as the SMTP password, then in FormBridge go to Account → SMTP Configurations → Add SMTP Server and enter Resend's SMTP host, port 587, TLS encryption, username "resend," and the API key as password.
Custom SMTP on FormBridge isn't limited to legacy providers — modern transactional email APIs like Resend expose the same SMTP interface alongside their own dashboards, and it connects to FormBridge exactly the same way.
Resend is built specifically for transactional sending: notification emails, receipts, password resets, and — relevant here — form notifications and autoresponders. It gives you domain verification, delivery logs, and a cleaner sending reputation than a general-purpose inbox provider, without the AWS-level setup overhead of something like SES.
In Resend's dashboard, find the SMTP section. You'll generally need:
resendCopy the API key immediately — like most providers, Resend only shows it once.
In FormBridge, go to Account → SMTP Configurations → + Add SMTP Server and enter the host, port, TLS encryption, username resend, the API key as the password, and a from name your recipients will recognize. Click Test SMTP, then save.
Assign the new SMTP account to whichever form(s) should send through Resend — remember a form only sends through one SMTP account at a time. Then double-check that form's own Email Settings has a notification email address configured; without it, custom SMTP delivery doesn't take effect even with everything else connected correctly.
If you're comfortable adding DNS records and want notification emails that reliably land in the inbox rather than spam — especially once your form is generating real submission volume — Resend is a solid middle ground between the simplicity of Gmail and the raw scale (and setup complexity) of Amazon SES.
Resend's SMTP setup typically expects the literal username "resend," with your API key used as the password — different from providers that expect a full email address as the username.
Yes. Sending reliably through Resend requires verifying a domain (adding DNS records it provides) so its infrastructure is authorized to send mail on your behalf; sending from an unverified domain is restricted.
For meaningfully higher submission volume, yes — Resend is built as a transactional email API with deliverability and domain reputation as the core product, whereas Gmail SMTP is meant for personal-scale sending and enforces daily caps.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.