mailgun-email

Send transactional emails and manage templates via the Mailgun REST API.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Shakudo-io/opencode-skills --skill mailgun-email
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mailgun-email
Source: https://github.com/Shakudo-io/opencode-skills/tree/main/mailgun-email
Command: npx skills add https://github.com/Shakudo-io/opencode-skills --skill mailgun-email

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables developers to programmatically send transactional emails, manage templates, track delivery events, and handle suppressions via the Mailgun REST API.

Core Features & Use Cases

  • Send plain text and HTML emails through Mailgun endpoints
  • Manage templates and send templated emails with variables
  • Track delivery events, bounces, unsubscribes, and complaints for compliance and analytics
  • Handle suppressions to prevent sending to addresses on bounce or unsubscribe lists
  • Use in workflows like transactional notifications, alerts, and onboarding messages

Quick Start

Load your Mailgun credentials from an environment file and run a test email using the API.

Frequently Asked Questions about mailgun-email

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send transactional emails using the Mailgun REST API?

You can send transactional emails by authenticating with a Mailgun API key using HTTP Basic Auth and making REST API requests to US or EU endpoints to deliver plain text or HTML messages.

Can I send templated emails with variables through Mailgun?

Yes, you can manage email templates and send templated emails by passing variables through the Mailgun REST API to dynamically populate message content for transactional notifications.

What credentials do I need to automate Mailgun email delivery?

Automating Mailgun email delivery requires a Mailgun API key, a configured sending domain, and HTTP Basic Auth using 'api' as the username, loaded typically from an environment file.

How does delivery tracking work for Mailgun transactional emails?

Delivery tracking works by monitoring Mailgun events across domains to capture delivery statuses, bounces, unsubscribes, and complaints for compliance and analytics reporting.

How do I handle suppressions to prevent sending to bounced email addresses?

You handle suppressions via the Mailgun REST API by managing bounce and unsubscribe lists to programmatically prevent sending emails to addresses flagged on those suppression lists.