mailgun

name	mailgun
description	Send emails via Mailgun API. Use when the user needs to send emails programmatically, such as newsletters, notifications, alerts, or automated reports. Requires MAILGUN_API_KEY and MAILGUN_DOMAIN environment variables to be configured.
env	["MAILGUN_API_KEY","MAILGUN_DOMAIN","MAILGUN_FROM","MAILGUN_DEFAULT_TO"]
homepage	https://github.com/openclaw/openclaw
repository	https://github.com/openclaw/openclaw

Mailgun Email Sender

Send emails programmatically using Mailgun's HTTP API.

Prerequisites

Configure the following environment variables in ~/.zshrc or ~/.bash_profile:

export MAILGUN_API_KEY="key-xxxxx"      # Your Mailgun private API key
export MAILGUN_DOMAIN="mg.yourdomain.com"  # Your Mailgun domain
export MAILGUN_FROM="Sender <[e-mail]>"  # Default sender
export MAILGUN_DEFAULT_TO="[e-mail]"  # Default recipient (optional)

Then reload your shell configuration:

source ~/.zshrc

Usage

Send a simple email

mailgun/scripts/send_email.sh "Subject" "Email body text"

Send to a specific recipient

mailgun/scripts/send_email.sh "Newsletter" "Content here" "[e-mail]"

Send with custom sender

mailgun/scripts/send_email.sh "Alert" "System down" "[e-mail]" "[e-mail]"

Features

• Simple command-line interface
• Uses environment variables for configuration
• Supports custom sender and recipient
• Returns success/error status codes
• Works with HTML content (pass HTML in body parameter)

Common Use Cases

• Daily/weekly newsletters
• System alerts and notifications
• Automated reports
• Confirmation emails
• Scheduled reminders

Troubleshooting

Error: MAILGUN_API_KEY and MAILGUN_DOMAIN must be set → Configure environment variables as shown in Prerequisites

Error: 401 Unauthorized → Check that your API key is correct and active

Error: 404 Not Found → Verify your MAILGUN_DOMAIN is correct

References

• Mailgun Documentation: https://documentation.mailgun.com/
• API Reference: See references/api.md