Feature Requests
If you’ve got a feature request, you’ve come to the right place! Please relay your request request here, along with any additional details you think might be helpful.
This is not the spot for feedback on current features, only new plausible ideas will be considered. Please be courteous of others and upvote if you believe strongly enough in an idea!
106 results found
-
Manage multiple accounts with the same email
There is a way to create multiple logins for the same Mailgun account but we can't reuse an existing account. The error message is:
Error: Unable to invite user. User already exists
We need a way to manage multiple accounts under the same email, not having this is a total nightmare :\ We have this in Stripe, Twilio, SendGrid, Mailchimp, etc ...
There is no way I will ask my clients to forward me the "passcode" everytime I need to login on my client's account.
117 votes -
Invite new users/roles to specific domain(s)
Recently you introduced invitation of new users and assigning them roles.
In addition to "roles" i would like to see that these invitations/roles can also be limited to specific domains.136 votes -
Support Non-credit card payment types
Allow customers to pay via alternative payment types other than credit card.
100 votes -
Add support for idempotent requests to the API
Add Idempotency-Key to request ala Stripe's API. https://stripe.com/docs/api?lang=curl#idempotent_requests
41 votes -
Alert and Notify based on Sending Metrics and Usage
There are some delivery issues which usually warrant manual inspection and care by the administrative users. I feel that continuing to send emails to addresses that have ended up in the Bounces list would at least be one of them.
It would be convenient if the user could select certain common delivery issues like this and get a notification about them emailed to a specified email address. This email address could then be a mailing list for administrative personel who could look in to the error and see it they should act upon it.
It is possible to implement this…
35 votesHello,
As we work through ideation on an alerts feature for Mailgun, I wanted to gauge opinion on the configuration of notification channels. If out of the box, Mailgun allows for configuration of notification channels to include emails addresses, webhooks, and Slack integration where in the flow does it make most sense where the channels are defined.
Our position is that the pattern for notification channels is created on the account level. Such that any all alerts created would use the notification channels previously defined. This would be foundational to a future state is which users could have greater control on how Mailgun communicates emergent issues (e.g. some users would like to receive domain disablement or similar notification posted to webhook rather than email).
So, for "alert and notify based on sending metrics and usage" is there any reason Mailgun needs to have notification channels defined on a per alert…
-
Shorten Tracking URLs
The current URLs used for tracking link clicks are quite long. Offering a way to shorten them via Bit.ly or perhaps an custom shortened URL would be helpful.
14 votes
- Don't see your idea?