Email and messaging
Mailgun consultant: email your systems can read as well as send.
SBD builds Mailgun setups that receive email, pass it to AI and business systems, and send authenticated transactional messages, for teams of 5 to 1,000 people. Workflow automation builds start at $1,500, with the fixed price set after a $500 Automation Audit that is credited to the build.
- Tool
- mailgun.com
- Usually paired with
- Retool, OpenAI, Cloudflare, n8n
- Timeline
- Most builds live in 3 to 5 business days from scope
- Owned by
- You, with accounts, credentials and code in your name.
What we build on Mailgun
- Receive inbound email and pass it to an AI or parsing step
- Send transactional email with domain authentication
- Track delivery and handle bounces by webhook
- Keep attachments linked to the right record
What we sync
Workflows we are asked for
- Mailgun inbound email to an AI extraction step
- Mailgun RFQ emails routed into an internal tool
- Mailgun delivery events into a database
- Mailgun transactional email from Retool
Documented in depth
Full write-ups of Mailgun integrations.
Often paired with
Tools Mailgun usually needs to talk to.
-
Mailgun and Retool
Internal tools built fast on top of your database and APIs, with roles.
-
Mailgun and OpenAI
GPT models through the business API for extraction, classification and drafting.
-
Mailgun and Cloudflare
DNS, edge functions, storage and security in front of your apps.
-
Mailgun and n8n
The automation platform we build most systems on: code where needed, visual where not, cloud or self-hosted.
What we build
What a Mailgun expert from SBD builds
Many business processes still start with an email: a request for quotation, a purchase order, a supplier invoice. Mailgun can receive that email at an address you control and hand it to your systems as data, so nobody has to retype it.
Our published example is an enquiry platform for an industrial distributor, which reads emailed RFQs with AI and matches parts against the SAP item master. Mailgun, Retool, OpenAI and Cloudflare are in that stack.
- Inbound addresses that turn each email and attachment into a record.
- AI extraction with a person checking anything uncertain.
- Transactional email from apps, with domain authentication set up first.
- Delivery and bounce events written back so the app shows what happened.
Fit
When Mailgun is the right choice, and when it is not
Mailgun suits systems where receiving and parsing email matters as much as sending it. If an app only sends notifications, a simpler service such as Resend may be enough.
Inbound email needs careful handling. Anyone can write to the address, so we check senders, cope with duplicates and forwarded threads, and keep the original message so a person can see what the AI read.
- You only send a few notifications from one app; a simpler service costs less attention.
- Your team needs to read and answer the email; a shared inbox or helpdesk fits better.
- You want cold outreach; use a tool built for it, and keep it away from your transactional domain.
Plans and limits
Mailgun plans and sending volume
Mailgun prices by monthly email volume, and features such as inbound routing and log retention vary by plan. Check the current figures on its pricing page. During the audit we estimate your sending and receiving volume so the plan is chosen against real numbers.
Engagement and cost
How hiring a Mailgun consultant from SBD works
Every engagement starts with an Automation Audit at $500, credited in full to your build. For Mailgun we collect a sample of real emails, check how much of each can be read reliably, review your domain setup and estimate monthly volume.
Workflow automation builds start at $1,500, and the fixed price is set after the audit and agreed before work begins. Your Mailgun subscription is paid by you to Mailgun. We do not resell licences.
Handover
What you own, and what happens when an email cannot be read
The Mailgun account, the domains and every connected system stay in your name. You receive a runbook covering each address and route, what happens to each message, and how to replay one.
Emails that fail or look uncertain go to a review queue with a named owner, and nothing is dropped silently.
In every build
Standards we apply to every build.
Under the hood
- Upserts keyed on the record
Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.
For the team
- Slack or email notifications
Alerts go to a named person on your team, by Slack, email or WhatsApp.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
Keys and data
- Keys are kept in a vault
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts for connections
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
The offer
Connect Mailgun to the rest of your stack.
We agree a fixed scope in a discovery call, and most builds go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.
- ScopeOne call to agree the workflows, the fields and the owner, written up the same day.
- BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
- Go-liveWe test in a sandbox first, then switch over. It takes longer only where a vendor has to approve something.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about Mailgun.
Mailgun or Resend?
Mailgun is a good fit when inbound email parsing matters. Resend is simple for apps that mostly send. Both need domain authentication set up properly.
Mailgun
Start with the one Mailgun workflow your team still runs by hand.
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call