Creating workflows for Device42 users

Let Oomnitza be your single source of truth!

You'll get visibility of your assets and users 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 users by creating configurable workflows to automate tasks such as:

• • Workflows for deleting users'
  • Workflows for getting a user's details
  • Workflows for updating users'

Before you start

Adding the Device42 Organization URL as a global variable

Creating workflows

Create user workflows

Create User

Modify User

Delete User

Before you start

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

We recommend that you also create the extended integration for Device42 users. You can use the information retrieved in these integrations to trigger workflows that can delete users, get user details, 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 user workflows

To create a user workflow, you must select credentials and enter the Device42 domain.

To choose a preset, complete these steps:  

1. Click Configuration > Workflows 
2. Click Add (+) and select People from the list.
3. Drag and drop the API block onto the Sandbox.
4. Click Edit on the API block and enter Device42 in the search field. 
5. Select a preset:
   • Device42 Create User
   • Device42 Modify User
   • Device42 Delete User
6. To choose a preset, click the forward arrow (>).
7. Configure the API Block following the preset instructions below, and save your changes.
8. Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to Schedule and add a rule so that the Email Equals <EmployeeEmail> you can trigger a workflow to fetch a user matching a certain name on a specific date. Refer to Using the Begin block. 
9. Connect the Blocks. 
10. Save, validate, and activate your workflow.

Using the Create User preset

The Create User preset enables you to create a Device42 user. When you select this preset you need to supply the following information:

• Name: End user name. 
• Email:
• Contact: Contact number.

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 Users.
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 User preset

The Modify User preset enables you to update or modify a Device42 user by their Device42 User ID. When you select this preset you need to supply the following information:

• Name: End user name. 
  
• Contact: Contact number.

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 will notice that the Device42 User ID is referenced in the property {{device42_user_id}}.You can map the User ID to this field by creating a user integration and following the mapping steps in Creating custom mappings, otherwise, you can enter the User ID. You can also update or add fields (such as notes, location, and email) 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 Users.
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 User preset

The Delete User preset enables you to delete a user by their Device42 User ID.

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 User ID is referenced in the property {{device42_user_id}}.You can map the User ID to this field by creating a user integration and following the mapping steps in Creating custom mappings, otherwise, you can enter the User ID.
3. Select the Response tab. Map the Response field {{response}} to a custom Oomnitza field. You can create a custom field by following the steps in Creating custom fields.

For further information refer to Device42 API Documentation: Delete Users.

Reference articles for workflows

• Mapping positive and negative responses
• Troubleshooting workflows 
• Using the API block