Built for agencies and B2B sales teams.

Start free →

Connect Google Workspace to DevBoxy.

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.

Explicit authorizationSend-only Gmail accessRevoke access anytime
Send-only accessNo inbox reading
Core capabilities

Everything you need to send from Google Workspace with confidence

A focused set of tools that fit into the wider DevBoxy outreach platform, built around permissions you can see and control.

Explicit authorization

Google shows the Gmail sending permission before you approve the connection, so you always know what you are granting.

Send-only Gmail access

The gmail.send permission allows sending on your behalf. It does not let DevBoxy read, list or delete inbox messages.

Account visibility

Review connection and readiness information for each Google account from your DevBoxy workspace.

Connection control

Remove the sender connection from DevBoxy, or revoke access from your Google Account. Either one ends sending.

What the permission allows

The gmail.send permission does not grant access to your Gmail inbox

DevBoxy asks for the narrowest permission it needs to send your campaign emails. Here is exactly what that means.

With gmail.send, DevBoxy can

  • Send the messages you configure through the Gmail API
  • Send from a Google account that your organization controls
  • Show you the account’s connection and readiness status

With gmail.send, DevBoxy cannot

  • Read your Gmail inbox
  • List the messages in your inbox
  • Delete inbox messages

Replies use a separate, supported connection

Because sending authorization does not include inbox access, reply tracking is configured separately. Processed replies appear in the unified inbox.

How to connect

How to connect a Google Workspace account to DevBoxy

Connecting takes a few steps, and you approve the permission yourself on Google’s consent screen.

  1. 01

    Start the connection

    Choose Google Workspace when you add a sending account in DevBoxy.

  2. 02

    Review the permission

    Google shows the Gmail sending permission before you approve.

  3. 03

    Approve the connection

    Sign in with the Google account you control and allow sending.

  4. 04

    Check readiness

    Review the account’s status in your workspace, then assign it to campaigns.

Connection control

You stay in control of the connection

A connection should be easy to inspect and easy to end. DevBoxy gives you two independent ways to remove access.

  • Remove it in DevBoxy. Delete the sender connection from your workspace whenever you no longer need it.
  • Revoke it in Google. Withdraw DevBoxy’s access from your Google Account settings at any time.
  • See what is connected. Connection and readiness information stays visible in your workspace.
Manage all sending accounts
Deliverability

Authenticate your Google Workspace domain before you send

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.

  • SPF. Authorise Google’s mail servers for your domain.
  • DKIM. Sign your messages so receivers can verify them.
  • DMARC. Tell receivers what to do when authentication fails.
SPF, DKIM, DMARC pass
Best practices

Best practices for sending cold email from Google Workspace

A few habits keep Google accounts healthy and your outreach on the right side of provider limits.

Use dedicated sending domains

Many teams send outreach from separate domains or subdomains, to keep the main brand domain protected.

Spread volume across accounts

Several accounts sending a little each look more natural than one account sending a lot.

Verify before you send

Bounces damage reputation quickly. Verify contacts before they enter a sequence.

FAQ

Google Workspace integration FAQ

Still unsure? Read the DevBoxy blog or contact the team.

How does DevBoxy connect to Google Workspace?

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.

What does the gmail.send permission allow?

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.

Can DevBoxy read my Gmail 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.

How do I disconnect my Google account?

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.

Which Google accounts can I connect?

You can connect Google Workspace accounts that your organization controls. DevBoxy also supports Gmail accounts you control. See Email Accounts for all supported providers.

Can I see the status of a connected account?

Yes. You can review connection and readiness information for each Google account from your DevBoxy workspace before assigning it to a campaign.

How are replies handled if DevBoxy cannot read my inbox?

Replies are tracked through supported reply-processing connections that you configure separately from sending. Processed replies appear in the unified inbox.

Do I need to set up SPF, DKIM and DMARC?

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.

Build a stronger outreach workflow with DevBoxy.

Start with the tools you need today, then connect more infrastructure, campaigns and conversations over time.