Email with your own domain
How to make your app's emails go out from an address on your domain, such as contact@yourcompany.com, instead of the platform's sender.
The app's emails already work without this. Sign-up confirmation, password reset, invites, automations and notifications go out from day one through a sender managed by Fabapp, with your app's name. Connecting your domain changes who signs: the email starts coming from your brand, which lands better in the inbox and does not look like a scam.
Before you start
- Plan: any paid plan (Starter or above). On Free the button shows a lock and takes you to the plans;
- Access to the domain's DNS, in the dashboard of wherever it is registered or hosted (Registro.br, Cloudflare, GoDaddy and others);
- Cost: connecting costs nothing. The app's automation and notification emails consume integration credits, with or without your own domain.
It is not in the Integrations tab: email lives in the Domains tab, in the EMAIL DOMAIN section, next to the site's domain.
Step by step
- in the app's editor, open the Domains tab;
- in the EMAIL DOMAIN section, in the Email sender box, click Use your own domain;
- in Sending domain, enter the domain. The screen recommends a dedicated subdomain (for example,
mail.yourcompany.com) to protect the main domain's reputation; - in Sending address (From), choose the part before the
@(the default isno-reply). The domain is filled in automatically; - in Sender name, write the name the recipient will read;
- click Continue. The screen now shows the Email DNS records;
- in your DNS dashboard, create each one of the records, copying the name, the type and the value exactly as they appear;
- go back to the Domains tab and click Verify.
The DNS records
The list comes ready to copy and has four types of record:
| Record | How many | What it is for |
|---|---|---|
| CNAME (DKIM) | 3 | signs each message, proving it came from your domain. This is what unlocks verification |
| MX | 1 | receives bounced-email notices, on a bounce. subdomain of your sending domain |
| TXT (SPF) | 1 | authorizes sending, on the same bounce. subdomain |
| TXT (DMARC) | 1 | sets the alignment policy, at _dmarc. of your sending domain |
The three DKIM CNAMEs are the ones that decide verification. Publish every record the list shows anyway: SPF and DMARC improve delivery and keep providers like Gmail from treating the message as suspicious. In some cases the MX and SPF do not appear; then publish the ones that do, and sending stays signed by DKIM.
DNS propagation can take from a few minutes up to 48 hours.
How to know it worked
- the email domain shows Connected in the Domains tab. While the records are not found, it stays Pending;
- the Email sender box now shows your address and the sender name;
- trigger a real email (for example, "forgot my password" in the app) and check the sender in the inbox.
While the domain is not verified, the app keeps sending through the platform's sender. Nothing stops working during the wait.
Common problems
- It stays Pending for hours. The most common case is the duplicated name: many DNS dashboards complete the domain on their own, and pasting the full name produces something like
abc._domainkey.yourcompany.com.yourcompany.com. On those dashboards, paste only the part before your domain; - The dashboard does not accept the CNAME. Some dashboards (Cloudflare, for example) offer a "proxy" on the record. Leave the email record as DNS only, with no proxy;
- A DMARC record already exists. A domain can only have one TXT at
_dmarc. If there is one already, keep the existing one instead of creating a second; - Error saying the sender has to belong to the domain entered. The sending address has to end in the same sending domain;
- I want to go back to the platform's sender. Open the email domain under Manage and click Remove.