Creating workflows for Mosyle users

Let Oomnitza be your single source of truth!

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

Connect Oomnitza and Mosyle in minutes

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

• • Workflows for creating users'
  • Workflows for getting a user's information by Email or User ID
  • Workflows for updating users'
  • Workflows for retrieving the SaaS user role and for deactivating SaaS users in Oomnitza

1.  

Before you start

Please note that the Oomnitza integration with Mosyle has updated its authorization process. For integrations created from October 9, 2023, onwards, Session authentication is required instead of the previously supported basic authentication. 

When adding workflows, select the Session Based alternatives.

For details on adding Session-based credentials to Oomnitza, see Adding your Mosyle credentials to Oomnitza. 

We recommend that you also create the extended integration for Mosyle users. You can use the information retrieved in these integrations to trigger workflows that can create, update, get user details, and much more.

Creating workflows

Create user workflows

To create a user workflow, you must complete these steps:  

1. Click Configuration > Workflows 
2. Click Add (+) and select Users from the Objects list.
3. Drag and drop the API block onto the Sandbox.
4. Click Edit on the API block and enter Mosyle in the search field. 
5. Select a preset:
   • Mosyle Create User Session Based
   • Mosyle Update User Session Based
   • Mosyle User Details by Email Session Based
   • Mosyle User Details by User ID Session Based
6. To choose a preset, click the forward arrow (>).
7. Select the credentials that you created in Adding your Mosyle credentials to Oomnitza.
8. Supply your Mosyle Access Token.
9. Configure the API Block following the preset instructions below, and save your changes.
10. 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. 
11. Connect the Blocks. 
12. Save, validate, and activate your workflow.

Using the Create User Session Based preset

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

• User ID: The Mosyle User ID. 
• User Name: The name of the user.
• User Type: Can be either ADMINGROUP_ADMIN or ENDUSER.

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 add fields that will be used in the request payload. For additional fields that can be used in the request payload refer to the below table.
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.

Key	Type	Required
user_id	string	Required
name	string	Required
type	ADMINGROUP_ADMIN or ENDUSER	Required
email	string	Optional
welcome_email	numeric. Select either (0, 1). 1 sends a welcome email after the user is created.	Optional

 

Using the Update User Session Based preset

The Update User Session Based preset enables you to update or modify a Mosyle user by their Mosyle 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 Body tab. You will notice that the Mosyle User ID is referenced in the property {{mosyle_user_id}}. Follow the mapping steps in Creating custom mappings so that this property exists in Oomnitza and is populated with information before you run this workflow. Alternatively, replace the property with the user id and surround with double quotation marks: for example "iduser": "123456". For additional fields that can be used in the request payload refer to the below table.
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.

Key	Type	Required
iduser	string	Required
name	string	Optional
identifier	string	Optional
email	string	Optional
managedappleid	string	Optional
type	ADMINGROUP_ADMIN or ENDUSER	Optional

 

Using the User Details by Email Session Based preset

The User Details by Email Session Based preset enables you to get a Mosyle user's details using their Email. 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 Mosyle User Email is referenced in the property {{email}}.
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. Once you have the entire response, you should then map individual JSON values to custom fields, as per the example below. For information on creating custom fields, see Creating Custom Fields in Oomnitza.

Using the User Details by User ID Session Based preset

The User Details by User ID Session Based preset enables you to fetch a Mosyle user by their Mosyle User ID.

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

• User ID: The Mosyle User ID. You can call the value in the workflow by entering: {{mosyle_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 Response tab. 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.

Reference articles for workflows

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

Create SaaS user workflows

You can create a Saas User workflow in Oomnitza using the Mosyle User Role preset. This preset supplies you with the Role of your SaaS users.

Prerequisites

Before you create a SaaS user workflow, you should have already run your extended user integration and selected User plus SaaS User to populate the software entry in the Software > SaaS menu.

To create a Saas User workflow using the Mosyle User Role preset, complete the following steps:

1. Click Configuration > Workflows 
2. Click Add (+) and select Software SaaS Users from the list.
3. Enter the name and a description of the workflow. 
4. Edit the Begin block by adding the rules that will trigger the workflow. For further information see SaaS User Roles.
5. Click the Blocks tab, and drag and drop the SaaS User Role retrieval block onto the canvas.
6. Click the Edit icon.
7. Enter Mosyle in the search field and choose the Mosyle User Role Session Based preset.
8. Click the right arrow >.
9. Select the credentials that you created in Adding your Mosyle credentials to Oomnitza.
10. Supply your Mosyle Access Token.
11. Select the Deactivate User checkbox to deactivate the SaaS user in SaaS > Mosyle > Users if they are not found in your Mosyle instance.
12. Click SAVE.
13. Connect the blocks.
14. Save, validate, and activate your workflow.

To view active Mosyle users in the SaaS Users UI, complete the following steps:

1. Click Software from the menu.
2. Select the Saas tab, and select your software entry for Mosyle.
3. Click Users in the side pane.
4. The Role column will be populated with the user details to confirm that this user has been found in your Mosyle SaaS.

Reference articles for creating workflows

• Creating SaaS user workflows.
• Offboarding SaaS users.