Using LMS365 Connectors in Microsoft Power Automate

How to use LMS365 Connectors in Microsoft Power Automate.

LMS365 give you an ability to automate some of the most common actions and manual processes in the LMS365 via Microsoft Power Automate. It means to react on the events happening LMS365 and send data to the LMS. You can use the existing templates for your flow or create your own one.

To create your own flow:

  1. 1. Go to the Microsoft Power Automate page and and sign in.

  2. 2. Click My Flows section, and then click the New button in the top navigation bar and select Instant − from blank button:

Picture 1

  1. 3. On the creation page, you can see the full list of the MS Power Automate connectors. Search for the LMS365 to see all actions related to the learning system:

Picture 10

The Connector consists of two groups of items:

Triggers – give you the ability to subscribe to some events in the LMS. Each trigger has a proper title that describes when the event is triggered. Usually, that is the starting point of the flow.
For example, the trigger “When a user has been deleted” means that the operation will be triggered when a user has been disabled/deleted from LMS365.

Actions – give you the ability to affect LMS. That means these are the set of predefined API calls to the LMS service.
For example, an action “Approve enrollment request” will approve the enrollment request.
For more information about the actions, visit
the connector reference for the LMS365.


  1. 4. Select the desired trigger from the list.

  2. 5. Add the steps.

  3. 6. Search for the required action that can be performed within the LMS365.

  4. 7. Fill in the required fields.

  5. 8. Add other actions if needed.


Let us create a simple flow which reacts to the Course Published event, gets the course information, and sends an email with the course information to the specified users. To perform this action:


  • Choose the “When training has been published to a catalog” trigger:


Picture 8

If you use the LMS365 Connector for the first time, enter connection name (LMS365) and credentials for the LMS API service. Please use the API key for both username and password fields.


  • 🛈The API key is a password for your LMS365 data. Keep it safe.

  • 🛈To get the API key for your tenant domain e.g., the Office 365 Global Administrator should navigate to LMS365 Admin Center – Global Settings – Settings – LMS Configuration – API key management and copy the API key:

Picture 5


  • After the connection is set, you will see a message that your flow has only a starting point and you need to add new steps:


Picture 11


  • Click the New step button.

  • Enter LMS365 in the search box to find the available LMS connector action.

In our example, we want to get information about the course that has been published – we select “Get course details” action:


Picture 2

  • Specify the Course Id value in order to get the information about the specific course. Click the field to see all available data you can operate with. Select the Course Id from the list to proceed:


Picture 3

  • 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 new action).
    In our example, we will select the Office 365 Outlook Connector and search for the ‘Send an email’ action:

Picture 6

  • 🛈Once you have set up a specific connection (Outlook, LMS365, SharePoint, etc.), you can reuse that connection in all flows.


and fill in some course data (e.g. title and description):


Picture 7

That is all, we are ready with the Flow that is triggered when a Course has been published, gets the detailed information about it, and sends Course’s description via email to the specified recipients.
The logic and approach are the same for all other cases.

You can make a request to get the desired data from API via Microsoft Power Automate as well. Let us create one more flow to get the list of all Courses and the enrollments withing the Course Catalog:

  • Choose the “Send an HTTP request” trigger and define the methods for the HTTP request. In our case use the GET as method as we need to receive the information. 


There are 5 HTTP methods: GET, PUT, POST, PATCH, DELETE.

  • the GET method is used for retrieving information,

  • the PUT method is used for updating the existing resource,

  • the POST method is used for creating a new resource,

  • the PATCH method is used for making a partial update on a resource,

  • the DELETE method is used for deleting resources.


  • Specify the path in the Uri field. You can get these data from Swagger. Navigate to the desired endpoint. In our case we use the endpoint
    GET /odata/v2/Courses that returns the list of all Courses. As we want to have all enrollments, we need to specify the “Enrollments” as the parameter. So the path will be Courses?$expand=Enrollments:


Picture 4

Once you have tried out the endpoint you can find the Uri in the Request URL field as well.

  • 🛈You can find all available parameters in the Responses field – Model.


When you run the flow, you will find required information in the Body field. The API will response in the JSON format:

"Enrollments": [


"Id": "407de1a8-e9a0-40a6-94ed-e70d7a1992b4",

"CourseId": "144e2fc1-76d1-4387-ae26-27df7f77ef26",

"UserId": "ae5119a5-3426-4402-982a-f071b54f0545",

"UserLoginName": "c:0t.c|tenant|e6e6f293-8809-4c64-a888-71f824be52df",

"Roles": [






To apply it for each course you need to add the new “Apply to each” action, click Expression and specify the following expression, which is the output from the previous step and looks like:


Picture 17

  • To get all enrollments add one more “Compose” action.

Picture 18

In the Input field add the desired expression. As we want to get the enrollments for each of the courses, we need to specify the following expression:


That is all, we are ready with this flow and get all enrollments:

Picture 15


Useful links:


The JSON tutorial;

The API fast track learning.


Was this article helpful?
3 out of 6 found this helpful


Article is closed for comments.