sinch-mailgun

Authenticate and manage Mailgun API workflows for transactional email delivery and tracking.

9|4|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/sinch/skills --skill sinch-mailgun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-mailgun
Source: https://github.com/sinch/skills/tree/main/skills/sinch-mailgun
Command: npx skills add https://github.com/sinch/skills --skill sinch-mailgun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Mailgun (Sinch) provides a unified email API and SMTP relay to send, receive, track, and manage emails, domains, webhooks, and templates, reducing integration friction and operational overhead.

Core Features & Use Cases

  • Email delivery via REST API, SMTP, and templates with domain management and webhooks.
  • Inbound routing, delivery tracking, suppression management, and analytics across regions.
  • Use case: Build a reliable transactional email system for onboarding, password resets, alerts, and notification campaigns.

Quick Start

Authenticate and configure your Mailgun domain to begin sending and tracking emails.

Frequently Asked Questions about sinch-mailgun

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

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

You can send transactional emails via the Mailgun API by authenticating with basic authentication using your domain-specific API key. This allows you to trigger reliable sending for onboarding flows, alerts, and password resets through REST API endpoints.

Can I track email delivery and manage suppressions across different regions?

Yes, you can track email delivery and manage suppressions across regions using the Mailgun API. It provides comprehensive analytics, delivery tracking, and suppression management to monitor transactional email workflows effectively.

How do I configure inbound routes and webhooks for receiving emails?

Configuring inbound routes and webhooks for receiving emails is handled through the Mailgun API. You can set up inbound routing and webhook configurations to process incoming messages and trigger application events based on email activity.

Does the Mailgun API support domain management and email templates?

Yes, the Mailgun API supports comprehensive domain management and email templates. You can authenticate with domain-based keys to configure, manage, and apply templates for your transactional email workflows across v4 and v3 endpoints.

What is the best way to manage domain configuration for production email use cases?

The best way to manage domain configuration for production email use cases is through the Mailgun REST API. It supports domain-based keys and comprehensive management to satisfy reliable sending, delivery tracking, and routing requirements.

Why do I need domain-based keys for Mailgun API authentication?

Domain-based keys are required for Mailgun API authentication to ensure secure access to your specific sending domains. This basic authentication method validates your requests for sending, tracking, and managing emails via the REST API.