Weekly Mailgun email stats in Google Sheets
Add one row of last week's Mailgun numbers to your sheet every Monday: sent, delivered, unique opens and clicks, hard bounces, complaints, unsubscribes.
Letaido's Mailgun integrations let an AI agent report on delivery, flag bounces in HubSpot, alert Slack and send emails from your templates.
Delivery reports, bounce alerts and template updates. Open one to watch it run.
Add one row of last week's Mailgun numbers to your sheet every Monday: sent, delivered, unique opens and clicks, hard bounces, complaints, unsubscribes.
Check yesterday's Mailgun hard bounce and complaint rates each morning, and post to Slack with a provider breakdown only when one runs high.
When a Mailgun email hard bounces, draws a spam complaint or someone unsubscribes, the agent marks the HubSpot contact and adds a dated note.
When a Stripe payment fails, the agent sends the customer your Mailgun template with the amount due and your billing login link.
Ask about one address and the agent reads its recent Mailgun events and suppression lists, then tells you what happened and when.
Paste new copy and the agent saves it as a new version of your Mailgun template, keeps the live one active, and sends you a test.
Five ways to connect Mailgun to the rest of your work.
| Option | Set up by asking | Works across your apps | Runs on its own | No code | Connects thousands of apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Mailgun's own integrations | No | Partly | Yes | Partly | No |
| Zapier, Make and similar | Yes | Yes | Yes | Yes | Yes |
| Mailgun API, SDKs and webhooks | No | Partly | Partly | No | Partly |
| Mailgun MCP server | Yes | Partly | No | Partly | No |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent reads delivery numbers and events, checks suppression lists, saves template versions and sends from your domains. It runs on a Mailgun event, a schedule, another app's event or when you ask. | Email work that crosses apps: weekly reports in Sheets, bounce alerts in Slack, bounces on HubSpot contacts, failed payment emails. | A focused catalog, not thousands of apps. Mailgun keeps 1 to 30 days of events, depending on your plan. |
| Mailgun's own integrations | Set connections listed in Mailgun's docs, such as Slack deliverability alerts, Datadog and Splunk monitoring, WordPress, Supabase and Heroku. | Sending from a website or app, and watching deliverability in a monitoring tool. | Each one does a set job between Mailgun and that tool. Setup varies: the Supabase one runs through Edge Functions you code, and Heroku adds email to apps you deploy. |
| Zapier, Make and similar | Triggers for bounces, deliveries, opens and clicks, complaints and unsubscribes start workflows the moment they happen. Actions send an email, add a mailing list member or validate an address. Zapier Copilot builds a workflow with you. | Fixed handoffs, like a form entry that sends a Mailgun email. | Check what Copilot sets up. New Log Data and New List are checked every 15 minutes on Zapier's entry plan. |
| Mailgun API, SDKs and webhooks | A REST API and SMTP relay with SDKs for Python, Node.js, PHP, Java, Ruby and Go, plus webhooks for delivery, open, click, bounce, complaint and unsubscribe events. | Sending from your own product, with exact control. | Needs developers. An account API key has full access to the account. |
| Mailgun MCP server | You run it on your own computer with your API key, in Claude Desktop, Claude Code, Cursor, VS Code or another MCP client. It sends email, reads stats and manages domains, templates and suppressions in a chat. | Developers who want Mailgun answers and changes inside their AI tool. | Runs only when you chat. Mailgun has no hosted version, and it has no delete tools. |
Connect Mailgun once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
Save it to run on a schedule or an app event.
A Mailgun or Stripe event, a schedule or you asking starts the job.
In Mailgun, open Account Settings, then API keys, and create a key. Copy it, since Mailgun shows it once. Use an account key (Admin role if your plan has roles), not a domain sending key, which can only send.
Pick your account's region, US or EU, so the agent reaches the right Mailgun servers. One key covers every domain in the account.
Say which sending domain, template, list or sheet the job is for. Mailgun has no default domain.
Allow all read operations once per app; approve each kind of write once. Then save it to repeat.
249 actions in 12 groups, from sending and events to templates and IP pools.
In Mailgun, open Account Settings, then API keys, create a key and paste it into Letaido with your region, US or EU. Use an account key (Admin role if your plan has roles), not a domain sending key, which can only send.
Yes. A job can start when an email is accepted, delivered, opened, clicked, fails, draws a spam complaint or someone unsubscribes, on any of your domains. Letaido creates the Mailgun webhook for you, and Mailgun can take up to 10 minutes to start sending to it. Opens and clicks need tracking on for the domain.
Yes. You run it on your own computer with your API key, in Claude Desktop, Claude Code, Cursor, VS Code or another MCP client, and it works while you chat. Letaido is not an MCP server: it has its own Mailgun connector and runs whole jobs on a Mailgun event, a schedule or when you ask.
Yes. Zapier runs a workflow you build from fixed triggers and actions, like sending an email or adding a list member. With Letaido you describe the job and the agent reads Mailgun's numbers, events and lists, then acts in your other apps, like a daily bounce alert in Slack.
Only when a job asks for it. Of the jobs above, only the failed payment job emails customers, and the template job sends a test to you.
As far as your plan keeps events and logs, 1 to 30 days. The missing email job says how far back the data it found goes.
Allow all read operations once per app; approve each kind of write once.
Connect Mailgun, then ask for a job like "Log last week's Mailgun email stats in our Google Sheet every Monday". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoSend an email or a pre-built MIME message from one of your Mailgun domains, resend a stored message, read a stored email and delete scheduled mail.
Read each message's events (delivered, failed, opened, clicked and more), query logs, account and usage metrics and bounce classification, and read or edit tags.
List, look up, add, import, remove and clear the bounce, unsubscribe and spam complaint lists of a domain, and manage its allowlist.
Create, update and delete mailing lists, and add, import, update and remove their members.
Create, copy, rename, update and delete email templates and their versions, per domain or for the whole account.
Add, verify, update and delete sending domains, manage DKIM keys and tracking certificates, and turn open, click and unsubscribe tracking on or off.
List, create, update and delete domain and account webhooks, and read or regenerate the webhook signing key.
Create, update, test and delete routes for incoming mail, and manage forward rules.
Set up send alerts and alert channels (email, Slack, webhook), and read or set sending limits and thresholds.
Read and assign dedicated IPs, manage IP pools, dynamic pools, spillover and IP warmup (plans with dedicated IPs).
Create, enable, disable and delete subaccounts, set their features, IPs, delegated IP pools and sending limits (plans with subaccounts).
Read the account's users, manage API keys, SMTP credentials and the IP allowlist, update account settings, and call any Mailgun API path when no other action fits.