If your business email runs on Google Workspace, the integration is intentionally light — you don't connect a Gmail mailbox to us. Gmail and Google Workspace are not built for high-volume outbound automation (and trying to do it that way leads to deliverability problems and rate limits).
Instead, we send automated email through your own authenticated domain using Mailgun. Your team keeps Gmail exactly as it is for human replies and personal sends, and replies to automated emails route back through Mailgun so our system can see them and stop the follow-up sequence.
Popular workflow recipes
When this happens → do thatTriggers & Actions
3 triggers · 3 actionsBoth Gmail and our unified inbox see it; AI sequences halt.
Tracked via Mailgun + suppress contact from future sends.
Standard mailgun-side handling.
Routes through Mailgun-authenticated sending subdomain.
Human team keeps using Gmail for one-to-one replies; both flows coexist.
Replies land in both places so AI sequences pause when a teammate jumps in.
How to connect Gmail / Google Workspace
~10 minutes- Direct Gmail / Google Workspace mailbox API access is not used because Google's per-account quotas and abuse-prevention systems are not designed for marketing- or automation-style outbound volume.