Mailgun

Mailgun API (Email marketing), 83 operations: send email (attachments, templates, tags, scheduling, tracking, batch recipient variables) and raw MIME, stored-message retrieval and resend, sending queues; templates and template versions; bounce, unsubscribe, complaint and allowlist suppressions; mailing lists and members including bulk add and list validation; inbound routes; domain and account webhooks; logs, events, metrics and tags; domains; and email validation. US and EU regions.

Credential: Mailgun private API key - see Credentials.

API key types

Each operation below lists the API key type it needs. API key types are decided when the key is created in the Mailgun dashboard. Mailgun has no OAuth, no consent screen and no per-endpoint scopes - but it is not scope-free either, because it issues two kinds of key with very different reach. The primary account API key (Account Settings > API Keys > Private API key) can call every endpoint below for every sending domain. A Domain Sending Key (Sending > Domains > your domain > Domain Settings > Sending API keys) can call exactly two of them - POST /messages and POST /messages.mime, and only for the domain it was created under - so a sending key pasted into this node works for Send email and 401s on all 81 other operations. That is the single most common Mailgun credential mistake. A second axis fails identically without being a permission at all: keys are per-REGION, so a US key used against api.eu.mailgun.net (or the reverse) is indistinguishable from a wrong key - check the node's Region field before rotating anything. If a run fails with a permission error, the node names the missing API key type in the error - grant it and re-run; you do not need to rebuild the workflow.

Operations (83)

Messages

Templates

Suppressions: bounces

Suppressions: unsubscribes

Suppressions: complaints

Suppressions: allowlist

Mailing lists

Routes (inbound email)

Domain webhooks

Account webhooks

Logs, metrics & tags

Domains

Email validation

Example

Send from an EU-region Mailgun account

Mailgun runs two independent regions with separate hosts, separate accounts and separate API keys. The node hardcoded the US host until SW21-era work, which meant an EU customer's every call 401'd with nothing explaining why. region is a node field rather than a credential field so existing credentials did not need migrating; it defaults to us, so saved workflows keep hitting the host they always did.

Set Operation to sendMessage, then fill in:

Sets {{mail.id}} (Mailgun's queued message id) and {{mail.message}}.