Block 1 - Schedule Trigger
- Type / Role
- n8n-nodes-base.scheduleTrigger - scheduleTrigger
- Config choices
- Version 1.1
What Is This? This workflow monitors your Elastic Email subaccounts daily and sends a Slack alert whenever an account's email credit balance drops below a configurable ...
n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.set, n8n-nodes-base.slack, n8n-nodes-base.filter, n8n-nodes-base.stickynote, n8n-nodes-base.code
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Łukasz.
Original n8n.io sourceThis workflow monitors your Elastic Email subaccounts daily and sends a Slack alert whenever an account's email credit balance drops below a configurable threshold. It's a simple but essential guard against unexpected sending failures caused by depleted credits.
Any team or agency managing multiple Elastic Email subaccounts — marketing departments, email service providers, or developers running automated email campaigns — who want proactive warnings before credits run out.
The workflow runs once a day on a schedule. It calls the Elastic Email REST API to retrieve all subaccount data, then filters out any accounts with a credit balance below the minimum you define in the Config node. If any low-credit accounts are found, a Slack message with all accounts their email address and current credit balance will be sent. API errors are caught separately and also reported to Slack.
Prerequisites:
Step 1: Set the credit threshold
In the Config node, set Minimum amount of Email Credits to the value below which you want to be notified (default: 100).
Step 2: Configure Elastic Email credentials
In the Load EE Subaccounts HTTP Request node, create a new Custom Auth credential with the following JSON:
{
"headers": {
"X-ElasticEmail-ApiKey": "<Your EE Auth Token>"
}
}
You can generate an API token directly in your Elastic Email account settings.
Step 3: Configure Slack credentials
Connect your Slack workspace using OAuth2 in both Slack nodes, and update the channel ID to your desired notification channel.
Need help? Reach out at [email protected] or visit sailingbyte.com.
Happy hacking!
This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Monitor Elastic Email subaccount credits and send low-balance alerts to Slack |
|---|---|
| Complexity | intermediate |
| Nodes | 10 |
| Categories | DevOps |
| Author | Łukasz |
| Published | 28 Apr 2026 |
Use the JSON export at /data/workflows/15374/15374.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
What Is This? This workflow monitors your Elastic Email subaccounts daily and sends a Slack alert whenever an account's email credit balance drops below a configurable ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.