Creating workflows for Device42 devices

Let Oomnitza be your single source of truth!

You'll get visibility of your devices as data from Device42 is automatically transformed into consumable information and actionable insights.

Connect Oomnitza and Device42 in minutes

You'll get visibility of your Device42 devices by creating configurable workflows to automate tasks such as:

• • Workflows for creating devices
  • Workflows for deleting devices
  • Workflows for updating devices

Before you start

Adding the Device42 Organization URL as a global variable

Creating workflows

Create asset workflows

Create Device

Modify Device

Delete Device

Before you start

Before you create the asset workflows, you need to have added your Device42 credentials to Oomnitza.

We recommend that you also create the extended integration for Device42 devices. You can use the information retrieved in these integrations to trigger workflows that can delete devices, create devices, and much more.

Adding the Device42 Organization URL as a global variable

To save time entering information when you create workflows, you can add the Device42 Organization URL as a global variable in Oomnitza.

1. From the menu, go to Configuration>General.
2. Click Global Settings.
3. Click Add new variable (+). 
4. Enter Device42.OrgURL as the variable name.
5. Enter the URL of your Device 42 system.
6. Save your changes.

Creating workflows

Create asset workflows

To create an asset workflow, you must select the Device 42 credentials that you created in Adding your Device42 credentials to Oomnitza.

To choose a preset, complete these steps:  

1. Click Configuration > Workflows > Assets.
2. Click Add (+) and enter the name and description of the workflow.
3. Click Add new. A Begin and End block are automatically added to the Sandbox.
4. Drag and drop the API block onto the Sandbox.
5. Click Edit on the API block and enter Device42 in the search field. 
6. Select a preset:
   • Device42 Create Device
   • Device42 Modify Device
   • Device42 Delete Device
7. To choose a preset, click the forward arrow (>).
8. Configure the API Block following the preset instructions below, and save your changes.
9. Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to New you can trigger a workflow every time a new asset is created. Refer to Using the Begin block.
10. Connect the Blocks. 
11. Validate, launch, and save your workflow.

 Understanding Workflows

Using the Create Device preset

The Create Device preset enables you to create a new device with the name supplied as the required argument.

When you select this preset you need to supply the following information:

• Name: Asset Name.
• Serial Number: The serial number of the device. If a device with a matching serial number is found, that device is updated. Serial numbers with fewer than 3 characters in length are ignored. Also, certain generic serial numbers like 123456789 or ‘not specified’ are ignored.
• Hardware: Hardware model name. 

You can configure the message payload by selecting Advanced Mode.

1. In the API block window, click the Advanced Mode button located in the upper right of the window.
2. Select the Body tab. You can, update or add fields (such as notes) that will be used in the request payload. For information on the fields that are permitted in the request payload refer to Device42 API Documentation: Create/Update Device.
3. Select the Response tab. You can map the entire response by placing {{response}} in the Response field and mapping it to a custom long text Oomnitza field, such as API Response. For information on creating custom fields, see Creating Custom Fields in Oomnitza.

Using the Modify Device preset

The Modify Device preset enables you to update an existing device using the Device ID.

When you select this preset you need to supply the following information:

• Device ID: Device ID. If you have created a device integration and followed the mapping steps in Creating custom mappings you can add the property {{device42_device_id}}to this field. Otherwise, you can enter the Device ID. 
• Serial Number: The serial number of the device. If a device with a matching serial number is found, that device is updated. Serial numbers with fewer than 3 characters in length are ignored. Also, certain generic serial numbers like 123456789 or ‘not specified’ are ignored.
• Hardware: The name of the hardware model for the device. An update will only occur if no hardware model is previously assigned to the device.

You can configure the message payload by selecting Advanced Mode.

1. In the API block window, click the Advanced Mode button located in the upper right of the window.
2. Select the Body tab. You can, update or add fields (such as notes) that will be used in the request payload. For information on the fields that are permitted in the request payload refer to Device42 API Documentation: Create/Update Device.
3. Select the Response tab. You can map the entire response by placing {{response}} in the Response field and mapping it to a custom long text Oomnitza field, such as API Response. For information on creating custom fields, see Creating Custom Fields in Oomnitza.

Using the Delete Device preset

The Delete Device preset enables you to delete a device, using a Device42 Device ID. You can configure the message payload by selecting Advanced Mode. 

You can configure the message payload by selecting Advanced Mode.

1. In the API block window, click the Advanced Mode button located in the upper right of the window.
2. Select the Information tab. You will notice that the Device42 Device ID is referenced in the property {{device42_device_id}}. Map the Device ID to this field by creating an asset integration and following the mapping steps in Creating custom mappings, otherwise, enter the Device ID.
3. Select the Body tab to a add field to the message body. For example, you might want to add the following: {"delete_vms": "yes"}to also delete Virtual Machines on the device. For further information, refer to Device42 API Documentation: Delete Device.
4. Select the Response tab. You can map the entire response by placing {{response}} in the Response field and mapping it to a custom long text Oomnitza field, such as API Response. For information on creating custom fields, see Creating Custom Fields in Oomnitza.

For further information on workflows see:
 Understanding workflows
 Workflow block overview
Enhanced API Block