Power Automate: Direct Link to Call Recordings
How to use the Luware Recording Power Automate flow to generate a direct link to a call recording from a Nimbus call.
This is an evolving integration. Specifications are subject to change and this article will be updated accordingly.
☝ Prerequisites and Licensing
The Luware Recording APIs require an additional license add-on. Contact solutions@luware.com or your Customer Success specialist for details.
The following must be in place before the flow can be deployed. A Luware engineer will confirm these are complete before starting configuration.
- An Azure Key Vault created and ready to use as part of the flow.
- An Azure Entra ID application registered within the customer's tenant. This is used in the flow to connect to the Azure Key Vault.
- The Nimbus Power Automate Connector installed. This will be provided by the Luware System Engineer.
- A Microsoft Power Automate subscription with a Premium Tier license. Pricing for these accounts is set by Microsoft and is outside your Luware subscription.
- A Global Administrator account on the customer's Azure tenant.
- A Nimbus Service Line Owner account. The account used to build and run the flow must be an owner of the Nimbus Service Line to be recorded.
Overview
Power Automate (formerly Microsoft Flow) is a workflow automation tool within the Microsoft 365 suite. Luware Recording integrates with Power Automate to generate a direct link to a call recording at the point a call ends. Once the link is available in the flow, it can be passed into any system or service that your organization connects to Power Automate, such as a CRM, ticketing system, or data store.
For a general introduction to Power Automate, see the Microsoft Power Automate documentation.
Target Audience
This article is aimed at a technical audience with working knowledge of Microsoft Power Automate.
Nimbus Service Lines
During flow configuration, you will need to provide the UPN(s) of the Nimbus Service Lines you want to obtain call recording links for. Multiple Service Lines can be added to a single flow.
Power Automate Configuration
All prerequisites must be completed before configuration begins. A Luware engineer will work with you in a one-hour workshop to import and configure the flow. The steps below outline what happens during that session.
Create the data connections in Power Automate to be used with the flow.
Import the Power Automate flow. The Luware engineer will send you the flow file before the workshop, ready for import.
Configure the Nimbus Service Lines. Update the imported flow with your preferred Nimbus Service Line UPNs. These are added on the trigger as shown below.
Store the key vault values. Your Luware Recording System Engineer will provide the values below. Store these securely in your Azure Key Vault.
Leave the remaining variables unchanged. No modification is required for the variables shown below.
API token authentication. This section of the flow retrieves the API token and stores it in a variable. It runs inside a do-until loop so it will keep retrying until a token is obtained.
Call recording link retrieval. This section makes an API GET request to the VFC system to find the ongoing call for the recorded user's extension, extracts the conversation identifier, builds the direct link, and stores it in the Final Call URL variable. From here, the link can be used however your flow requires.
Testing
Testing and sign-off are the customer's responsibility. Luware will provide a test plan to follow and can assist if issues arise during testing, but is not responsible for issues that occur once the flow is in production.
Limitations
- This integration works only with Nimbus Contact Centre calls.
Using the Recording Link
Once the flow is configured, the direct recording link is stored in the Final Call URL variable at the end of each call. You can extend the flow to pass this link to any system supported by Power Automate, including CRMs, ticketing platforms, databases, or notification services. Microsoft provides a full connector library at learn.microsoft.com/en-us/connectors/connector-reference/.