This page will always reflect the latest Release Notes, recent improvements and changes made to Nimbus.

Other Information Resources:

• Our Release Note History contains information on all previous releases from this year.
• Updates on our Nimbus Power BI Template are distributed on request. Please refer to the Nimbus BI Template Release Notes for updates.
• To stay up to date on Nimbus feature and upcoming maintenance, please visit the following resources:

📣Important Announcements

Please take note of the following long-term and ongoing announcements below:

End of announcements. Regular release notes continue below.

22 July 2026 - 1.132 Release Notes

🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is being rolled out sequentially on our clusters:

Auto Arrange: Clean layout for Workflows

Workflow design in Nimbus just got easier. With the new Auto arrange button, Nimbus users can now instantly arrange the layout for their entire workflow: Blocks are neatly positioned and connector lines stay easy to follow, no matter how large or complex the workflow gets. One click is all it takes to keep a flow looking sharp, any time structural changes are made.

🔎 Added with this update:

• Workflow editor and workflow template editor: a new Auto arrange button in the toolbar, alongside Expand all, Collapse all, and Fit to screen.
• One click arranges the entire flow into a clean top-down layout: blocks are positioned automatically, and existing connectors redraw over the new layout.
• Available any time, so Nimbus users can re-arrange a flow whenever they like, including right after adding or restructuring blocks.
• Disconnected blocks (with no path from START) are placed predictably; wider blocks automatically get the spacing they need.
• In the template editor, all blocks are arranged, including locked ones. Lock state only guards block configuration, not canvas position.
• The new layout is applied immediately and persists on the next Save; discarding or cancelling the edit restores the previous layout.

UI Profiles: Tailor the Portal Menu per user

Administrators can now shape the Nimbus User Portal menu to match each user's role. With the new UI Profiles, admins can define exactly which pages appear in the navigation menu and which page opens by default after login. Your Agents, Supervisors, and other roles each get a Nimbus Portal experience tailored to what they actually need.

🔎 Added with this update:

• A new UI Profiles configuration page under Admin Portal > Configuration > UI Profiles.
• Administrators can define visible menu pages per profile, set custom icons and tooltips per page, and configure a default landing page.
• UI Profiles can be assigned to individual users or in bulk via Extensions User Settings.
• Pages not included in a profile are hidden from the menu¹ but remain fully reachable via direct links, such as deep links or contextual actions elsewhere in Nimbus Portal.
  ¹💡Note: Certain options cannot be hidden despite being removed from the profile, e.g. User Preferences (Portal) & Nimbus Companion.

Export Workflows and Templates via API

Building on the existing Workflow Export/Import feature, the new Export Workflows and Templates via API allows Tenant Administrators to gain full control over how and when their workflows and workflow templates are backed up. Exports can be scheduled and automated, integrating workflow protection directly into existing IT processes on top of the export options already available in the portal.

✅Administrator action: Using the new API export functionality requires new Provisioning.Workflow.Export rights to be granted to the Nimbus App on your Tenant. Refer to Nimbus API > “Grant API Web Access Permissions” for details.

🔎 Added with this update:

• A new export API endpoint for workflows and workflow templates, usable alongside the existing portal-based export.
  • New Methods: GET Discover Workflows, POST Export Workflows
• Export scope can be set at tenant or OU level, so administrators can pull an entire tenant's workflows or just those belonging to a specific organizational unit.
• An overwrite parameter controls whether existing local files are refreshed or preserved, making it easy to keep a local archive current without duplicating or overwriting unchanged definitions.

Bulk Export for User and Service Configuration

With Bulk Export, all users in Administrator roles can export all user and service configurations within an Organization Unit, or across the whole tenant, in a single operation, giving them a fast, reliable way to capture configuration snapshots at scale, without giving up the precision of selecting specific entities when that's all that's needed.

🔎 Added with this update:

• Configuration Export 
• OU-scoped export: select an OU in the grid filter and export all users/services within it in one file. Useful for backups, reviews, or migrations.
• Whole-tenant export: clear the OU filter to export the entire tenant's user/service configuration in a single operation.
• Hand-picked export remains available as before, for exporting only specific, manually selected entities.
• Choose the output format (JSON (combined) or CSV) depending on how the export will be used downstream.

Virtual User: Simplified configuration structure

Configuring a Virtual User is now faster and more intuitive. The configuration page has been reorganized into three clear tabs — General, Behavior, and Tools and Outcomes — guiding Nimbus users step by step through setting up behavior, conversation flow, and tools, without needing to consult detailed documentation. Terminology has also been standardized throughout, making it clearer what each field actually controls.

🔎 Added with this update:

• A new tab-based layout for Virtual User configuration: General (name, description, bot/profile assignment, modalities, license), Behavior (instructions, messages, timeouts, voice & persona settings), and Tools and Outcomes (conversation flow instructions, outcomes, and extensions like Web Requests or MCP Server).
• Standardized terminology: 
  • Prompt-related fields that affect the Virtual User's behavior are consistently labeled as Instructions, clearly separated from “Description” fields for the Nimbus UI, which have no effect on the AI. This also affects related configuration entities such as Parameters.
  • Intents are now renamed to “Outcomes” (also in the “Add Virtual User” activity, to clearly correlate to the “Tools and Outcomes” fields (.
  • The previous Role field is now marked (Deprecated) to reflect that its purpose is now covered by the “General Instructions” field.
• Related KB update: Use Case - Integrating Nimbus Virtual User with external systems updated for the new UI.

Virtual User transcription support

Nimbus now supports Transcription data to be caught via Trigger Events and Flow Actions. Customer interactions with Virtual Users (GPT Realtime bot) can be used to generate a transcript of each conversational session. When the Virtual User session ends, Administrators can pick up the transcript in Power Automate for downstream workflows (e.g. CRM updates, quality assurance, providing service-case context, complaint routing, or booking).

🔎 Added with this update:

• The former Companion Service Settings have been renamed to “AI Service Settings” to better reflect the general purpose.
• Added Transcription support for Virtual Users. 💡Note that Virtual User sessions are not shown on the My Sessions page, and are meant to be delivered via Nimbus Power Automate Connector the moment the session ends, where you can route it to a CRM, ticketing system, booking process, or analytics pipeline.
• Power Automate Connector updated with the following Virtual User features:
  • Trigger Events: Added "When a Virtual User has an update” event which can react to “Transcription ready” and “Session Terminated” events.
  • Flow Actions: Added ”Get Virtual User Data" flow action which can specific Virtual User transcription or the entire session transcript.
  • ☝️Please note that the new Power Automate Connector is undergoing certification as of this release. More info on this below.
• Related KB update: Use Case - Setting Up Transcription updated to reflect both methods for Virtual User and Companion.

INC Upcoming Connector Feature Certification ⌛Pending Connector Certification: Features or partial changes on the functionality described in the following are still undergoing the Microsoft review and certification process. Changes are not yet part of the officially certified Nimbus Power Automate Connector, so your Power Automate UI may differ. Available Connector update paths INC Power Automate Connector Update Path Customer Tenant Admin Procedures Nimbus Customers can choose between following upgrade paths for the Power Automate connector:  A: Update Path B: Migration Path From the Custom Connector page, retrieve the V1 connector. Install it locally on your Tenant as a “custom connector”. When you are already using the custom connector, you need to migrate all your existing Flows to the certified connector from the Microsoft Power Automate store. Benefits: Newest connector functionality is available as soon as the custom connector is installed. Benefits: Once migrated, future connector updates are rolled out automatically. Drawbacks: Manual future Connector Migration effort. Drawbacks: Initial migration effort. Due to the Microsoft recertification process, the certified connector will get new features later. Luware Development Whenever Luware releases a Nimbus Version, the “Upcoming V1” connector can be retrieved as a Luware-hosted download.  Updates occur whenever Flow Actions / Trigger Events are updated, communicated via Latest Release Notes. The same package will be submitted to Microsoft for certification. Luware / Microsoft connector Certification Process The V1 download package is submitted to Microsoft for Store Certification. Once this approval is done, the submitted V1 connector becomes the new “certified connector" directly available in the Microsoft Store. Customers already using the certified connector get updates automatically.  Flows may need minor adjustments (e.g. to make use of new Flow Actions / Trigger Events features). 💡Note: Each update triggers a re-certification process by Microsoft and takes ~4-6 weeks.     Test Connector functionality early ✅ Whenever Whenever Nimbus team mentions new Power Automate Connector functionality on the Latest Release Notes you can download the “to be certified (V1)” connector manually. Then you need to install this upcoming (V1) connector as Custom Connector on your tenant. ☝Note that Custom-installed connectors will not update automatically. Once the functionality becomes available in the certified connector you need to perform a manual Connector Migration of your flows.     Learn how to update the Custom Connector Updating the Nimbus Custom Power Automate Connector Luware development implements changes in the upcoming Nimbus Power Automate Connector (v1) and starts a certification process with Microsoft right after every major Nimbus release. 🤔When do I need to manually update a custom connector? If the official Nimbus Release Notes mention new connector features which you would like to try out ahead of time – e.g. by adding new actions and triggers – you can perform a manual update and install the V1 connector as Custom Connector on your Tenant. Learn more… INC Power Automate Connector Update Path Customer Tenant Admin Procedures Nimbus Customers can choose between following upgrade paths for the Power Automate connector:  A: Update Path B: Migration Path From the Custom Connector page, retrieve the V1 connector. Install it locally on your Tenant as a “custom connector”. When you are already using the custom connector, you need to migrate all your existing Flows to the certified connector from the Microsoft Power Automate store. Benefits: Newest connector functionality is available as soon as the custom connector is installed. Benefits: Once migrated, future connector updates are rolled out automatically. Drawbacks: Manual future Connector Migration effort. Drawbacks: Initial migration effort. Due to the Microsoft recertification process, the certified connector will get new features later. Luware Development Whenever Luware releases a Nimbus Version, the “Upcoming V1” connector can be retrieved as a Luware-hosted download.  Updates occur whenever Flow Actions / Trigger Events are updated, communicated via Latest Release Notes. The same package will be submitted to Microsoft for certification. Luware / Microsoft connector Certification Process The V1 download package is submitted to Microsoft for Store Certification. Once this approval is done, the submitted V1 connector becomes the new “certified connector" directly available in the Microsoft Store. Customers already using the certified connector get updates automatically.  Flows may need minor adjustments (e.g. to make use of new Flow Actions / Trigger Events features). 💡Note: Each update triggers a re-certification process by Microsoft and takes ~4-6 weeks.     💡Good to know:  If you performed a Connector Migration before now use the Microsoft store-certified connector, you can skip the update steps shown below. After each V1 connector update re-certification by Microsoft, your connector updates automatically.   Manual Connector Update Steps Retrieve the latest connector file from your Nimbus cluster region: 💡 Uncertain? You can find out your region by logging into Nimbus Portal / Admin and see how the URL changes. INC Nimbus Power Automate Connector URLs Switzerland 01 https://portal.ch-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json Switzerland 02 https://portal.ch-02.luware.cloud/api/manifests/v1/PowerAutomateConnector.json Germany 01 https://portal.dewe-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json Germany 02 https://portal.dewe-02.luware.cloud/api/manifests/v1/PowerAutomateConnector.json United Kingdom 01 https://portal.ukso-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json Australia 01 https://portal.aue-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json West Europe 01 https://portal.euwe-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json East United States 01 https://portal.use-01.luware.cloud/api/manifests/v1/PowerAutomateConnector.json ☝Legacy (v0) Custom Connector users: Replace the /v1/ part of the URL above with /v0/ to download the legacy connector (e.g. to Update your existing Connector) with new files. Note that the legacy connector will not receive feature updates anymore. ☝Migration note for all custom-installed connectors: You can install the v1 to-be-certified connector as Custom Connector. However, when switching to the certified connector within Microsoft Power Automate, a Connector migration is necessary for all existing custom connectors. Go to https://make.powerautomate.com/ and expand Data > Custom Connectors. Select your Nimbus Custom Connector from the list. Click on the Context menu (three dots) at the end of the line.  Select “Update from OpenAPI file”. Click the "Import" button and select the new file. Finally click “Continue”. ⮑ The connector is now updated and should be visible on your Tenant.

Other Changes and Improvements

• Trigger Events: Added new Trigger event “When a voicemail is ready”, related to the new Voicemails transcription feature added to Modalities Service Settings. 💡Note that this Event is also part of the upcoming (to be certified) Power Automate Connector. “Voicemail Transcription” is acting independently to Virtual Users or “Companion” related event and trigger.
• Nimbus Companion Interface - Various UI improvements: 
  • Resize handle to adjust the split-view / Nimbus UI proportions
  • Added possibility to create a new chat from split view