Preparation in Nimbus

✅ We need to create some variables in Nimbus first.

1. In Nimbus, we need to go to Configuration > Parameters and create a Custom Parameter to store the Contact ID of the Microsoft Dynamics contact:
   
2. Still within Nimbus Configuration, go to Conversation Context and create a Context item with the URL to Microsoft Dynamics.
   1. Set the URL using the Custom Parameter we just created: "DynamicsContactId" that will hold the contact ID. This will eventually form your final URL to your Dynamics instance.
   2. In this example: https://orgcxxxx.crm4.dynamics.com/main.aspx?appid=d87604e4-bce3-ec11-bb3d-0022487fcfaa&pagetype=entityrecord&etn=contact&id=$(CustomContextParameters.DynamicsContactId)
      
3. Make this Conversation Context available in your Nimbus via Services Overview > Service Settings > "Extensions" Tab.
   

Create Your Flow

✅ Preconditions:

• In Power Automate, ensure you work in the correct environment. You can select it accordingly next to your Account information.

Where to switch the environment in Power Automate	Where to find the environment name in Microsoft Dynamics 365

💡 This is necessary to be able to work with the right tables when using the Microsoft Dataverse Connector. 

Now it's time to create a new flow:

1. Head to "My Flows"
2. Click on "+ New Flow" and create a blank "Automated Cloud Flow"
3. Give your new flow a speaking name, e.g. "Dynamics Caller Lookup"
4. In the text box underneath, search for “Nimbus” and choose the "When a task changes state" trigger
5. Click the "Create" button
6. Select the “When a task changes state” Trigger Event.
7. In the “Services Item” dropdown select the Nimbus service's UPN. 
   💡 You can also get the data of multiple services at this point, but for the sake of simplicity we keep it to one service in this example.
8. In the “Task Events” dropdown select “System Accepted”.
9. In the “Advanced parameters” dropdown enable “Modalities” and "Directions".
10. In the “Modalities Item” dropdown select “Audio”.
11. In the “Directions Item” dropdown select “Inbound”.

Get Microsoft Dynamics Contacts

✅ We want to search for the caller in the Microsoft Dynamics contacts.

1. In the editing area click to add a new action.
2. Search for "dataverse list rows" and select “List rows” under the “Microsoft Dataverse” section.
3. Configure the action as follows:

Field	Value to fill in / 🌟 = Nimbus dynamic content
Table Name	🌟 ID of last connected user
Filter Rows	mobilephone eq '@{triggerOutputs()?['body/microsoftCallerId']}' (in our example we want to filter on the MobilePhone column in Dynamics. In Nimbus the phone number parameter is stored under “Microsoft Caller ID”)
Row Count	1 (as we we only want to get the first results)

Update the Nimbus Task

We're assuming that your previous data retrieval step was successful. Now it's time to let Nimbus know about it so the caller info is also shown in the UI and the Dynamics Contact Id will be set in Nimbus using Flow Action “Update Task” .

1. In the editing area click to add a new action.
2. Search for "Nimbus" and select “Update Task” under the “Luware Nimbus” section.
3. Configure the action as follows:

Field	Value to fill in / 🌟 = Nimbus dynamic content / 🌟🌟= List rows dynamic content
Task ID	🌟 Task ID
Customer First Name	🌟🌟First Name
Customer Last Name	🌟🌟Last Name
Customer Display Name	🌟🌟Full Name
Customer Company	🌟🌟Company Name (value)
Customer Job Title	🌟🌟Job Title
Customer Department	🌟🌟Department
Custom Context Parameters	Click on to and add [ { "name": "DynamicsContactId", "value": @{items('For_each')?['contactid']} } ]