How to Use Gmail SMTP Server for Sending Email easy steps


This step-by-step guide demonstrates how you may connect to the Gmail SMTP server for sending emails from a Node.js web application that might be installed on Google Cloud Functions, AWS Lambda, Cloud Run or running on your local desktop.

And unlike most other Node SMTP tutorials that utilise the username and password combination, this solution uses OAuth and doesn’t require you to turn on less protected applications access in your Google account.

Create Gmail OAuth Credentials

Create a new Google Cloud Project and enable the Gmail API as described in a previous tutorial.

Gmail SMTP OAuth Application

In the APIs & Services section, click on Credentials and click on Create credentials > OAuth Client Id to create a new client ID that will be used to identify your application to Google’s OAuth servers.

Set the application type as Web Application and put the following URL in the Authorized Redirect URI.


Click the Create button and you’ll be provided the OAuth Client ID and Client Secret values that you’ll need in the next step.

Create Gmail Refresh Token

Gmail Access Refresh Token

Next, we’ll produce a refresh token using the Google Developer OAuth 2.0 playground. The access tokens are good for an hour but the refresh tokens are valid indefinitely (until manually cancelled) and may be used to produce a fresh access token.


Go to, select the Gear Icon and tick the option that states Use your own OAuth credentials. Copy-paste the Client ID and Client Secret that you have generated in the previous step.

Inside the Select & Authorize APIs section, enter the scope and click the Authorize APIs button to generate the permission code.

Click the Exchange authorization code for tokens to produce the refresh token that we’ll want in the following step.

Refresh Token

Prepare the Node.js Application

Create a new folder and install the googleapis and nodemailer packages.

mkdir gmail-smtp-sender
cd gmail-smtp-sender
npm init --y
npm install dotenv googleapis nodemailer --save
touch index.js

Create a new .env file in the root folder and add the credentials in the file. Add the file to .gitignore so it is not added to the repository.

// Replace these with your own credentials
REFRESH_TOKEN = '1//04yt8hEatvIr3uyk-ZJSYIhmYqMk4C4EqfPK24w'

Open the index.js file and add the following code. You may need to replace the sender’s email with the email address of your own Gmail account that you have authorized to send email.

The Gmail SMTP server name is and the Gmail SMTP port is 465. You can send up to 100 emails per day when the messages sent via SMTP.

const { google } = require('googleapis');
const nodemailer = require('nodemailer');

const sendEmail = async () => {
  const oauth2Client = new google.auth.OAuth2(
  oauth2Client.setCredentials({ refresh_token: process.env.REFRESH_TOKEN });

  const accessToken = await oauth2Client.getAccessToken();
  const myEmail = '[email protected]';

  const smtpTransport = nodemailer.createTransport({
    service: 'gmail',
    host: '',
    port: 465,
    secure: true,
    auth: {
      type: 'OAuth2',
      user: myEmail,
      clientId: process.env.CLIENT_ID,
      clientSecret: process.env.CLIENT_SECRET,
      refreshToken: process.env.REFRESH_TOKEN,

  const mailOptions = {
    from: 'Sender Name <[email protected]>',
    to: 'Receiver Name <[email protected]>',
    subject: 'Test email 🚀',
    text: 'This is a test email from Node.js 🎉',
    html: 'This is a <b>test email</b> from Node.js 🎉',

  try {
    const response = await smtpTransport.sendMail(mailOptions);
    console.log(`Email sent!`, response);
  } catch (f) {
  } finally {

sendEmail().then(() => console.log('Done!'));

Here’s a test email sent by the application. If the email receiver client doesn’t support HTML mail, the plain text version is rendered.


Correct Gmail OAuth Scope

While you can send emails from Gmail using the scope, you would need to use the restricted scope for Gmail SMTP. If your OAuth client uses a different scope when requesting permissions for an user, the application will return the 535-5.7.8 Username and Password not accepted error.

Leave a Comment