PRECONDITIONS
☝External licensing costs
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 of your Luware subscription.
☝Nimbus Licensing
Licensing: To use the Power Automate integration, at least one of your Nimbus services must be Enterprise Routing or Contact Center licensed. Additional licenses can be assigned via License Management in the Administration UI.
Configuration: Flow interaction requires an existing Nimbus service already provisioned on your tenant. Power Automate Trigger Events react to Workflow Activities in your currently running Nimbus Workflows – as defined in your Modalities Service Settings. If your service has no (valid) workflow defined, trigger events will not be recognized.
☝User Roles
You need either Team Owner or Administrator in Nimbus to set up Power Automate Flows. Check that your currently logged-in user account has one of the required Nimbus Power Automate Roles.
💡Tip: To keep impacts and licensing cost to a minimum we recommend setting up flows as a Tenant Administrator as you have full access to all services and their configuration items located within their respective Organization Units. This also reduces the risk that Flow Actions and related Trigger Events suddenly stop working, as Nimbus Configuration entities, permissions or related user roles change.
Learn more about this…
The same user account UPN you use in Microsoft Flow is matched with the according User Role granted via Nimbus User Administration. Nimbus data is filtered via the Organization Unit placement of your logged-in user account. In effect, Services and Users outside of this OU placement are (not) shown in Flow Actions and Trigger Events to prevent accidental manipulation.
The following table will give you a brief overview on which Nimbus User Role can manage Power Automate flows:
| Nimbus User Role | Notes on Flow access |
|---|---|
| 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, as the view on services and user data is restricted by Organization Units. If the Admin role is moved or deprecated, flows may cease to function correctly.
💡This role is primarily meant for assisting on configuration tasks, e.g. managing flow-related Address Books and Workflows. |
| Tenant Admin |
✅ Recommended!
|
| Team / Service Owner |
☝ Usable, but limited access to data entities within Organization Unit rules of user account (reading up the path rule):
|
| Supervisor / User | ❌ Have no access to the connector itself or any related configuration items and service settings. |
🔎 Refer to Power Automate Roles for more details.