This page answers "does Atriomail work with X?" for WHMCS, the REST API, automation tools such as n8n, Blesta, DNS hosts, portal sign-in links and migration sources. For each one it says what you can connect, what the connection does, and where it stops.

At a glance

Integration Status What it does Limits
WHMCS provisioning module Available (version 3.1.1) When a client orders an Atriomail product in WHMCS, the module creates the client's Atriomail account and email domain, plus the first mailbox if the domain clears the security check during the order. Service actions: Create, Suspend, Unsuspend, Terminate and Change Package. Requires WHMCS 9. Changes made in the Atriomail panel or through the API do not sync into WHMCS billing on their own. Details on the WHMCS module page.
REST API Available Authenticates with an API key in the X-API-KEY header. Covers domains, mailboxes, forwarders, catch-alls, mailbox storage, customer accounts, IMAP migration jobs, DNS record checks and single-use sign-in links. Up to 30 requests per minute. DNS record checks also count against a separate allowance for each account. It does not cover everything you can do in the panel. A key carries the full permissions of the account that created it.
n8n and other automation tools Available through the REST API n8n's HTTP Request node, or any tool that can send HTTPS requests with a custom header, calls the API with your key. No native n8n node. The API's coverage and its limit of 30 requests per minute apply. Details on the n8n page.
Blesta No working integration today Atriomail does not offer a working Blesta integration today. A Blesta setup would have to be built on the REST API.
Cloudflare DNS and Namecheap DNS Available with a connected DNS account Atriomail imports the account's domain list. For a domain from that account that passes the security check, Atriomail can write MX, SPF, DMARC, autodiscover and autoconfig records, plus the DKIM key, into the zone. The domain's DNS must be hosted in the connected account, and the domain must already be there when you add it in Atriomail; otherwise it shows "DNS Automation Pending" and you add the records by hand. Writing the MX record moves that domain's mail, so add the domain when you are ready to switch, then delete any MX record that still points at your old provider.
Other DNS hosts, including Amazon Route 53 and DNSimple Route 53 and DNSimple: add the records from the DNS Setup dialog. Other hosts: check with us Without a connected DNS account, every domain has a DNS Setup dialog that lists the records to add at the DNS host, each with a copy button. Automatic mail DNS, including the DKIM key, is built for Cloudflare and Namecheap. Check with us before you connect any other DNS account in the control panel.
Single-use sign-in links for your portal Available through the REST API (the WHMCS module uses them too) Your billing system or portal requests a link that takes a customer straight into their Atriomail control panel. Each link is valid for 60 seconds and works once. It is not SAML or OpenID Connect, and it does not sign the customer in to webmail.

Not on this list? If a tool is not listed here as available, do not assume it works. Ask us before you promise it to a client.

WHMCS provisioning module

Atriomail has a WHMCS provisioning module, version 3.1.1. It was rebuilt in 2026 and tested end to end in a WHMCS 9 install against the live platform. It requires WHMCS 9, and the WHMCS product must be a Hosting Account or Reseller Account type.

What the module does

  • Orders. When a client orders an Atriomail product in WHMCS, the module creates the client's Atriomail account and email domain. It also creates the first mailbox if the domain clears the security check during the order.
  • Service actions. The complete list is Create, Suspend, Unsuspend, Terminate and Change Package, plus a Test Connection check.
  • Suspend and Unsuspend. Suspending in WHMCS deactivates the client's domain on Atriomail. Unsuspend reactivates it.
  • Terminate. Deletes the domain with its mailboxes and aliases, and removes the recurring charges the module added in WHMCS. Deletion is permanent.
  • Change Package. Updates the domain's mailbox and storage limits. A downgrade below current usage is refused.
  • Client area. Clients get Dashboard, Mailboxes, Aliases, Catch-all and My Domains pages. Within the product's limits, they add and delete mailboxes, change mailbox passwords, add or remove 5 GB storage blocks, manage aliases and set a catch-all without leaving WHMCS. Clients with several Atriomail services see all their domains on one My Domains page.
  • Client Dashboard. It shows setup progress, the MX, SPF and Amazon SES records to add, verification status, IMAP and SMTP settings, and usage. It displays the records; it does not publish them.
  • Setup reminders. Clients get reminder emails 1 and 3 days after the security check if the domain is still not verified, and a notice when it goes live. This needs the WHMCS daily cron.
  • Control panel access. Clients open their Atriomail control panel from the WHMCS client area with a single-use sign-in link, valid for 60 seconds. It does not sign in to webmail.
  • Admin view. WHMCS admins get a setup checklist on the product page and a per-service tab showing the linked account and domain, verification status, the mailbox list with usage and the last API error, with buttons to re-check verification, re-sync, reset a mailbox password and resend the welcome email.

Billing in WHMCS

You set the price per mailbox and per 5 GB storage block on the WHMCS product. Mailboxes and storage that clients add in the WHMCS client area are billed as recurring WHMCS charges at your retail prices. The module generates the storage add-on options in 5 GB steps up to 100 GB, in every currency and billing cycle you have configured. The product's default limits are 5 mailboxes and 15 GB of base storage, so raise them for bigger clients.

Changes made in the Atriomail panel or through the API do not sync into WHMCS billing on their own. If you change a client's service outside WHMCS, check their recurring charges in WHMCS afterwards.

Getting the module

Account holders download the module from the Plugins page in the Atriomail control panel. It installs by uploading files, with no shell access needed. It is also listed on the WHMCS Marketplace: search for AtrioMail under Provisioning Modules. The Plugins page carries the latest build, and the Marketplace listing can lag behind it. The module never writes your Atriomail API key to the WHMCS module log, and it masks passwords.

For setup steps and the full feature list, see the WHMCS module page and the longer guide to selling email in WHMCS with the Atriomail module.

REST API

The Atriomail REST API authenticates with an API key sent in the X-API-KEY header. It covers these areas:

  • domains
  • mailboxes
  • forwarders
  • catch-alls
  • mailbox storage
  • customer accounts
  • IMAP migration jobs
  • DNS record checks
  • single-use sign-in links

It does not cover everything you can do in the panel, so check that the calls you need exist before you plan a build around them.

API keys and rate limit

  • API keys are created in the panel and shown in full once. They are stored hashed, can have an expiry date, and can be switched off or regenerated.
  • A key carries the full permissions of the account that created it, so store it like a password.
  • Repeated failed attempts are temporarily locked out.
  • The API allows up to 30 requests per minute.
  • DNS record checks also count against a separate allowance for each account.

What resellers can do with the API

  • Customer accounts. Create customer accounts, and domains owned by those customers. Retrying a customer creation returns the existing account instead of an error.
  • Per-domain caps. Cap a domain's mailbox count and total storage through the API or the WHMCS module (not in the panel). Requests over the cap are refused, and a cap cannot be lowered below current usage.
  • Provisioning state. New domains go through an automated security check, and the API reports each domain's state: screening, review, ready or rejected.
  • DNS records and mail settings. The API returns the DNS records a domain needs (MX, SPF, Amazon SES verification and DKIM, and the domain's DKIM key) and the IMAP and SMTP settings to give end users.
  • Migration jobs. IMAP migration jobs can be created, updated, paused and removed, using a password or an app password.
  • Sign-in links. See single-use sign-in links below.

n8n and other automation tools

There is no native n8n node and no ready-made n8n integration. n8n's generic HTTP Request node can call the Atriomail REST API: send your API key in a header named X-API-KEY. Any automation tool that can send HTTPS requests with a custom header can do the same.

Whichever tool sends the request, the API's coverage and its limit of 30 requests per minute apply. Atriomail does not push notices to your workflows when a mailbox or domain is changed in the panel, through the API or through the WHMCS module, so a workflow reads the current state from the API when it needs it. The n8n page walks through the setup.

Blesta

Atriomail does not offer a working Blesta integration today. A Blesta setup would have to be built on the REST API described above. If you are planning one, talk to us first so you know what the API covers before you write code.

DNS hosts

Cloudflare and Namecheap

Automatic mail DNS, including the DKIM key, is built for Cloudflare and Namecheap. Connect your Cloudflare or Namecheap account in the Atriomail control panel and let Atriomail import its domain list. When you then add one of those domains and it passes the security check, Atriomail can write the mail records into that zone: MX, SPF, DMARC, autodiscover and autoconfig, plus the DKIM key.

  • DNS must be hosted there. The domain's DNS must be hosted in the connected account. Records written there only take effect if the domain's nameservers point to that account, so having the domain registered there is not enough on its own.
  • Order matters. The domain must already exist in the connected DNS account. Connect the provider, let it import the domains, then add the domain in Atriomail. Otherwise the domain shows "DNS Automation Pending" and you add the records by hand. If a domain is pending, only move it into the connected DNS account once you are ready to switch its mail.
  • Writing the MX record moves mail. On a connected account, the MX record is written as soon as the domain clears the security check, and that starts moving the domain's mail. Add the domain when you are ready to switch. Then check the zone and delete any MX record that still points at your old provider. Mail servers try the MX record with the lowest preference number first (RFC 5321, section 5.1), so until you delete the old record, some or all of the domain's mail can keep going there.
  • Existing records. Atriomail reads the zone first and, when it finds an existing SPF or DMARC record, leaves it in place instead of adding a second one. It does not edit that record either, so compare an existing SPF record with the SPF value in the DNS Setup dialog and merge in anything it is missing yourself. A domain should publish only one SPF record (RFC 7208, section 3.2).
  • Branded mail hostnames. For a white-label reseller's customers, the automation writes the reseller's branded mail hostname, as long as that hostname points at the mail server. White-label is a paid add-on.

The step-by-step walkthrough is in connecting Cloudflare and Namecheap for automatic mail DNS.

Amazon Route 53, DNSimple and other DNS hosts

On Amazon Route 53 and DNSimple, add the records yourself from the DNS Setup dialog, and do not connect those accounts in the control panel without checking with us first. For any other DNS host, check with us before you connect its account or rely on automation.

Without a connected DNS account, every domain has a DNS Setup dialog listing the records to add at the DNS host: MX, SPF and DMARC, plus the DKIM key and the Amazon SES verification records once they are generated. Each record has a copy button.

Checking the records

  • Each domain shows its DNS status in the panel, with a refresh button that re-checks the live records on demand.
  • In the panel and through the API, you can check your own domains against their exact DKIM key and Amazon SES records, before and after a cutover.
  • Anyone can use the free DNS checker without an account. Enter a domain to see whether its MX, SPF, DKIM and DMARC records exist and are well-formed, with a suggested fix for anything missing. It reads public DNS only, and DKIM uses the selector you type.

If a record type is unfamiliar, the email hosting glossary explains MX, SPF, DKIM and DMARC.

Your billing system or customer portal can request single-use sign-in links through the REST API. Each link takes a customer straight into their Atriomail control panel, is valid for 60 seconds and works once. The WHMCS module uses the same kind of link in its client area.

This is not SAML or OpenID Connect. The link signs the customer in to the control panel only; it does not sign them in to webmail.

Migration sources

IMAP migration is built into the panel and has no charge; you pay only for the mailboxes you move mail into. The tool copies mail from:

  • Any server that allows IMAP sign-in with a password, such as typical hosting mail on cPanel, Plesk or DirectAdmin servers. This is a mail copy over IMAP, not a control panel integration.
  • Gmail and Google Workspace, with an app password. Google requires 2-Step Verification for app passwords, and a Workspace admin can block them.
  • Yahoo Mail and iCloud Mail, with an app-specific password from that provider.

Microsoft 365 and Exchange Online mailboxes cannot be moved with the built-in tool, because Microsoft no longer allows password sign-in over IMAP. Outlook.com and Hotmail accounts are not a supported source either. The built-in tool's provider list includes an Outlook/Office 365 entry, and choosing it does not change this. Talk to us before you quote any of these moves to a client.

What the tool does:

  • It keeps the folder structure and the original date on every message. It moves mail only; calendars and contacts are not copied.
  • For a single-mailbox job, the panel tests the sign-in for both the old and the new mailbox before it starts, so a wrong password shows up in seconds.
  • A job can be run as a dry run first, or scheduled for later.
  • Bulk migration lists many mailboxes from the same old server in one job and tracks how many completed or failed. Every account needs its own password, and large books should be planned with us first.
  • Jobs can also be created, updated, paused and removed through the REST API.

What is not available today

People often ask about these. Atriomail does not offer any of them:

  • A working Blesta integration.
  • A native n8n node.
  • Support for WHMCS 8.
  • Notices pushed to your own systems when a mailbox or domain is changed in the panel, through the API or through the WHMCS module.
  • Sign-in through SAML or OpenID Connect, or sign-in links that open a signed-in webmail session.
  • Automatic syncing of changes made in the Atriomail panel or API into WHMCS billing.
  • Moving Microsoft 365 or Exchange Online mailboxes with the built-in tool.

For DNS hosts other than Cloudflare and Namecheap, see Amazon Route 53, DNSimple and other DNS hosts above.

Common questions

Does Atriomail work with Blesta?

Not today. Atriomail does not offer a working Blesta integration, so a Blesta setup would have to be built on the REST API. The API covers domains, mailboxes, forwarders, catch-alls, mailbox storage, customer accounts, IMAP migration jobs, DNS record checks and single-use sign-in links.

Is there a native n8n node for Atriomail?

No. There is no native n8n node and no ready-made n8n integration. n8n's HTTP Request node can call the Atriomail REST API with your API key in the X-API-KEY header, and the same approach works in any automation tool that can send HTTPS requests with a custom header.

Which DNS hosts get mail records written automatically?

Cloudflare and Namecheap. Connect the DNS account and let Atriomail import its domain list, then add a domain from that account. Once the domain passes the security check, Atriomail can write its MX, SPF, DMARC, autodiscover and autoconfig records and its DKIM key into the zone. Writing the MX record moves that domain's mail, so add the domain when you are ready to switch, then delete any MX record in the zone that still points at your old provider. On Amazon Route 53 and DNSimple, add the records from the DNS Setup dialog. For those and any other DNS host, check with us before you connect the account in the control panel.

Is WHMCS 8 supported?

No. The module, version 3.1.1, requires WHMCS 9. It was rebuilt in 2026 and tested end to end in a WHMCS 9 install against the live platform.

Do changes made in the Atriomail panel or API sync into WHMCS billing?

Not on their own. Mailboxes and storage that clients add in the WHMCS client area are billed as recurring WHMCS charges at your retail prices. Changes made in the Atriomail panel or through the API do not sync into WHMCS billing on their own, so check the client's recurring charges in WHMCS after you change their service outside WHMCS.

Does Atriomail notify my systems when a mailbox or domain changes?

Not for changes made in the panel, through the API or through the WHMCS module. Atriomail does not push notices to your systems when mailboxes or domains are added, changed, suspended or deleted there. A system that needs current data reads it from the REST API, which allows up to 30 requests per minute.