Connect Mailgun to PostgreSQL
Send Mailgun domains and events to PostgreSQL on a schedule. Filter by date. Refresh as often as every 15 minutes.
PostgreSQL
schema mailgun
domainsevents
How to connect Mailgun and PostgreSQL
5 steps. You can preview the Mailgun data in Coupler.io before anything reaches PostgreSQL.
Step 1 of 5
Connect Mailgun
Enter your Mailgun private API key and domain region code. You only do this once per account.
Step 2 of 5
Choose what to export
Pick the Mailgun data you want in PostgreSQL.
Step 3 of 5
Fine-tune the export
Optional settings for this Mailgun export.
Step 4 of 5
Connect PostgreSQL
Enter your PostgreSQL connection details, then the schema and table for the Mailgun data.
Show 3 more fields Show fewer fields
Step 5 of 5
Choose a write mode and schedule
Every run either replaces or appends the data in PostgreSQL. Run it as often as every 15 minutes.
Each run deletes the existing rows in domains and loads fresh Mailgun data.
Coupler.io made it easy to create dashboards and reports from different data sources. The sync is reliable and the user experience is amazing.
Take your data analytics to the next level
Sign Up with Google
Sign Up with MICROSOFT
SIGN UP WITH EMAIL
By signing up to Coupler.io, you agree to our Privacy Policy and Terms of Use.
Build your Mailgun integrations with these destinations
Get the most of Mailgun to PostgreSQL integration
Gather data
Understand data
Automate data
Act on data
2 data types, including Domains and Events.
With your Mailgun private API key and domain region code, entered once when you add the connection.
Yes. Set the start date to cover the period you need.
Yes, if the database user has CREATE privileges. Coupler.io creates the mailgun schema and the domains table on the first run.
Yes. Append adds new rows to domains on each run, while Replace swaps in a fresh copy. With Append, add new Mailgun columns to the table yourself before the next run.
On a schedule you choose, from monthly down to every 15 minutes, depending on your Coupler.io plan.
Yes. Add more sources to the same data flow, for example Calendly or Klaviyo, and join or append them before the data reaches PostgreSQL.
