ManageEngine OpManager

Get alerts from ManageEngine OpManager into Squadcast

Follow the steps below to configure a service so as to push related alert data from ManageEngine OpManager onto Squadcast.

Squadcast will then process this information to create incidents for this service as per your preferences.

Using ManageEngine OpManager as an Alert Source

On the Sidebar, click on Services.

You can either choose to use existing service or create a new service

Now, click on the corresponding Alert Sources button.

Select ManageEngine OpManager from Alert Source drop down and copy the Webhook URL shown.

Create a Squadcast Webhook in ManageEngine OpManager

  • Go to you /Opmanager/bin folder and run the following command
sudo wget

Once the file is downloaded please make sure that the file has execute permissions for your ManageEngine OpManager user.

If not, then please provide the same using the following command

sudo chmod +x
  • Login to ManageEngine OpManager.
  • Go to Inventory->Devices and select the device whose alerts you want to send to Squadcast.
  • Click the Envelope Icon on the top right corner to configure notifications and click Add

Select Run Program.
In Command Name paste the following:


In Program Arguments paste the following (make sure to replace the url with the Webhook URL you copied from the Squadcast dashboard):

"" "$alarmid" "$message" "$displayName" "$category" "$stringseverity" "IP Address:$DeviceField(ipAddress)" "$strModTime" "$eventType"  "Entity: $entity"

Click Next.
Check all the severities you want to receive notifications for.

Select appropriate time window and trigger options.
Click Next.

Give a name to the notification profile and click Save.

Now whenever an event is triggered in ManageEngine OpManager, an incident will be automatically created in Squadcast.

Updated 5 months ago

ManageEngine OpManager

Get alerts from ManageEngine OpManager into Squadcast

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.