Hirevire
Uncategorized

Connect Google to Send Outgoing Emails

Updated 2 months ago

Hirevire can send candidate emails through your connected Google account, ensuring messages come from your own email address. This requires granting Google permission to send email on your behalf during the connection flow.

How to Connect Your Google Account

  1. Go to Settings > Email settings in your organization

  2. Click Connect Google account

  3. On Google's consent screen, review the permissions

  4. Make sure "Send email on your behalf" is checked — this is the critical permission Hirevire needs

  5. Click Allow to complete the connection

Important: Google frequently shows the "Send email on your behalf" checkbox unchecked by default. If this permission is not granted, outgoing emails will fail with an "insufficient authentication scopes" error.

Fixing Missing Email Permissions

If your Google account was connected without the send permission, emails will not be delivered. You'll see errors like "insufficient authentication scopes" in the email logs.

To fix this:

  1. Go to Settings > Email settings

  2. Click Connect Google account to reconnect

  3. On Google's consent screen, ensure "Send email on your behalf" is checked

  4. Click Allow to save the updated permissions

After reconnecting with the correct permission, emails should send immediately.

Check Email Delivery in Logs

If emails aren't arriving, check the logs to diagnose the issue:

  1. Go to Logs > Email

  2. Filter by job or organization to find relevant emails

  3. Look for error messages that explain why delivery failed

Common errors include:

  • "insufficient authentication scopes" — Google send permission was not granted; reconnect with the checkbox checked

  • Authentication failed — The connection may have expired or been revoked; reconnect your account

Google vs SMTP

Hirevire supports both Google OAuth and SMTP for outgoing email. Google OAuth is simpler to set up and avoids managing SMTP credentials. If you previously configured SMTP but now see Google-related errors, your account may have been connected via Google OAuth at some point.

Both methods work independently — use whichever fits your workflow.

Was this helpful?
Was this helpful?