Monitor Elastic Email subaccount credits and send low-balance alerts to Slack
Ready for 3.0What this workflow does
This workflow has 7 nodes and runs on a schedule (every day at 04:00). Along the way it connects Slack. It also calls api.elasticemail.com over HTTP.
How it runs
Trigger: On a schedule (every day at 04:00).
- Config (Edit Fields (Set)): sets or maps fields
- Load EE Subaccounts (HTTP Request): calls api.elasticemail.com
- Check if account has enough email credits (Filter): keeps only the items that match a condition
- Send a Error message (Slack): uses Slack
- Prepare message content (Code): runs custom JavaScript code
- Send notification about low Email Credits (Slack): uses Slack
Services it uses
HTTP calls to: api.elasticemail.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (6)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - Slack
n8n-nodes-base.slack - Filter
n8n-nodes-base.filter - Code
n8n-nodes-base.code
From the author
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 threshold. It's a simple but essential guard against unexpected sending failures caused by…