Before starting, make sure you’ve already added your domain in Flowforth. You’ll need the DNS record values shown on the domain settings page.
Open DNS Settings in Cloudflare
- Log in to your Cloudflare account
- Select your domain
- Go to DNS → Records
Add the MX Record
Click Add record:- Set the Type to
MX - Enter the name from Flowforth (e.g.,
send) in the Name field - Copy the MX Value from Flowforth into the Mail Server field
- Set the Priority to
10 - Use the default
Autofor TTL - Click Save
Cloudflare automatically appends your domain to the Name field. Enter only the subdomain portion — for example, type
send instead of send.example.com.| Cloudflare | Flowforth | Example Value |
|---|---|---|
| Type | Type | MX |
| Name | Name | send |
| Mail Server | Value | feedback-smtp.us-east-1.amazonses.com |
| Priority | Priority | 10 |
| TTL | — | Auto |
Add the SPF Record (TXT)
Click Add record:- Set the Type to
TXT - Enter the name from Flowforth (e.g.,
send) in the Name field - Copy the TXT Value from Flowforth into the Content field
- Use the default
Autofor TTL - Click Save
Cloudflare automatically appends your domain to the Name field. Enter only the subdomain portion — for example, type
send instead of send.example.com.| Cloudflare | Flowforth | Example Value |
|---|---|---|
| Type | Type | TXT |
| Name | Name | send |
| Content | Value | "v=spf1 include:amazonses.com ~all" |
| TTL | — | Auto |
Add the DKIM Record (TXT)
Click Add record:- Set the Type to
TXT - Enter the DKIM name from Flowforth (e.g.,
resend._domainkey) in the Name field - Copy the DKIM Value from Flowforth into the Content field
- Use the default
Autofor TTL - Click Save
Cloudflare automatically appends your domain to the Name field. Enter only
resend._domainkey instead of resend._domainkey.example.com.| Cloudflare | Flowforth | Example Value |
|---|---|---|
| Type | Type | TXT |
| Name | Name | resend._domainkey |
| Content | Value | p=example_domain_key_value |
| TTL | — | Auto |
Add the DMARC Record (TXT)
While not strictly required, adding a DMARC record is highly recommended. It improves deliverability and protects your domain’s reputation.If your domain already has a DMARC record, you do not need to add another one. You can check by looking for an existing
TXT record with the name _dmarc in your Cloudflare DNS records.- Set the Type to
TXT - Enter the DMARC name from Flowforth (e.g.,
_dmarc) in the Name field - Copy the DMARC Value from Flowforth into the Content field
- Use the default
Autofor TTL - Click Save
| Cloudflare | Flowforth | Example Value |
|---|---|---|
| Type | Type | TXT |
| Name | Name | _dmarc |
| Content | Value | v=DMARC1; p=none; |
| TTL | — | Auto |
Add the Tracking Records (Optional)
If you enabled click tracking or open tracking when adding your domain in Flowforth, you’ll need to add these two additional records. You can also enable tracking later from the domain detail page in Flowforth — the records will appear in your DNS table when tracking is turned on.CNAME Record (Tracking)
Click Add record:- Set the Type to
CNAME - Enter
linksin the Name field - Enter
links1.resend-dns.comin the Target field - Make sure the Proxy status is set to DNS only (grey cloud icon)
- Use the default
Autofor TTL - Click Save
| Cloudflare | Flowforth | Value |
|---|---|---|
| Type | Type | CNAME |
| Name | Name | links |
| Target | Value | links1.resend-dns.com |
| Proxy | — | DNS only (grey cloud) |
| TTL | — | Auto |
CAA Record (Tracking)
Click Add record:- Set the Type to
CAA - Enter your domain in the Name field (e.g.,
example.comor@) - Set the Tag to
issue - Enter
amazon.comin the CA domain name field - Use the default
Autofor TTL - Click Save
| Cloudflare | Flowforth | Value |
|---|---|---|
| Type | Type | CAA |
| Name | Name | Your domain |
| Tag | — | issue |
| CA domain name | Value | amazon.com |
| TTL | — | Auto |
Verify in Flowforth
Once all records are added in Cloudflare, go back to your domain in Settings → Domains and click the “Records Added” button. Flowforth will check your DNS records and verify the setup in the background.DNS changes can take anywhere from a few minutes to several hours to propagate. If verification doesn’t succeed right away, wait and try again later.
Troubleshooting
- Verification failed: Double-check the records you added in Cloudflare for copy/paste errors. Make sure you’re using only the subdomain portion in the Name field (e.g.,
sendnotsend.example.com). - Priority conflict: If priority
10is already in use on another MX record, use a different value like20or30. - Still not verifying after 72 hours: Contact support@flowforth.co and we’ll help you debug the issue.
If you need help, contact support@flowforth.co.