Nimbus can integrate with many systems in many ways. It is crucial to understand that Nimbus provides the following integration endpoints:

Nimbus Integration Endpoints

Power Automate Triggers

• You can listen to events from Nimbus and react to these.
• You can create tasks in Nimbus using the Power Automate Connector.
• You can get and set data of the Nimbus task object. For instance add a URL to it which will be used for the conversation context described in this list.

🔍 See Nimbus Power Automate Connector, Trigger Events, and Power Automate Use Cases.

Conversation Context

• You can pop a web page on an incoming service call.
• You can also integrate the web page in the Services Overview dashboard.

🔍 See Conversation Context.

Nimbus Embedded Web App

• You can show a web page on a dashboard.

OData API

• You can get the Nimbus reporting data from the OData API using your Nimbus user.

Nimbus Assistant web hooks

• With so called service or direct call templates, you can configure and execute web hooks using data from Nimbus.

🔍 See Service Call Templates and Direct Call Templates.

Nimbus Assistant app hooks

• With so called service or direct call templates, you can run applications on the local machine using data from Nimbus.

🔍 See Service Call Templates and Direct Call Templates.

FAQ

🤔 Can the call be signaled via a widget in a third-party system?
Yes. Luware does not offer its own widget. It is possible to query call events via Power Automate and then trigger the corresponding APIs of a third-party application. 

🤔 Can I make calls from the third-party system?
Yes. The call can be started directly in Nimbus using a click to call link

🤔 Can the call be accepted in the third-party system?
No. Calls must be answered via MS Teams. It always rings in MS Teams

🤔 Can I forward the status from my third-party system to Nimbus?
No. Nimbus works with the Teams status and some Nimbus-internal statuses