Sending and receiving email from your app: verifying a domain, daily limits, bulk sends, bounces, and what it costs.
Every Floot app can send and receive email through Floot's own mail service — no provider account and no API key. Ask your assistant for the feature ("email me when someone books", "let customers write to support@") and it wires it in. This page covers what you set up yourself, and the limits worth knowing.
Verify a sending domain before you go live
Until your project has a verified sending domain, your app's mail goes out from Floot's shared domain, and anything addressed to someone other than you is delivered to you instead, with [target: …] in front of the subject and a notice in the body explaining why. That is handy while you test and wrong for a live app: nothing errors, so it is easy to miss that no customer ever received a signup email. Bulk sends are refused outright until a domain is verified.
- 1
Open the Email tab
Open your project on floot.com, go to Services → Email, and click Add email domain. Adding a domain requires a paid plan.
- 2
Enter the domain to send from
If your main domain already serves your website or has mailboxes, use a subdomain such as
mail.yourdomain.com— Floot suggests one when it spots a likely conflict. Your app can then send from any address at that domain. - 3
Add the DNS records
Set up automatically connects to your DNS provider and adds the records for you; Set up manually shows them so you can copy them yourself. Verification usually takes minutes but can take up to 24 hours, and Floot keeps checking while the Email tab is open.
Receiving email
Your app can also receive email at its domain — a support inbox, replies to notifications, mail that turns into tasks. Sending has to be verified first. Then open the domain's ⋮ menu in the Email tab, choose Set up receiving emails, and add the one MX record it shows. A subdomain is the safe choice: receiving on your root domain takes over mail for any mailboxes already there, and Floot warns you when it finds some.
Your assistant writes the code that handles incoming mail. Mail that the spam or virus scan flags is never handed to it; it shows in the Email tab as rejected, with the reason.
Limits and cost
- 1,000 emails a day
- Per project, counted separately for the preview and the published app, per UTC day, on every plan. If a legitimate app needs more, contact support.
- Bulk sending
- For the same email to many people, your assistant uses a bulk send: one template, up to 200 recipients per call, with per-recipient details and unsubscribe headers. It is paced by the mail system, so a long list takes a while.
- Cost
- Email is metered as hosting usage: about $0.30 per 1,000 emails sent and $0.40 per 1,000 received.
Marketing email needs extra care
Every Floot app sends through one shared mail system, so an app that draws spam reports or bounces gets its sending stopped. Email only people who opted in, include an unsubscribe link and the one-click unsubscribe headers, stop mailing addresses that bounced or complained, and send an imported list a small test batch first. Your assistant knows these rules — ask it to follow them.
Bounces and delivery status
The Email tab keeps a log of what your app sent and received. Your app can also read the status of the email it sent — delivered, bounced, complained, or rejected — for 30 days after each send. That is not a permanent history: if you want a record, such as a per-contact bounce flag, ask your assistant to save it in your app's own database.
An address that bounced is blocked
Because the mail system is shared, an address that hard-bounced is blocked for every Floot app, and sends to it are refused without being attempted. If the address works now — say the mailbox was just created — open that email in the Email tab's log, click Allow sending to <address> again, and send it again. You can do this once per address every 30 days, and five times a day per project. An address blocked because its owner marked your mail as spam needs support.
Sharing a domain with your other projects
A verified domain belongs to one project, but other projects you own can send from it too: open the domain's ⋮ menu and choose Share with project…. Their mail goes out under that domain's reputation and appears in the owning project's email log; receiving stays with the owning project. The share stops working if the two projects end up with different owners.
Using your own provider
Floot email is optional. If you already use Resend, SendGrid, Mailgun, Postmark, Amazon SES, or Mailchimp, your app can use that instead — see Connecting external services.