Sending from where you already build
Most of these tools can already send mail, through a mailbox you connected or through the platform's own infrastructure. That holds until something depends on it arriving. Then you want a domain you control, a signing key that is yours, and a record of what happened to each message, which is the same API call everywhere, and a different five minutes of setup in each tool.
Building with an AI assistant rather than by hand? The prompts do the same job in one paste.
Send email from Bubble
BubbleAPI Connector, one POST call, and a shared header your other calls can reuse.
Send email from Django
DjangoA subclass of BaseEmailBackend named in EMAIL_BACKEND; the rest of Django keeps calling send_mail as before.
Send email from FlutterFlow
FlutterFlowAn API Call with three variables and a Bearer header, and a note on keeping the key on the server rather than in the app bundle.
Send email from Make
MakeOne HTTP module, and a scenario that can branch on the reply instead of guessing.
Send email from n8n
n8nHTTP Request node with a Header Auth credential, so the key never sits in the workflow.
Send email from Next.js
Next.jsServer-side fetch from a Route Handler or Server Action; the key in an environment variable; idempotency for retried requests.
Send email from Retool
RetoolOne REST API resource, reused by every query that needs to send something.
Send email from Ruby on Rails
Ruby on RailsA custom Action Mailer delivery method, registered in an initializer and selected in production; deliver_later works unchanged.
Follow up a signup with a consented email sequence
SequencesAdd the person with their consent, define the sequence in your code, enroll them, and stop it when they buy. Any platform that can make an HTTP request.
Send email from Supabase
SupabaseDatabase Webhooks for "email when a row appears"; an Edge Function with fetch when the message needs building.
Send email from WordPress
WordPressA must-use plugin on the pre_wp_mail filter, so every wp_mail() call goes out over HTTP under your domain and DKIM key, with nothing else to configure.
Send email from Xano
XanoExternal API Request with the key from an environment variable; the message id stored next to the record that caused it.
Send email from Zapier
ZapierA Webhooks by Zapier "Custom Request" with two headers and a JSON body; Code by Zapier if you are on a plan without webhooks.
Sending from Lovable and Supabase
LovableA working Edge Function, and why SMTP is the wrong tool inside one.
Somewhere else?
Anything that can make an HTTP request can send through us, and the request is the same one in every guide above. The API reference has it, and the SMTP settings cover tools that only speak SMTP.