If you use Elastic Email to manage multiple subaccounts, running out of credits can stop important messages, marketing campaigns, or automated notifications sent by your systems. The problem is that with several or even dozens of subaccounts, it is easy to miss the moment when one account’s balance starts getting close to zero.
That is why I created a free n8n automation that checks the available Email Credits across all Elastic Email subaccounts once a day and sends a Slack alert before the credits run out.
Instead of checking the Elastic Email dashboard manually, you can automatically receive a notification exactly when your attention is required.
Why should you monitor Elastic Email credits?
Automated emails are often part of a larger business process.
They can include:
- transactional emails,
- registration and order confirmations,
- user notifications,
- marketing campaigns,
- messages generated by SaaS applications,
- automated reports and alerts.
If the credit balance is depleted, email sending may stop. In many cases, the problem only becomes visible when messages are no longer reaching recipients.
With a single account, checking the balance manually may still be manageable. With multiple subaccounts, however, it quickly becomes another repetitive task you need to remember about.
Automation reverses this process.
You do not have to check whether everything is fine. The system will notify you when something starts to require attention.
Who is this automation for?
The workflow is designed primarily for companies and teams managing multiple Elastic Email subaccounts.
It can be useful for:
- software houses managing client infrastructure,
- marketing agencies,
- email service providers,
- teams running multiple email campaigns,
- SaaS companies using separate accounts or subaccounts for different products and clients,
- administrators responsible for maintaining the continuity of email delivery systems.
The more subaccounts you manage, the more value automated monitoring can provide.
How does the automation work?
The workflow runs once a day and performs several simple operations.
Step 1: Load Elastic Email subaccounts
The automation connects to Elastic Email through the REST API and retrieves information about the available subaccounts.
This means you do not need to manually define every account that should be monitored.
Step 2: Check available credits
For each subaccount, the workflow checks the current Email Credits balance.
In the Config node, you can define the minimum credit level you consider safe.
The default value is:
100 Email Credits
If the balance of any account drops below the defined threshold, it is included in the warning.
You can easily adjust the threshold to match your email volume. A company sending relatively few messages may use a lower limit, while teams running high-volume campaigns may want to keep a larger safety buffer.
Step 3: Send a Slack alert
If the automation finds subaccounts with a low balance, it prepares a summary message and sends it to the selected Slack channel.
The message includes information about the accounts that require attention, such as:
- the subaccount email address,
- the current number of available credits.
This means you do not receive unnecessary notifications every day. The alert appears only when action is actually required.
Step 4: Report API errors
Monitoring is only useful if you also know whether the monitoring process itself is working correctly.
That is why errors occurring during communication with the Elastic Email API are handled separately and also reported to Slack.
As a result, the absence of low-balance alerts does not simply mean that every account has enough credits. If the workflow cannot retrieve the data, you will be notified about that as well.
How do you configure the workflow?
Configuring the automation involves connecting n8n with Elastic Email and Slack, as well as setting the credit threshold below which an alert should be triggered.
A detailed setup guide, the required credentials, and a description of each configuration step are available directly on the workflow page in n8n.
This allows you to go through the setup step by step and adapt the automation to your own environment.
See the workflow and full configuration guide in n8n: https://n8n.partnerlinks.io/monitor-elasticemail-subaccounts
Why does it run once a day?
When monitoring email credits, there is usually no need to check the balance every few minutes.
Running the workflow once a day provides a reasonable balance: it allows you to detect potential problems early enough without making unnecessary API requests.
However, if your company sends very large volumes of email and credit balances can change quickly, you can easily adjust the schedule in n8n.
The same applies to the alert threshold. The key is to adapt both settings to the actual rate at which your credits are being consumed.
Try it for free
The workflow is available for free and can be used as a ready-made automation or adapted to your own processes.
You can, for example:
- change the minimum credit threshold,
- change how often the workflow runs,
- customize the alert message,
- replace Slack with another notification channel,
- extend the workflow with additional actions triggered when a low balance is detected.
You can find more ready-to-use, free business automations here: https://sailingbyte.com/free-business-automations/
If you see similar repetitive processes in your company that still require manual checking and intervention, contact us and see what automation solutions we can build for your business.
