mailgun-api_skill

Overview

This skill integrates Mailgun via a managed OAuth gateway to send, receive, and track transactional email. It proxies requests to Mailgun API (default US region) and injects your OAuth token so you can manage domains, messages, templates, routes, lists, suppressions, webhooks, and stats with simple HTTP calls. Use the Maton API key for authentication and optionally specify a connection when you have multiple Mailgun accounts.

How this skill works

Requests are sent to the gateway base URL https://gateway.maton.ai/mailgun/v3/{resource} which forwards to Mailgun's API and injects the configured OAuth credentials. All calls require the Authorization: Bearer $MATON_API_KEY header; specify Maton-Connection when selecting a non-default OAuth connection. POST/PUT bodies must use application/x-www-form-urlencoded (or multipart/form-data for MIME), while GETs use query parameters and Mailgun cursor-based pagination.

When to use it

• Send transactional emails from applications or back-end jobs.
• Manage Mailgun domains, credentials, tracking, and DNS-related settings.
• Create and update templates, mailing lists, and list members.
• Configure routes and inbound forwarding or storage actions.
• Manage suppressions (bounces, unsubscribes, complaints, whitelists) and view delivery events or stats.

Best practices

• Store MATON_API_KEY in environment variables and never hard-code secrets.
• Use application/x-www-form-urlencoded for form requests and multipart for MIME messages.
• Specify Maton-Connection header when working with multiple Mailgun accounts to avoid accidental use of the default connection.
• Limit results with the limit parameter and follow paging links to iterate large result sets.
• Use tags, custom variables (v:), and tracking options to tie events to application context for easier analytics.

Example use cases

• Send password reset, account verification, or purchase receipts using domain-specific templates.
• Automate inbound email handling by creating routes that forward or store messages to webhooks.
• Run suppression hygiene: list bounces, remove bad addresses, and add trusted senders to whitelists.
• Collect and analyze delivery events (delivered, opened, clicked) for campaign and transactional diagnostics.
• Create and manage mailing lists and programmatically add or remove subscribers.