Page tree

OpBot - virtual assistant for your virtual datacenter

Skip to end of metadata
Go to start of metadata


Download the OpBot virtual Appliance

Login into your Slack account and add OpBot using the button below

Add to Slack

Write down the API Key (you´ll need that key when importing the virtual appliance)

On this page:

Installation & Configuration

Extract the downloaded archive containing the virtual appliance and import it using either the Windows vSphere Client or the VMware vSphere Web client.

Deploy vApp of OpBot

After choosing the Cluster, ESXi Host, Datastore and Network, the OVF Deployment Wizard asks you for the vApp specific settings.

VMware vApp Network settings

These are the Guest OS settings consisting of:

  • Hostname
  • Network Configuration, DHCP enabled or IP (Don´t forget the DNS server that is used to resolve your vCenter and!)
  • Proxy if needed (important as OpBot needs to connect to

VMware vApp vCenter and Slack config

  • VMware vCenter IP or FQDN (remember to configure DNS if needed)
  • VMware vCenter credentials (please only use a read-only user for security reasons)
  • Slack API token (the one you wrote down when adding the custom bot)
  • OpBot Key - you should have received an email when starting your trial

That´s it – just power on the virtual machine and if everything has been setup correctly, OpBot should be active in Slack.

OpBot direct chat message

Important: You can change any of the configurations within the vApp settings and restart the VM to activate them. Just think about a password change for the VMware vCenter account.

Change OpBot Configuration later

Import using PowerCLI

If you want to automatically import the vApp into your vCenter without typing all information manually, please customize the following PowerCLI snippet:

OpBot vApp Import
connect-viserver "vcenter" -User "" -Password ""
$VMHost = Get-VMHost "ESXi"
$Datastore = Get-datastore "DataStore"
$Network = Get-VirtualPortGroup -Name "VMNetwork" -VMHost $vmhost
$Config = Get-OvfConfiguration opbot.ovf
$config.NetworkMapping.VM_Network.Value = $Network
$config.Common.dhcp.value = $false
$config.Common.hostname.value = "opbot"
$config.Common.ip.value = "ApplianceIP"
$config.Common.netmask.value = ""
$ = "ApplianceGW"
$config.Common.dns.value = "ApplianceDNS"
$config.Common.domain.value = "Appliance.domain"
$config.Common.vmware_login.Value = "vCenteruser"
$config.Common.vmware_password.value = "vCenterpw"
$config.Common.vmware_vcenter.Value = "vCenterIP"
$config.Common.slack_token.Value = "xoxb-"
$config.Common.opbot_lickey.Value = "####-#####-#####-#####-#####"

Import-VApp -name "opbot" -Source opbot.ovf -OvfConfiguration $config -VMHost $vmhost -Datastore $Datastore | start-vm

Update of the appliance using PowerCLI

Luc Dekens wrote a great article how to upgrade the appliance and saving all the vApp settings before:


Can I deploy multiple Bots within one Slack account?

Yes, but Slack doesn't allow multiple OpBots at the same time. Nevertheless, you can just add another integration and use a custom bot (search for Bots). You can use the Slack Token for another deployed OpBot appliance.

Write a comment…