Creating workflows for users

Let Oomnitza be your single source of truth!

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

Create an Oomnitza user workflow in minutes

Create configurable workflows to automate tasks relating to Oomnitza users such as:

• Getting a SaaS user’s role
• Returning the assets and SaaS applications assigned to a user
• Deleting a user

Navigation

Before you start

Creating workflows

Creating Saas user workflows

User Role preset

Creating user workflows with the API block

Delete User

Count assigned assets for user 

Read user details from SaaS user 

Get assigned assets from user 

Get assigned SaaS from user

Before you start

Before you can configure any of the available workflows with Oomnitza, you first need to enter your credentials in Oomnitza and set global variables. For further information, refer to Getting started with Oomnitza workflows.

Creating Saas user workflows

You can create the SaaS User workflow by following the steps in Creating Saas user workflows. To locate the available presets, enter Oomnitza in the Select Preset search field and select the Oomnitza User Role preset.

Oomnitza User Role preset

The Oomnitza User Role preset enables you to read a SaaS user’s role from Oomnitza. When you select this preset, enter the following details in the Configure section:

• Your Ooomnitza Credentials that you created in Adding the credentials.
• Your Subdomain should be derived from the variable created in Setting the Oomnitza subdomain as a global variable or entered manually. 

Creating workflows

Creating asset workflows with the API block

To reduce your workload and automate complex and repetitive tasks, you can create workflows with the API block by following the steps in Creating asset workflows with the API block. To locate the available presets, enter Oomnitza in the Select Preset search field. Select your preset of choice and for every preset enter the following information in the Configure section:

1. Your Ooomnitza Credentials that you created in Adding the credentials.
2. Your Subdomain should be derived from the variable created in Setting the Oomnitza subdomain as a global variable or entered manually. 

For information on the specific requirements for each preset, click one of the links below:

Delete user

Count assigned assets for user

Read user details from SaaS user

Get assigned assets from user 

Get assigned SaaS from user

Using the Oomnitza Delete user preset

The Oomnitza Delete user preset enables you to delete/deactivate a user from Oomnitza. Use the Advanced Mode to configure the message payload. To do this, 

1. Click the Advanced Mode button located in the upper right of the window.
2. Select the Information tab.
3. The user id is assumed to be stored in the field {{user_external_id}}. If you do have have a field matching this name, you can create one in People>Customization. For further information, see Creating Custom Fields in Oomnitza.
4. Select the Response tab. You have the option to map the Response field {{response}} to a custom long text Oomnitza field. You can create a custom field by going to People>Customization. 

Using the Oomnitza Count assigned assets for user preset

The Oomnitza Count assigned assets for user preset can be used within people workflows to count the number of assets that are assigned to user. Use the Advanced Mode to configure the message payload. To do this, 

1. Click the Advanced Mode button located in the upper right of the window.
2. Select the Information tab. The user id is assumed to be stored in the field {{username}}. If you do have have a field matching this name, you can create one in People>Customization. 
3. Select the Response tab. Map the Jinja statement, which counts all assets that are assigned to a given user, to a custom numeric Oomnitza field. You can create a custom field by going to People>Customization. 

Tip:  In some cases you might want to only count certain assets. To do so, you can customize the URL in the Information tab. For example, if you wish to only count the number of notebooks, you would add %20AND%20asset_type%20eq%20%27Laptop%27 at the end of the URL.

Using the Oomnitza Read user details from SaaS user preset

The Oomnitza Read user details from SaaS user preset enables you to read the last login field from a SaaS user and add it to SaaS User. When constructing a workflow that uses this preset, the following information is mandatory:

• Map Last Login to Field. A DateTime field which will contain the last login date. The field name should be in lower case, and spaces replaced with an underscore. You can create a custom field by going to People>Customization. For further information, see Creating Custom Fields in Oomnitza.

Use the Advanced Mode to configure the message payload. To do this, 

1. Click the Advanced Mode button located in the upper right of the window.
2. Select the Information tab. The user id is assumed to be stored in the field {{user_id.username}}. If you do have have a field matching this name, you can create one in People>Customization. 
3. Select the Response tab. You have the option to map the Jinja statement, which gets the users last login, to a custom DateTime Oomnitza field. You can create a custom field by going to People>Customization. The Jinja statement returns the response in the same manner as the Map Last Login to Field, except in the form of a dict or array. This format may be preferable for troubleshooting. 

Tip: You could use this preset in conjunction with the Slack last login user integration. You would need to create the integration and then run a scheduled workflow using the Slack SaaS user role API and Read user details from SaaS user preset to pull the slack_last_login field into the Oomnitza Last Login to Field.

Using the Oomnitza Get assigned assets from user preset

The Oomnitza Get assigned assets from user preset can be used within workflows to get the assets that are assigned to a user. This preset returns the assets assigned to a user in comma separated format.

When you select this preset, you should enter the Oomnitza field names the JSON response will map to. 

• Map Computer Name to Field. For example, computer_name. The computer name of the asset assigned to the user. 
• Map Serial Number to Field. For example, serial_number. The serial number of the asset assigned to the user. 

For information on creating Oomnitza fields, see Creating Custom Fields in Oomnitza.

Next, you can use the Advanced Mode to configure the message payload. To do this, 

1. Click the Advanced Mode button located in the upper right of the window.
2. In the Information tab, you will notice that the user information is assumed to be stored in the  {{email}} field. If you do have have a field matching this name, you can create one in People>Customization. 
3. Select the Response tab. 
4. You can use Jinja in the API response to configure the response mapping. For example, if you do not have {{computer_name}} in your API response, but do have a {{model}}, you can add the following to the Response field and map it to a suitable Oomnitza field:
   

   {% if response %}{{ response|map(attribute='model') | list | join(',
     ') }}{% else %}{% endif %}  

Using the Oomnitza Get assigned SaaS from user preset

The Oomnitza Get assigned SaaS from user preset enables you to get a list of SaaS applications assigned to a user.

When you select this preset, you should enter the Oomnitza field names the JSON response will map to. 

• Map Saas Name to Field. For example, saas_name. The name of the SaaS application assigned to the user. 
• Map Saas ID to Field. For example, saas_id. The SaaS id of the application assigned to the user. 
• Map Assigned Contract ID to Field. For example, assigned_contract_id. The contract id of the SaaS application assigned to the user. 

For information on creating Oomnitza fields, see Creating Custom Fields in Oomnitza.

Use the Advanced Mode to configure the message payload. To do this, 

1. Click the Advanced Mode button located in the upper right of the window.
2. Select the Information tab. The user id is assumed to be stored in the field {{username}}. If you do have have a field matching this name, you can create one in People>Customization. 
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. Once you have the entire response, you can then map individual JSON values (such as {{response[0].assigned_contract_id}},{{response[0].roles[0].role_id}}) to custom fields. For further information, refer to the Enhanced API Block.
   

Example response:

[
  {
    "assigned_contract_id": "string",
    "available_contracts": [
      {
        "contract_id": "string",
        "contract_name": "string",
        "contract_type": "string",
        "has_free_license_keys": true
      }
    ],
    "roles": [
      {
        "role_id": "string",
        "role_external_id": "string",
        "role_external_label": "string"
      }
    ],
    "estimated_spend": 0,
    "saas_id": "string",
    "saas_name": "string",
    "uid": 0
  }
]

For further information on workflows see:
 Understanding workflows
 Workflow block overview

Unleash the power of Oomnitza

To get valuable actionable insights that help you manage your assets, learn how to:

• Configure dashboards for your users and software
• Configure custom reports about your users and software
• Create workflows to automate tasks

See  Getting started for more information.