With the LMS365 connector, you can easily subscribe to events happening inside the LMS365 applications as well as you can perform actions based on the data coming from LMS365 events.
To see how this works, we will look at an example of using the LMS365 connector with Microsoft Power Automate.
You need to use an API key with Full Control permissions to create flows with Microsoft Power Automate. If you use an API key with Read Only permissions, you will receive the following error: “The response is not in a JSON format”.
Here, you can find templates for flows in LMS365 created with Microsoft Power Automate.
You can also create your own unique flows with Microsoft Power Automate that will react to the events happening inside LMS365 and send data to LMS365 if needed.
To create your own flow, go to https://powerautomate.microsoft.com and sign in. Select the My Flows section and then Create from blank.
Search for “LMS365” to see all actions related to the learning system.
The LMS365 connector consist of two groups of items:
- Triggers – give you the possibility to subscribe to events in the LMS. Each trigger has a title that describes when the event is triggered. Usually, that is the starting point of the flow.
For example, the trigger LMS365 - When training has been published to a catalog means that the event will be triggered when any course has changed its status to Published and is now available in the course catalog.
- Actions – give you the possibility to affect LMS. That means, these are the set of predefined API calls to the LMS service.
For example, the action Enroll user to training gives you an ability to enroll a user in to a specific course.
Let’s create a simple test flow which will react to the Course Published event, will get the course information, and send an email with the course information to a specified users.
To do this, please follow the steps below:
- Select the relevant event from the Triggers list.
- If you use the LMS365 connector for the first time, you will be required to enter your credentials for the LMS API service using an API key for both the username and password field.
- After the connection is set, a message will notify that your flow only has a starting point and that you need to add more steps.
- Select New step > Add an action option and then enter LMS365 in the search field to find the available LMS connector action.
In our example, we want to get information about the course that has been published. Therefore, we select the Get course details action.
- The action’s block will be added to the flow. Here, you need to specify the Course Id value in order to get the information about the specific course.
- Select the field to see all available data you can operate with and select the course Id from the list.
- After the Course Id value is selected, you can choose what to do with the data returned by the Get course details action (by adding a new action).
In our example, we will select the Send email action and fill in course data.
That is all. We are now ready with a flow that is triggered when a course has been published, gets detailed information about it, and sends the course description via email to the specified recipients.
The logic and approach are the same for all other cases. The same functionality is provided by Microsoft Power Apps and Microsoft Azure Logic Apps.