Google Gmail setup in Regal Send

Updated September 24, 2026

Google Gmail setup in Regal Send#

Use the guided Google Gmail setup in Regal Send to connect one Gmail or Google Workspace account for WordPress email. The connection uses Google OAuth and requests only the Gmail gmail.send permission. You will need access to a Google Cloud project and the account that will send your site’s mail.

Before you begin#

  • Use a publicly reachable WordPress site with HTTPS.
  • Have permission to configure a Google Cloud project and its OAuth app.
  • Know which Google account will send email from WordPress.

Google does not accept a raw IP address as the host of a standard Web OAuth redirect URI. If your WordPress site uses a local IP address or a non-public test hostname, use a publicly reachable HTTPS domain for the Google connection.

Create the Google Cloud project and enable Gmail API#

  1. Open the Gmail API page in Google Cloud. Select an existing project or create one, then enable Gmail API for that project.
  2. Open Google Auth Platform Branding and set the app name and support email.
  3. Open Audience and choose the audience suitable for your account. For an External app in Testing, add the Google account you will connect as a test user.
  4. Open Data Access and add only https://www.googleapis.com/auth/gmail.send. This scope allows Regal Send to send mail on the connected account’s behalf; Regal Send does not request permission to read your mailbox.

Google classifies gmail.send as a sensitive scope. Google’s publishing and OAuth verification requirements may apply when the app is used beyond test accounts. While an External app remains in Testing, authorisations for this Gmail permission expire after seven days, including refresh tokens. Reconnect when that happens or complete the relevant Google publishing and verification steps.

Create a Google Web OAuth client#

  1. Open Google Auth Platform Clients and choose to create an OAuth client.
  2. Select Web application as the application type.
  3. In Authorised redirect URIs, paste the exact redirect URI shown by the Regal Send wizard. Do not add a trailing slash or change any part of it.
  4. Create the client. Copy the Client ID and the full client secret. Google shows the full secret when it is created; store it securely. If you lose it, create or rotate a secret rather than trying to retrieve the old value.

See Google’s OAuth client instructions for the current console details.

Connect Gmail in WordPress#

  1. In WordPress, open Regal Send > Setup Guides or Regal Send > Integrations, then choose Open guided Google setup.
  2. Copy the wizard’s exact redirect URI into Google Cloud before continuing.
  3. Enter the OAuth Client ID and client secret. Set From Email to the account you will authorise, or an email alias configured and verified in Gmail.
  4. Save the Google details. Regal Send encrypts the saved client secret. A blank secret field keeps the saved value; it does not remove it.
  5. Select Connect Google, sign in to the sending account and approve the requested Gmail send permission.
  6. When Regal Send shows Connected, open the test-email step, enter a recipient address and send a test.

A Sent test means Google accepted the message for delivery. It does not confirm that the message reached the recipient’s inbox.

Fix common Google connection errors#

Redirect URI mismatch#

Copy the redirect URI again from the wizard and compare it character by character with the Web OAuth client’s authorised redirect URI. Confirm the WordPress site is using its public HTTPS domain.

Access denied or the account cannot authorise#

Check that the Google account is included as a test user when the app audience is External and its publishing status is Testing. Workspace administrators can also restrict access to Gmail scopes.

Invalid client#

Confirm that the Client ID belongs to this Google Cloud project and Web OAuth client. If the secret was lost or rotated, replace the saved secret in Regal Send and save again.

Authorisation expires after seven days#

This is expected for an External app left in Testing while requesting the Gmail send permission. Reconnect the account, or review Google’s publishing and verification requirements for production use.

Google accepts the account but rejects the From address#

Use the connected Google account as From Email, or verify the address as an allowed sending alias in Gmail. Then send another test email.

Was this article helpful?

Still need help? Contact support