Building an Azure Queue Trigger Function for Sending Emails with Nodemailer

{
  "IsEncrypted": false,
  "Values": {
    "AzureWebJobsStorage": "YOUR_STORAGE_CONNECTION_STRING",
    "QUEUE_NAME": "mail-trigger",
    "ACCOUNT_NAME": "YOUR_STORAGE_ACCOUNT_NAME",
    "ACCOUNT_KEY": "YOUR_STORAGE_ACCOUNT_KEY",
    "FUNCTIONS_WORKER_RUNTIME": "node"
  }
}

{
  "version": "2.0",
  "logging": {
    "applicationInsights": {
      "samplingSettings": {
        "isEnabled": true,
        "excludedTypes": "Request"
      }
    }
  },
  "extensionBundle": {
    "id": "Microsoft.Azure.Functions.ExtensionBundle",
    "version": "[3.*, 4.0.0)"
  },
  "concurrency": {
    "dynamicConcurrencyEnabled": true,
    "snapshotPersistenceEnabled": true
  }
}

• Version: Indicates the version of the Azure Functions runtime. In this case, it's version "2.0."
• logging: Configures logging settings for the Azure Functions application.
• applicationInsights: Configures Application Insights integration for logging and monitoring.
• samplingSettings: Specifies settings for log sampling.
• isEnabled: Enables or disables log sampling. If true, log sampling is enabled.
• excludedTypes: Specifies log types to exclude from sampling. In this case, "Request" logs are excluded.
• extensionBundle: Configures the Azure Functions extension bundle.
• id: Specifies the ID of the extension bundle.
• version: Specifies the version range of the extension bundle to use. In this case, it's set to a range from version 3.x to version 4.0.0.
• concurrency: Configures concurrency settings for the Azure Functions application.
• dynamicConcurrencyEnabled: Enables or disables dynamic concurrency, allowing the system to adjust concurrency levels based on demand.
• snapshotPersistenceEnabled: Enables or disables snapshot persistence, which helps maintain the state between function executions.

Step 5. Configure function.json: Update the function.json file to specify the queue trigger binding.

{
  "bindings": [
    {
      "name": "myQueueItem",
      "type": "queueTrigger",
      "direction": "in",
      "queueName": "mail-trigger",
      "connection": "AzureWebJobsStorage"
    }
  ]
}

Step 6. Write the Azure Queue Trigger Function Code: Now, create a file named index.js and implement the Azure Queue Trigger Function using Nodemailer.

const nodemailer = require("nodemailer");

module.exports = async function (context, myQueueItem) {
  context.log("JavaScript queue trigger function processed work item", myQueueItem);
  const transporter = nodemailer.createTransport({
    host: "smtp.office365.com",
    port: 587,
    ssl: true,
    tls: true,
    auth: {
      user: "[email protected]",
      pass: "***********",
    },
  });

  const mailOptions = {
    from: "[email protected]",
    to: myQueueItem,
    subject: "Test Email",
    text: "Hello, this is a test email from Node.js using Nodemailer!",
  };

  transporter.sendMail(mailOptions, (error, info) => {
    if (error) {
      console.error("Error sending email:", error);
    } else {
      console.log("Email sent:", info.response);
    }
  });
};

The code has been finalized. Please execute it by pressing F5,

Proceed by initiating the function, and then include your email address in the Azure Queue Storage.

Now, verify that your function app is receiving your email ID from the queue storage.

The function has been successfully triggered. Please check your email for the message sent from the function app.

Step 7. Deploy your function app to Azure using Visual Studio Code or your preferred deployment method. Once deployed, add a message to the "mail-trigger" queue in the Azure Storage Account. Check the Azure Function logs to see the processing details and verify the email sent to the specified address.

Conclusion

Well done! You have successfully developed an Azure Queue Trigger Function using Node.js and Nodemailer for sending emails triggered by messages in an Azure Storage Queue. This implementation offers versatility for handling diverse automation scenarios within your applications. Delve into additional Azure services and features to further augment and refine your automated workflows. If you have any questions or concerns, please feel free to share them in the comments section.