A connected bot can configure mail the same way Settings → Sending domains does in the app: add a Cloudflare domain for sending and receiving, then create aliases such as [email protected]. You still connect the bot once (OAuth or an API key). After that, you can ask in chat instead of clicking through the UI.
The four setup tools
These tools sit next to the existing mail tools. They do not send or read messages:
list_domains— every sending/receiving domain on the account, the mailboxes on each one, and whether the next extra domain would need Paddle. Does not charge.add_domain— start a domain (for examplewinos.lol). FlareMail provisions Cloudflare Email Sending and inbound Email Routing when it can. Optionaldisplay_namesets the From name. Optionallocal_partcreateshello@only after the domain is already verified.create_mailbox— add an alias on a verified domain. Passlocal_partplusdomain(hello+winos.lol) or a fulladdress([email protected]). Optionaldisplay_name. Does not send mail.get_domain_setup— DNS and Email Routing status plus the next human step. Setrefresh=trueto re-check Cloudflare verification and retry inbound routing.
Add an alias on a domain you already have
This is the common path once winos.lol (or any domain) is already verified in FlareMail:
- Ask the bot to list domainsIt should call
list_domainsand show status (verified / pending) and receiving (on / off / error). - Create the mailboxAsk for
[email protected](or support@, you@, …). The bot callscreate_mailboxwithlocal_partanddomain, or withaddress. - Confirm it landedThe new address appears under that domain and in
list_mailboxes. Use it asfromon drafts and sends.
List my FlareMail domains, then create [email protected].
Add a new sending + receiving domain
Your first domain is free. The domain must already be an active zone on the Cloudflare account connected to FlareMail. Then:
- Name the hostnameAsk the bot to add
winos.lol(or your domain). It callsadd_domain. - Watch next_stepsIf Cloudflare wrote DNS, verification is usually quick. If the tool returns pending DNS or leftover MX, call
get_domain_setupwithrefresh=true, or open the app and click Verify / Fix receiving. - Create the first aliasOnce status is verified, call
create_mailboxforhello@(or passlocal_partonadd_domainonly if the domain is already verified).
Extra domains: the bot never charges
The first sending domain is free. Each additional domain is $9.99/mo through Paddle — same as adding it in the app. The MCP path will not increase your subscription or open a hidden checkout.
- If a seat is still needed,
add_domainreturnsrequires_payment: true, the $9.99/mo price, acheckout_urlofhttps://app.sendwithflare.com, and next steps. - Open Settings → Sending domains in the app and add the domain there. Paddle checkout runs in the app.
- After payment completes, ask the bot to call
add_domainagain (orlist_domainsto confirm). - If billing is past due, the bot returns that code and tells you to update the card from the Paddle receipt — it will not retry a failed charge.
When setup still needs a human
- Pending DNS — records are usually written automatically. Wait a minute, then
get_domain_setupwithrefresh=true. If it stalls, confirm the returneddns_recordsin Cloudflare DNS. - Receiving not live — leftover MX (Google, Microsoft, WordPress
_dc-mx) must be replaced with Cloudflare Email Routing. In the app: Settings → Sending domains → Fix receiving. - Unverified domain —
create_mailboxis rejected until the domain is verified. Useget_domain_setup, then retry.
Prefer the app?
The same flow lives in Settings → Sending domains. See Add a sending domain. Manual inbound routing (when you are not using automatic provisioning) is Connect Cloudflare Email Routing.