Mailgun integration
The Mailgun integration lets InboxEagle receive email events (opens, clicks, bounces, complaints) from your Mailgun account, pass them through the Bot Finder pipeline for bot classification, and surface clean engagement signals in your InboxEagle dashboard.
Prerequisites
Section titled “Prerequisites”- An active InboxEagle account (Basic or Agency plan required for Bot Finder)
- A Mailgun account with a sending domain configured and verified
- Mailgun API key or access to the Mailgun Control Panel to configure webhooks
How the integration works
Section titled “How the integration works”Mailgun sends event data to InboxEagle via webhook on every email event. InboxEagle’s Bot Finder pipeline:
- Receives the Mailgun webhook payload
- Verifies the HMAC-SHA256 signature (Mailgun’s webhook authentication) with a 5-minute replay window
- Normalizes the event into a unified schema alongside SES and Klaviyo events
- Analyzes the event using the same 6-layer bot detection pipeline as the SES integration
- Delivers the classified result to your configured delivery method (webhook, SNS, or S3)
Setup steps
Section titled “Setup steps”-
Open the Mailgun integration
In the InboxEagle app, go to Integrations → Mailgun (or navigate via the Integrations hub at app.inboxeagle.com/integrations).
-
Get your InboxEagle Mailgun webhook URL
Click Generate webhook URL. InboxEagle generates a unique endpoint URL for your account. Copy this URL — you will register it in Mailgun.
-
Register the webhook in Mailgun
In your Mailgun Control Panel:
- Go to Sending → Webhooks
- Select your sending domain from the dropdown
- Click Add webhook
- Choose the event types to send: Opens, Clicks, Bounces, Spam Complaints, Unsubscribes, Failures
- Paste the InboxEagle webhook URL into the URL field
- Click Create webhook
-
Verify the connection
In InboxEagle, the Mailgun integration page shows a Connection status indicator. After Mailgun sends the first test event, it updates to Active.
If the status remains Pending, use Mailgun’s Test webhook feature (available in the webhook settings) to send a test event manually.
-
Send a test email
Send a test email through your Mailgun-configured sending domain. After a few minutes, bot-classified events should appear in the InboxEagle Bot Finder dashboard.
Supported Mailgun event types
Section titled “Supported Mailgun event types”| Mailgun event | InboxEagle classification |
|---|---|
opened | Analyzed for bot activity; classified as bot, suspicious, or human |
clicked | Analyzed for bot activity; classified as bot, suspicious, or human |
delivered | Logged; not analyzed for bots |
bounced | Logged; contributes to bounce rate metrics |
complained | Logged; contributes to spam complaint metrics |
unsubscribed | Logged; contributes to unsubscribe rate metrics |
failed | Logged as a delivery error |
Webhook security
Section titled “Webhook security”InboxEagle verifies every incoming Mailgun webhook using HMAC-SHA256 signature verification. Mailgun includes a timestamp and signature in each webhook payload; InboxEagle validates both:
- Timestamp validation — Events older than 5 minutes are rejected (replay protection)
- Signature validation — The HMAC signature is verified against your Mailgun webhook signing key
You do not need to configure this manually — InboxEagle retrieves the signing key during the integration setup flow.
Viewing Mailgun data in InboxEagle
Section titled “Viewing Mailgun data in InboxEagle”After the integration is active:
- Bot Finder dashboard — Opens and clicks from Mailgun appear alongside SES events. Filter by provider to see Mailgun-only data.
- Intelligence Agent — Query Mailgun bot rates in natural language (e.g. “What is my bot rate via Mailgun this month?”)
- Deliverability dashboard — If you send from domains tracked in InboxEagle, domain-level placement data is updated when Mailgun campaigns are detected.
Troubleshooting
Section titled “Troubleshooting”Webhook shows “Error” status
Section titled “Webhook shows “Error” status”- In Mailgun, go to Sending → Webhooks and check the delivery log for your InboxEagle webhook. HTTP errors are shown per event.
- Common causes:
- 401 — Signing key has changed; reconnect the integration
- 404 — Webhook URL has been regenerated; update the URL in Mailgun
- Timeout — Transient; Mailgun will retry automatically
Events arriving but not appearing in dashboard
Section titled “Events arriving but not appearing in dashboard”- Confirm the events are reaching InboxEagle by checking the connection status indicator
- Events are processed asynchronously — allow 1–2 minutes for events to appear in the Bot Finder dashboard
- If events still do not appear after 5 minutes, trigger a manual refresh in the dashboard
HMAC verification failing
Section titled “HMAC verification failing”- This usually means your Mailgun webhook signing key was rotated after setup
- Go to Integrations → Mailgun and click Reconnect to refresh the signing key
- Re-register the webhook URL in Mailgun if it changes during reconnection
Disconnecting Mailgun
Section titled “Disconnecting Mailgun”To disconnect the Mailgun integration:
- Go to Integrations → Mailgun in the InboxEagle app
- Click Disconnect
- Remove the InboxEagle webhook URL from your Mailgun webhook settings (optional, but prevents unnecessary webhook delivery attempts)
After disconnecting, InboxEagle stops receiving and processing Mailgun events. Historical data remains in your account.
Next steps
Section titled “Next steps”- Bot Finder dashboard — Monitor bot detection results including Mailgun events
- Bot Finder advanced configuration — Customize bot thresholds and detection rules
- AWS SES integration — Add SES as a complementary event source
- Intelligence Agent — Query cross-provider bot rates in natural language