Nimbus Power Automate Connector

Leverage parameter retrieval and parallel automation within your workflows

Nimbus supports MS (Microsoft Power Automate) by providing a separate Connector called "Luware Nimbus".

Some possible use cases could be: 

  • A Simple Notification: Retrieve Nimbus Task -> Task gets Lost → Trigger an E-Mail 
  • Live-Data Exchange during Calls: On Updated Nimbus Task → Retrieve caller Info → Request Task Details from your CRM or User Directory → Update the Task Details
  • Call-Routing according to lists and parameters: e.g. VIP or Blacklist handling of calls based on Whitelists / Blacklists you keep within your service team.
With Flow connectors you can request user details and context from external systems as new users appear in the queue


  • A Microsoft Power Automate subscription with "Premium Tier" license is required to set up the necessary connectors in your Flows. 🔍 Note that the pricing for these accounts is determined by Microsoft and outside your Luware subscription.
  • Service Licensing Requirements - To use the Power Automate integration, your Nimbus service must be Enterprise or Contact Center licensed. Additional licenses can be assigned via License Management in the Administration UI.
  • Flow interaction requires an existing Nimbus service / team already provisioned on your tenant. Power Automate Trigger Events react to activities in your currently active Workflows – as defined in your Modality Service Settings. If your service has no (valid) workflow defined, the Events will not be recognized.
  • You need either Team Owner or Administrator to set up these Flow tasks . 💡 We recommend setting up flows as a Tenant Administrator as you have full access to services and related data entities within their respective Organization Units . This is also reducing the risk that Flow Actions and related Trigger Events stop working as data entities move or become unavailable due to changes on the user account.

Installing the Nimbus Power Automate Custom Connector on your Tenant

As the custom connector cannout be found on the Microsoft Store yet, you need to retrieve it manually and install it on your Tenant. 

💡We are currently working on a official connector certification and will inform about future changes via our Release Notes.
🤔Already got a connector installed? Learn how to Update an existing Nimbus Power Automate Connector.

Add Custom Connectors

1.Log into your Microsoft Power Automate  account.       
2-On the left menu, click on "More" > "Discover all".       
3.Locate and pin the "Custom Connectors" entry to your menu.

4.Select your new Custom Connectors entry.       
5.Add the top right, click "New custom connector" to open a pulldown. Select "Import an OpenAPI file".       
6.Enter Nimbus and the environment (e.g. Nimbus Production), then choose the OpenApi file according to your data cluster location: 

Nimbus Power Automate Connector URLs

Switzerland 01
Germany 01
Germany 02
UK 01
Nimbus Power Automate Connector URLs

✅ Make sure to configure your web proxies to allow access to these domains or whitelist the complete * domain.

🤔 How can I find out my location? The location of your data cluster is picked once during the first Service Provisioning. You can also see it in your browser URL when logging into the Nimbus Administration which redirects you to the location where your Nimbus instance is installed.

Define Connector Details

  1. Unfortunately a couple of things can not be specified in the OpenApi File. So we will need to edit them manually now.
    1. Upload the connector icon
  2. Set the Icon background color to #6E2878

Create an App Registration in your Azure Tenant

1.Register a new App on your Azure Tenant. 🔍 Refer to: 

 How to register the Connector as new Azure App

  1. Go to > App Registrations > New registration
  2. Name your application “Luware PowerAutomate Connector
    → The end result should look like this:

✅Keep this page open as you will need the Application (client) ID later.


2.Create the Application Secret for your new App.       
🔍Learn more at       
3.Fill out your Flow Config as follows.  Use your ClientId and Resource URL and fill out the Client secret with the step above.        
☝Note that these values are unique to you. Screenshots below are just examples.

Field Description

Filled-out App

Auth Type OAuth 2.0 (automatically filled)


Identity Provider ☝ Attention: By default Generic OAuth 2 is selected → Select Azure Active Directory
Client ID

Application / Client ID

✅ Taken from Azure App Registration (Overview > "Application (client) ID") → See previous step above.

Client Secret

Application / Client Secret (👇same as Resource URL)

✅ Taken from Azure App Registration (Certificates & secrets > Client secrets > New client secret > "Client Secret Value" → See previous step above.

☝ Make sure to paste the secret itself, not the Secret ID.

Login URL (automatically filled)
Tenant ID common (automatically filled)
Resource URL

Same as Application / Client ID

✅ Taken from Azure App Registration (Overview > "Application (client) ID") → See previous step above.

Scope (automatically filled)
Redirect URL

☝Will be automatically filled in once the connector is created → See next step below.

4.Click on "Create connector". ☝The Redirect URL will be filled in automatically.      
5.In Azure, make sure to enter the Redirect URL in your Enterprise Application Registration. 

Show me how...

  1. Add the Redirect URL:
  2. Check your App registration. It should have at least 1 Redirect URL and 1 secret.

6.Test your connector: On the last page of the connector creation process you can test your connector. Click New Connection and sign in with the account with which you will be creating the flows.

🤔 Connection refused? Your tenant admin needs to give consent on the "User.Read" Permissions of the Nimbus App registration. This will allow you to Sign-In on the connector on behalf of the tenant administrator.

Delegated User.Read Permission required for the Connector

7.Optionally share the connector with other owners / users if needed. When doing so, please keep the following notes in mind:


  • All users which need access to a shared flow to also need to be granted access to the Nimbus Power Automate Connector App itself.
  • Keep in mind that each user accessing the Nimbus connector also needs a Microsoft Power Automate license to create flows. 💡 Microsoft product licensing cost are outside of Luware scope.
  • Nimbus grants connector access only to Nimbus Service / Team Owners or Administrators Roles with according Permissions on your Tenant.     
    🔍 New users sharing the connector require the according role assigned (within User Administration ). Also refer to Service Permissions for more details on how user rights are granted per service.     
    💡 Most of our customers create Nimbus Power Automate Flows with a service account that is also Nimbus Tenant Admin at the same time. This ensures unhindered access to all services and their required flows while keeping maintenance on a minimal level.


Flows and User Access

Before creating new productive Power Automate Flows, keep in mind that your currently logged-in user account will be used. Access to Nimbus service data within Trigger Events depends on the User Role granted via Nimbus User Administration.

The following table will give you a brief overview on which roles to use when managing your (future) Flows:

Role Notes
Partner Admin Cannot use triggers for services in the customer tenant with his own account. Also have limited visibility on live-data.
OU Admin Can access the connector, but is not recommended to manage live call-data with.   
This role is primarily meant for assisting on configuration tasks, e.g. managing flow-related Address Books and Workflows.
Tenant Admin 

✅ Recommended!

  • Can use triggers for all service teams on the tenant.
  • Can see all tasks of service teams on the tenant.
  • Can use flow actions to access or update connected Address Books.
Team / Service Owner

☝ Usable, but limited access to data entities within Organization Unit rules of user account (reading up the path rule):

  • Can use triggers for assigned service teams only.
  • Can see all tasks of service teams only when part of the "Owner" group in MS Teams or where manually assigned as Service Owner.
  • No permissions to access or update connected Address Books .
Supervisor / User Have no access to the connector itself or any related configuration items and service settings.

🔍 Detail permissions for each Trigger Event and the related Flow Actions can be found on the Power Automate Permissions page - both for legacy and (to be) certified connectors.



You are now ready to use the Nimbus Connector within a Flow. We recommend carrying on with any of the following chapters:

  • As you clicked "Create Connector" in the earlier step, new Nimbus Trigger Events and Flow Actions should already be available for selection.
  • A consent warning may be shown once you add the Nimbus connector trigger / action event for the first time. → Once you re-add the item it should work permanently.

From here on out you can:


Table of Contents