Legacy and Certified Connector Differences

Learn the difference between v0 (current) and v1 (certified) connector

The Nimbus Power Automate Connector has multiple variants. On this page we highlight the differences and in which case you should opt for a specific version.

Connector Type Audience File Path Notes

Custom Connector

(v0, to be phased-out)

Customers that set up flows before 31 Jan 2024

OR

Customers that want to remain on existing features and want to delay the migration.

/v0/PowerAutomateConnector.json

  • The Custom Connector was our existing way of providing functionality in Nimbus. It will receive bugfixes, but no new functionality.
  • Documentation on the connector will only provided in this Knowledge Base
  • Updates have to be done manually as described in Power Automate Connector Introduction → Installation chapters.

💡When to use: 

  • If you are already using the Custom Connector, continue to use the v0 version until we can offer the Certified Connector
  • If you are just starting with the flow Connector, use the Certified Connector below.

☝ A changeover to the officially Certified Connector requires a manual migration of your flows.

To be Certified Connector Pack (v1)

OR

New Custom Connector (v1)

Customers that need latest development features in PowerAutomate and don't want/can't wait for the Certified Connector

Certification Package

/custom-connector.zip

/v1/custom-connector.zip

Single Json

/PowerAutomateConnector.json

/v1/PowerAutomateConnector.json

  • This new connector is our upcoming to be certified version.
  • Documentation will not be available on the Microsoft store yet until certified.

💡 When to use:

  • Use this when you want to test upcoming preview functionality, which is not available on the Certified Connector yet.
  • We recommend not to use this connector for productive flows as last-minute (breaking) changes could occur.
  • Install the to be Certified Connector as a Custom Connector → See Power Automate Connector Introduction → Installation

☝ A changeover to the officially Certified Connector requires a manual migration of your flows.

Certified Connector Pack (v1)

Customers that set up flows after 31 Jan 2024

 

Customers that want to upgrade to certified features and can migrate from the Custom Connector as early as possible.

/certified-connector.zip 

/v1/certified-connector.zip

  • The Certified Connector will new way of providing a Nimbus Power Automate integration.
  • Documentation will be provided directly in the connector itself and hosted by Microsoft alongside with each new update.
  • The connector will be directly available from the Microsoft store can be integrated and updated more easily.

💡When to use: 

☝ Do not install the the Certified Connector as Custom Connector. Use the Certified Connector directly from the Microsoft store for all productive use cases. 

Comparison of different Nimbus Power Automate connectors and when to use them

🤔 What is the meaning of the different file paths?

Refer to these URLs below and replace the last part of the path to retrieve the corresponding connector

Nimbus Power Automate Connector URLs

Switzerland 01 https://portal.luware.cloud/api/manifests/v0/PowerAutomateConnector.json
Germany 01 https://portal.dewe-01.luware.cloud/api/manifests/v0/PowerAutomateConnector.json
Germany 02 https://portal.dewe-02.luware.cloud/api/manifests/v0/PowerAutomateConnector.json
UK 01 https://portal.ukso-01.luware.cloud/api/manifests/v0/PowerAutomateConnector.json
Nimbus Power Automate Connector URLs

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

🤔 What are the technical differences between the Custom and Certified Connector?

Naming of Flow Actions, Trigger Events and related System Fields and Parameters will vary between the connectors. This is also done to provide more future flexibility as Nimbus provides more means of Task Distribution and supported modalities. 

 🤔Can I switch my existing flows to a different connector?

Unfortunately, existing flows that don't use the Certified Connector yet need to be manually migrated. This is due to how connectors are authenticated on your Tenant, each using their own actions and triggers with changed data structure. We are looking into ways to make a migration as seamless as possible, but manual effort (and testing) of existing flows cannot be avoided. 

 🤔 What if I can't switch from the Custom Connector yet?

Your "old" Custom Connectors will continue running, but will not receive new feature updates, just essential bugfixes and improvements. We will communicate reliances and future update paths via our Release Notes and with advance communication via our Customer Success team. 

Detail Comparison

Trigger Events

The new certified connector will feature clearer namings. Trigger Events will therefore be easier.

Version v0 Version v1

You can either use 

GetOnNewTasks- when a new Nimbus task is created in the system.  

 

GetOnUpdatedTask – when a task has been updated. You need to use this  

When the task has been routed into a sub service. 

Use sesion event=AcceptedBySystem for all new tasks in an underlying service

 

A screenshot of a computer
                                Description automatically generated

 
 
 
 

When a task changes state – New or old tasks, use this trigger whenever a task changes state (new in the system, has been routed into a sub service, parameter updated, all other workflow events that can occur) 

 

 

 

 

 

A screenshot of a computer
                                Description automatically generated

Comparison of legacy (v0) and certified (v1) connector

Trigger Outputs

Trigger Outputs (json format) will change in their format. Below is an example:

  • Red= removed in v1
  • Green= added in v1 – All fields are always available in the outputs for v1, even if the content is null. The field “Customer” is omitted in v0 when its content is null.
  • Yellow=Renamed in v1 (Name and/or values)
Version v0 Version v1

{

    "headers": {

        "Host": "",

        "Content-Type": "application/json; charset=utf-8"

    },

    "body": {

        "RequestId": "63e4874e-6f75-4b70-b6c8-c3cb8bebad8f",

 

        "Id": "9f1f6000-60c5-494b-a911-ecc93656313b",

        "CallChainId": "5abdff94-3363-4e81-8b9d-1d90d6e0333e",

 

        "Event": "AcceptedBySystem",

        "Type": "Incoming",

        "Modality": "Audio",

 

        "CustomerIdentifier": "+41584042840",

        "CallerTelNumber": "+41584042840",

        "MicrosoftCallerId": "+41584042840",

        "IsAnonymous": false,

 

 

        "Created": "2023-12-07T09:40:41.5554626Z",

        "Terminated": "2023-12-07T09:40:42.9044671Z",

 

 

        "TeamId": "e3d815c4-cd71-4786-a348-59283215e23e",

        "TeamName": "Contact Center Bank",

        "ServiceDisplayName": "Contact Center Bank",

        "ServiceUPN": "Contact.Center.bank@lunifico.com",

 

        "CustomContextParameters": {

            "ID11": "",

            "Message": ""

        },

        "PreferredUsers": []

    }

}

 

{

    "headers": {

        "Host": "",

        "Content-Type": "application/json; charset=utf-8"

    },

    "body": {

        "TenantId": "00000000-0000-0000-0000-000000000000",

 

        "TaskId": "9f1f6000-60c5-494b-a911-ecc93656313b",

        "CallChainId": "5abdff94-3363-4e81-8b9d-1d90d6e0333e",

 

        "Event": "SystemAccepted",

        "Direction": "Inbound",

        "Modality": "Audio",

 

        "CustomerIdentifier": "+41584042840",

        "CallerTelNumber": "+41584042840",

        "MicrosoftCallerId": "+41584042840",

        "IsAnonymous": false,

 

 

        "Created": "2023-12-07T09:40:41.5554626Z",

        "Terminated": "2023-12-07T09:40:42.9044671Z",

 

 

        "ServiceId": "e3d815c4-cd71-4786-a348-59283215e23e",

        "ServiceName": "Contact Center Bank",

        "ServiceDisplayName": "Contact Center Bank",

        "ServiceUPN": "Contact.Center.bank@lunifico.com",

 

        "TaskInformation": {

            "Customer": null,

            "CustomContextParameters": [

                {

                    "Name": "ID11",

                    "Value": ""

                },

                {

                    "Name": "Message",

                    "Value": ""

                }

            ],

            "PreferredUsers": []

        }

    }

}

 

Disruptive changes

Note that the JSON format changes will inherently require your existing legacy flows to be edited, as mappings to Flow variables and similar references will not work.

 

Mapping of Trigger Events

More details on how workflows interact with flow can be found on the Trigger Events page.

 
Version v0 - Session Events Version v1 - Task Events
Created Workflow Started
AcceptedBySystem System Accepted
Queued In Queue
Connected To User Connected To User
Queue Left Queue Left
Parameter Updated Parameter Updated
Outbound Connected To Destination Destination Reached
A screenshot of a computer
                        Description automatically generated

A screenshot of a computer
                        Description automatically generated

Working with CustomContextParameters

This chapter describes how your own Custom Parameters and System Fields and Parameters are handled.

Trigger outputs for CustomContextParameters

Version v0

Version v1

Values can either be null or strings

 

        "CustomContextParameters": {

            "Parameter1": null,

            "Url": "https://www.crm.com/userid=12345",

            "QueuePosition": "3",

            "TicketNumber": "Case-1234",

            "Message": ""

        }

 

Values can either be null or strings

 

 "CustomContextParameters": [

    {

      "Name": "Parameter1",

      "Value": null

    },

    {

      "Name": "Url",

      "Value": "https://www.crm.com/userid=12345"

    },

    {

      "Name": "QueuePosition",

      "Value": "3"

    },

    {

      "Name": "TicketNumber",

      "Value": " Case-1234"

    },

    {

      "Name": "Message",

      "Value": ""

    },

]

 

Store the whole CustomContextParameters container in a variable

Version v0 – Initialize variable Version v1 – Initialize variable

Type=Object

Value= triggerOutputs()?['body/customContextParameters']

 

Type=Array

Value = triggerOutputs()?['body/taskInformation/customContextParameters']

Get a custom context parameter value by name 

Version v0 Version v1

Get it directly from within the path

 

Type=String

Value=triggerOutputs()?['body/customContextParameters/TicketNumber']

 

 

 

 

First, filter the array for the parameter to get the value from

 

From = triggerOutputs()?['body/taskInformation/customContextParameters']

Then select the value from the filtered array

Type=String

Value= first(body('Filter_array'))?['Value']

Update the Nimbus Task with a new CustomContextParameter

This is the same in both versions. The only difference is the reference to the Nimbus task which was RequestId in version v0 and now is Task ID in version v1.

Version v0

Version v1

 

 

Add a new value to the CustomContextParameter collection and update the Nimbus task

Version v0 Version v1

Call the trigger GetOnUpdatedTasks

Store the existing custom context parameter values in variable of type Array

 

The use “Append to array variable” to append new values to the custom context parameters

 

 

When updating the Nimbus Task with Update Task, add the variable as a whole to the field CustomContextParameters

 

Call trigger “When a task changes state”

Store the existing custom context parameter values in variable of type Array

 

 

The use “Append to array variable” to append new values to the custom context parameters

 

 

When updating the Nimbus Task with Update Task, add the variable as a whole to the field CustomContextParameters

 

 

Table of Contents