Email IntegrationΒΆ

Simple Mail Transfer Protocol (SMTP) provides DivvyCloud the ability to send email notifications and is compatible with all DivvyCloud resources. As an example, you can email a listing of all Instance Owners who have provisioned an instance without corporate-required tags (or Instance Owners who have modified an instance removing corporate-required tags.)

Follow the steps below to configure and leverage the integration:

1.) Login to DivvyCloud. Navigate to System Administration on the left-hand side menu.


2.) Configure Email (SMTP). Email is isolated to an organization allowing you to tailor email settings to business units, geographies, or however your enterprise is structured. Select Actions next to the organization you wish and then select Configure Email (SMTP).


3.) Configure SMTP Settings – Enter Information. Enter in the information relevant to your organization. E.g.,

a. Hostname/IP. Enter the name or IP address of the host used for SMTP transactions, e.g.,

  1. Port. Enter the port used for SMTP transactions, e.g., 465

c. When enabled SSL will be used to encrypt communications. Select if you want DivvyCloud to use Secure Sockets Layer (SSL) to encrypt the connection, which is recommended if you are sending sensitive information

d. Username. Optional. Enter the username for the account that you will use to connect to the SMTP server, e.g.,

e. Password. Optional. Enter the password of the account that you will use to connect to the SMTP server

f. Sender. Enter the email address you wish to use as the default for emails sent from DivvyCloud, e.g.,


4.) Configure SMTP Settings – Test. Click test to see if your settings are correct. You should see a confirmation message indicating success


5.) Configure SMTP Settings – Submit. Click on submit to save your settings. You should see Email Configured has a checkmark next to your organization


6.) Test with a Bot. You can now leverage the DivvyCloud Email action within your Bot configurations. To test, you can create a bot that based upon its scope and filtering will return a positive result. For example, you can examine a cloud account to see if it has a cloud user. (N.b., you will receive one email per match, so choose a test without too many matches!) For the bot’s action, you can now send yourself an email for all matches. You can use Jinja2 templating to add resource-specific data in your email. Also allows you to dynamically assign a recipient via one or more tags. Enable batch execution so you can run a test immediately. After saving, remember to first Resume the bot, then Retroactive Scan the bot to run it, and finally check your inbox to see the results.