Mailgun

Mailgun (mailgun.com). Use this skill for ANY Mailgun request — reading, creating, updating, and deleting data. Whenever a task involves Mailgun, use this skill instead of calling the API directly.

Operate Mailgun through your OOMOL-connected account. This skill calls the mailgun connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Communication, Marketing. Exposes 17 action(s).

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Mailgun. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "mailgun" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "mailgun" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

• add_suppression — Add one Mailgun suppression or allowlist record.
• create_template — Create a Mailgun template and optionally its initial active version.
• create_template_version — Create a new version for a Mailgun template.
• delete_suppression — Remove one Mailgun suppression or allowlist record.
• get_domain — Get Mailgun domain details including DNS records and sending state.
• get_domain_tracking_settings — Get open, click, unsubscribe, and web scheme tracking settings for a domain.
• get_suppression — Get one Mailgun suppression or allowlist record.
• get_template — Get metadata for one Mailgun template and optionally its active version.
• get_template_version — Get content and metadata for one Mailgun template version.
• list_domains — List Mailgun domains available to the current API key.
• list_events — List delivery, engagement, and failure events for a Mailgun domain.
• list_suppressions — List records from a Mailgun suppression or allowlist table.
• list_template_versions — List versions for a Mailgun template.
• list_templates — List templates stored for a Mailgun domain.
• send_email — Send an email through Mailgun using a stored domain.
• update_domain_tracking_settings — Update open, click, or unsubscribe tracking settings for a Mailgun domain.
• verify_domain — Ask Mailgun to verify DNS records for a sending domain.

Safety

• Read actions (get / list / search) are safe to run directly.
• Create, update, send, or post actions change Mailgun state — confirm the exact payload and effect with the user before running.
• Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Mailgun is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  https://console.oomol.com/app-connections?provider=mailgun
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Mailgun homepage: https://www.mailgun.com