Using the Nimbus Nimbus Power Automate Connector, you can retrieve caller data to fill into a call list for your team. This can be useful for your team to coordinate callbacks and other actions on missed calls.
PRECONDITIONS
- At least one productive Nimbus team must be in place so you can configure the necessary parts and retrieve team data for this use case.
- You must be the Nimbus team owner, as you need access to the team's Flow connector retrieve team data with your credentials / access permissions.
- You need a "Power Automate for Office 365" License on the same team owner account that will create / manage flows for your team.
- SharePoint must be connected to your service team in order to create a new tab with shared data.
How-To: List of Missed Calls with Callback Coordination
Create a new list as tab in your team
Within teams, locate your Nimbus service team and perform the following steps to create a new list:
- Click on "Add a Tab"
- Search for and select "Lists"
- Click in "Create a new List"
- Select "Blank List"
- Give the list a name (which will also appear as your tab title)
Prepare your List
Now it's time to prepare your list to hold the necessary data. In this example we add the following columns:
| Column* | Type | Purpose | Update via Flow |
|---|---|---|---|
| Date / Time of Call |
Date and time Include time: Yes |
Will be filled automatically by the flow at the point of call. | ✅ Yes |
| Number called | Single line of text | Stores the number of the caller | ✅ Yes |
| Caller name | Single line of text | Stores the name of the caller | ✅ Yes |
| Has been answered |
Yes/No Default: No |
Acts as the default for missed call entries in your list. Will be set "Yes" if a call was answered. |
✅ Yes |
| Answered by |
Person or Group Show profile photo: Yes |
Will be filled by the flow to automatically provide user details | ✅ Yes |
| Has been called back | Choice |
Manually filled by your team. 💡 You can have any selection, e.g. (Yes, No, Tried to call) |
❌ Done manually |
| Who called back |
Person or Group Show profile photo: Yes |
❌ Done manually | |
| Call_ID | Single line of text |
☝ Important for reference in the Flow so the correct line is filled. You can hide this column later. |
✅ Yes |
| Title | Default | Default by the list design. You can hide this column later. | ✅ Yes |
*This is just an example, column names are completely your choice.
Create new flows
Now it's time to update your list with a new Flow which is triggered during an incoming Nimbus call.
- Visit the Flow landing page: https://emea.flow.microsoft.com
- Head to "My Flows"
- Click on "+ New Flow" and create a blank "Automated Cloud Flow"
- Give your new flow a speaking name, e.g. "Create new List Entry"
- Do not select a trigger, instead select “ Skip ”
- Continue in the next step.
Remember this procedure and refer back to it later. We will describe multiple flows to be created separately below.
Flow A: Create new entries with caller data
✅ Note: This step is directly continued from step 4. Within the same flow we create the connection between your SharePoint list and the Nimbus connector.
- In the "Search for Connectors" enter "Nimbus" → You should now see multiple results
- Select " GetOnNewTasks "
You might be required to authenticate with the connector. Use the credentials of the user that is the owner of the Nimbus team(s) of which you are accessing data off.
- In the connector dropdown you can select any Nimbus service you are a part of.
💡 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. - Below your Nimbus "GetOnNewTasks" connector, add a new step.
- Search for "SharePoint"
- Select “Create Item”
- Configure the SharePoint Item as follows:
| Field | Value to fill in / 🌟 = Nimbus dynamic content | |
|---|---|---|
| Site Address | The Service you want to retrieve data from |
|
| List Name | The list / tab created previously in → Step 1 | |
| Title | Required, but will be hidden later - use "🌟 Id" to fill with a unique value. | |
| Date / Time of Call | 🌟 Created | |
| Number called | 🌟 MicrosoftCallerId | |
| Caller Name | 🌟 Customer.Displayname | |
| Has been answered | No | |
| Call_ID | 🌟 Id | |
| All other fields | <leave empty, as is> |
8. Lastly, give your new Flow a clear name, e.g. "Nimbus Caller create list entry"
Flow B: Add employee data to existing entries
✅ Now we'll create a separate flow with a connector to add employee data and update your existing entries. For that we connect to a O365 User Directory (AD) and fill in the employee data in to our existing entries, identified with "Call_ID".
- Create a new flow (same as → Step 4) but enter a new name for it like "Add employee info to list",.
- In the "Search for Connectors" enter "Nimbus" → You should now see multiple results
- This time, select " GetOnUpdatedTasks "
- In the connector dropdown select:
- the same Nimbus service you used previosuly on "GetOnNewTasks"
- SessionEvent: Item: "Connected to User"
🔍 Learn more about Trigger Events
- Below your Nimbus " GetOnUpdated " connector, add a new step.
- Select the "Get user profile" for O365 users (V2) action
- Configure the O365/Azure Directory action as follows:
Field |
Fill in / 🌟 = Nimbus dynamic content |
|---|---|
| User UPN | 🌟 LastConnectedUserId |
8. Add a SharePoint " Get Items " step to your flow.
9. Configure the Step as follows:
| Field | Fill in / 🌟 = Nimbus dynamic content | |
|---|---|---|
| Site Address | The Service you want to retrieve data from |  |
| List Name | The list / tab created previously in → see Step 1 | |
| Filter query | Uses the Column to hold your Caller ID, in this case: Use the dynamic content 🌟 Id ☝ Note that the dynamic Id needs to be put in single quotation marks e.g. 'Id' or the formula will throw an expression error. |
|
| All other fields | <leave empty, as is> | |
💡 When done we recommend to rename the step to something more speaking like "Get SharePoint List Entry for the call" to signal when this trigger occurs.
☝ Be aware that SharePoint will limit searches via the Get Items action to only the first 5,000 entries by default. You can enable searching additional entries by going to the settings of the Get Items action and enabling Pagination.
10. Below your SharePoint " Get Items " add a new step.
11. Select the SharePoint "Update Item" action.
12. Configure the action as follows:
| Field | Fill in / 🌟 SharePoint or 🌟 O365 dynamic content | |
|---|---|---|
| Site Address | The Service you want to retrieve data from | 
|
| List Name | The list / tab created previously in → see Step 1 | |
| ID |
The SharePoint 🌟 ID of the list item.
→ Selecting the ID will wrap the step into an "Apply to Each" loop. You can leave this and move on. |
|
| Title | 🌟 Title | |
| Has been answered | Select "Yes" 💡 Don't forget to fill the next "Answered by Claims" entry with the user that answered. |
|
| Answered by Claims | → Select Custom Value, then pick 🌟 "User Principal name" from the previous "Get User Profile" step. |
|
| Call_ID | 🌟 ID | |
| All other fields | <leave empty, as is> | |
Check and adjust your output
✅ Now everything should be set up as required. You can test your flow by making a call to your service (e.g. via the Service Settings > Test Call).
Optionally we recommend the following tweaks:
- Hide unneeded columns from view such as "Title" or "Call_ID"
- Add conditional formatting to your list to make unanswered calls clearly visible
- Adjust the sorting of entries by Date / Time to make new calls appear on top