Explicit authorization
Google shows the Gmail sending permission before you approve the connection, so you always know what you are granting.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Authorize a Google account you control so DevBoxy can send the messages you configure through the Gmail API. The permission is send-only, and you can remove it at any time.
A focused set of tools that fit into the wider DevBoxy outreach platform, built around permissions you can see and control.
Google shows the Gmail sending permission before you approve the connection, so you always know what you are granting.
The gmail.send permission allows sending on your behalf. It does not let DevBoxy read, list or delete inbox messages.
Review connection and readiness information for each Google account from your DevBoxy workspace.
Remove the sender connection from DevBoxy, or revoke access from your Google Account. Either one ends sending.
DevBoxy asks for the narrowest permission it needs to send your campaign emails. Here is exactly what that means.
Because sending authorization does not include inbox access, reply tracking is configured separately. Processed replies appear in the unified inbox.
Connecting takes a few steps, and you approve the permission yourself on Google’s consent screen.
Choose Google Workspace when you add a sending account in DevBoxy.
Google shows the Gmail sending permission before you approve.
Sign in with the Google account you control and allow sending.
Review the account’s status in your workspace, then assign it to campaigns.
A connection should be easy to inspect and easy to end. DevBoxy gives you two independent ways to remove access.
Connecting an account lets DevBoxy send, but your domain’s DNS decides how receivers treat the mail. Check SPF, DKIM and DMARC before an account joins a live campaign.
| Type | Host | Value | Status |
|---|---|---|---|
| TXT | @ | v=spf1 include:_spf.google.com ~all | Pass |
| TXT | google._domainkey | v=DKIM1; k=rsa; p=MIIBIjAN… | Pass |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:… | Pass |
A few habits keep Google accounts healthy and your outreach on the right side of provider limits.
Many teams send outreach from separate domains or subdomains, to keep the main brand domain protected.
Several accounts sending a little each look more natural than one account sending a lot.
Bounces damage reputation quickly. Verify contacts before they enter a sequence.
Once an account is connected, build on it.
You authorize a Google account that you control, and DevBoxy then sends the messages you configure through the Gmail API. Google shows the Gmail sending permission before you approve the connection.
The gmail.send permission allows DevBoxy to send messages on your behalf. It does not let DevBoxy read, list or delete messages in your inbox.
No. The gmail.send permission does not grant DevBoxy access to read your Gmail inbox. Reply tracking uses a separate, supported connection that you configure on its own.
You can remove the sender connection from your DevBoxy workspace, or revoke access from your Google Account settings. Either one ends DevBoxy’s ability to send from that account.
You can connect Google Workspace accounts that your organization controls. DevBoxy also supports Gmail accounts you control. See Email Accounts for all supported providers.
Yes. You can review connection and readiness information for each Google account from your DevBoxy workspace before assigning it to a campaign.
Replies are tracked through supported reply-processing connections that you configure separately from sending. Processed replies appear in the unified inbox.
It is strongly recommended. Authentication records help receivers trust your mail. You can test them with the free network tools before you launch a campaign.
Start with the tools you need today, then connect more infrastructure, campaigns and conversations over time.