Integrations / Mailgun

Mailgun

Mailgun transactional email delivery — send messages, and inspect sending domains, mailing lists, and deliverability stats/events.

Basic auth

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A Mailgun account you can administer.

Admin who can create API keys under Settings.

Vendor setup

Get the credential

Open API keys

In Mailgun, go to Settings → API Keys (or Account settings → API security).

Create a private key

Click Create Private API key. Name it for Telara. Copy it. Mailgun uses HTTP Basic: the username is api and the password is the private key — Telara’s form maps this for you.

Paste in Telara

Settings → Integrations → Mailgun. Paste the private API key. Pick US vs EU if the form asks — it must match the region of the domain.

In Telara

Connect in Telara

Basic auth

Mailgun uses HTTP Basic auth (confirmed against the spec's securitySchemes: type=http, scheme=basic) with the literal string "api" as the username and your Mailgun private API key as the password — NOT your account email or any other value. When creating this credential: store the field "username" as exactly "api", and store your Mailgun private API key (Account Settings > API Keys > Private API key) in "api_key". Also store "domain" (your verified sending domain, e.g. "mg.example.com") and, for EU-region Mailgun accounts only, "region_base_url" set to "https://api.eu.mailgun.net/v3" — both are optional convenience fields consumed by this catalog's param/credential fallback and auto_fill mechanisms (see api.base_url and the domain param on send_email/get_domain/get_domain_stats/get_domain_events below); omit region_base_url entirely for US accounts (default).

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for

Username
API key

Knowledge

What gets indexed

Resource	Coverage
Domain	Partial — not every record the vendor holds is synced
List	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Domain	Up to 1 day	Removed records disappear on the next full sync
List	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Domain, List.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Public keys cannot read events. Telara needs the private API key.

EU domains on the US API host fail Connect.