All integrations
Resend

Resend

Let your app send real emails: welcome, receipts, reminders, alerts.

Official Resend docs

What is Resend?

Resend is a service that sends emails for your app. Once it is connected to Bloxks, your app can send real emails on its own: a welcome message after sign up, a receipt after a purchase, a reminder the day before an appointment, an alert when something happens.

You don’t write any code: you connect your key once, then you ask for what you want in the chat.

What it unlocks in Bloxks

  • Automatic emails: welcome, order confirmation, reminder, weekly summary, new message alert.
  • Emails to you: get notified when a user fills a contact form, books a slot or leaves a review.
  • Your own address: emails leave from your domain (for example hello@yourapp.com), so they reach the inbox instead of spam.
  • A secret key: your key is stored encrypted and only lives on the server side of your app. It never appears in your app’s code, so nobody can steal it from the App Store version.

Step 1: create your Resend account

  1. Open resend.com and click Get Started.
  2. Sign up with your email or your GitHub/Google account. The free plan is enough to start.

Without a domain, Resend only lets you send test emails to your own address, from onboarding@resend.dev. To email your users, add a domain you own:

  1. In Resend, open Domains and click Add Domain.
  2. Type your domain (for example yourapp.com). Tip: a subdomain like mail.yourapp.com keeps things tidy.
  3. Resend shows a few DNS records (lines to copy). Paste them in the DNS settings of the site where you bought your domain (OVH, GoDaddy, Namecheap, Cloudflare…).
  4. Come back to Resend and click Verify DNS Records. It usually takes a few minutes, sometimes up to a few hours.

When the domain shows Verified, you can send from any address on it (hello@, no-reply@, support@…).

Step 3: create your API key

  1. In Resend, open API Keys.
  2. Click Create API Key, give it a name (for example "Bloxks") and choose Sending access.
  3. Copy the key right away (it starts with re_): Resend only shows it once.

Step 4: connect it to Bloxks

Two ways, pick the one you prefer:

  • From the chat: just ask for an email feature. If Resend isn’t connected yet, Bloxks shows a Connect Resend card: click it, paste your key, done. The build continues on its own.
  • From Connections: open Connections, pick Resend, click Add connection, paste your key and validate.

Bloxks then passes the key to your app’s backend (Supabase) automatically. You have nothing else to set up.

Step 5: ask for your emails in the chat

Describe what you want in plain words. A few examples:

  • "Send a welcome email when someone creates an account."
  • "When a user books a session, email them a confirmation with the date and time."
  • "Send me an email at hello@mydomain.com every time someone fills the contact form."
  • "Send the order receipt by email after each purchase, from no-reply@myshop.com."

Bloxks creates a small server function in your app’s backend that sends the email through Resend, and connects it to the right button or moment.

Step 6: test it

  1. Open your app in the preview or on your phone.
  2. Trigger the action (create an account, book, fill the form…) with a real email address you can check.
  3. Look at your inbox, and also at Emails in Resend: every send is listed there with its status (delivered, bounced…).

Resend or "login emails"?

These are two different things:

  • Login emails (email verification, password reset, magic link) are sent by Supabase. To send them through Resend, open Backend → Users in Bloxks and click Connect next to the email sending banner. You use the same Resend key.
  • Your app’s emails (welcome, receipts, reminders, alerts) use the Resend connection described on this page.

You can use both at the same time.

If something doesn’t work

  • No email received: check your spam folder, then the list in Resend → Emails. If nothing is listed, tell the chat "the email isn’t sent" and Bloxks looks into it.
  • "You can only send testing emails to your own email address": your domain isn’t verified yet (step 2).
  • "The domain is not verified": the sending address doesn’t match your verified domain. Ask the chat to send from an address on that domain.
  • "API key is invalid": the key was deleted or mistyped. Create a new one (step 3) and replace it in Connections → Resend.

Good to know

  • The free Resend plan covers 3,000 emails a month (100 a day). Paid plans start when you need more.
  • Your key is stored encrypted and never exposed in your app’s code.
  • To change or remove your key, open Connections → Resend.
  • Never send emails to people who didn’t ask for them: stick to messages linked to what they do in your app.

Want to go deeper? Read the official Resend docs.

Go further

The pages of this documentation that use Resend.

Frequently asked questions

Resend is for emails your app sends itself (welcome, receipts, alerts). Sign-in emails go through Supabase: see Sign-in emails.

To write to your users, yes: Resend only sends from a verified domain. Without one, you can only send yourself a test.