Trigger Events

During an active call session Nimbus will send trigger events according to the steps configured in the respective service Workflow. These events are available for selection within the Microsoft Power Automate Connector and described in the following.

Relation between call events, power automate triggers and workflow activities:

Session Event	Related Trigger Event	Description	Related Workflow Activities
Calling	*GetOnNewTasks*	Trigger during incoming call in a Service Line.	None, right after "Start"
Accepted by System	*GetOnUpdatedTasks*	Trigger when incoming call was accepted by the service.	"Accept Conversation"
Parameter Updated	*GetOnUpdatedTasks*	Trigger after a " Collect Information" Workflow Activity exit.	"Collect Information" Use "Check Parameter" - as recommended follow-up, e.g. when manipulating the parameter with external systems
Queued	*GetOnUpdatedTasks*	Trigger when the call was put into the queue.	"Queue"
Connected to User	*GetOnUpdatedTasks*	Trigger when the call was connected to a user.	As part of "Enqueue"
Queue Left	*GetOnUpdatedTasks*	Trigger once the call leaving the queue (Leave queue without getting connected to an user).	None, right after "Enqueue"
Terminated	*GetOnUpdatedTasks*	Trigger once the call is terminated.	"Disconnect Conversation"

Related concepts

Each event can update Context - Fields and Parameters which are available as data fields within the Nimbus Microsoft Power Automate Connector.
You can follow up these events with Flow Actions to update entries in Address Books.

Example Workflow with Trigger Events shown:

Related example Use Cases

Here are some example use cases that showcase the use of trigger events:

Name and Goal of the Use Case	_UCID
Use Case - Managing Caller Data in Sharepoint Lists	_{UC NIMB 002}
Use Case - Storing external CRM data in custom parameters	_{UC NIMB 008}
Use Case - Retrieving called Agent information from O365	_{UC NIMB 009}
Use Case - Caller Information from Graph	_{UC NIMB 010}
Use Case - Adding external Address Books via Power Automate	_{UC NIMB 013}
Use Case - Looking up phone numbers via Search.ch API	_{UC NIMB 014}
Use Case - Creating a callback task for missed calls in Salesforce	_{UC NIMB 018}
Use Case - Connecting to Azure Table Storage inside a flow	_{UC NIMB 019}
Use Case - Updating a task for a known Contact in Salesforce	_{UC NIMB 020}
Use Case - Creating and opening a Salesforce-Task as Agent accepts a call	_{UC NIMB 021}
Use Case - Waiting for a parameter to be updated via Power Automate	_{UC NIMB 022}
Use Case - Forwarding Voicemails received in Nimbus to Email	_{UC NIMB 023}
Use Case - Working with Blacklists or Whitelists in Nimbus	_{UC NIMB 024}
Use Case - Creating an incident task in ServiceNow	_{UC NIMB 025}
Use Case - Creating a ServiceNow ticket based on user input	_{UC NIMB 027}
Use Case - Looking up a caller to open Dynamics 365 contact context	_{UC NIMB 029}
Use Case - Creating a callback task in Dynamics 365	_{UC NIMB 031}
Use Case - Connecting to OData via Postman	_{UC NIMB 032}
Use Case - Creating a custom settings page for a workflow	_{UC NIMB 033}
Use Case - Looking up caller information in HubSpot	_{UC NIMB 035}
Use Case - Looking up caller information from Zendesk	_{UC NIMB 036}
Use Case - Creating an IVR Ticket Service with Zendesk	_{UC NIMB 037}
Use Case - Creating a dynamic emergency message routing scenario	_{UC NIMB 038}
Use Case - Adding Custom Data to Luware Power BI Reports	_{UC NIMB 039}
Use Case - Planning After Call Work with Teams, Office and Nimbus	_{UC NIMB 040}
Use Case - Posting interactive custom adaptive cards to agents	_{UC NIMB 042}
Use Case - Transferring calls to an on-call agent from an excel list	_{UC NIMB 043}
Use Case - Extending the standard Power BI Report with IVR Choices	_{UC NIMB 044}
Use Case - Collecting data from customers in an automated IVR without agents	_{UC NIMB 045}
Use Case - Integrating a customer satisfaction survey with Nimbus	_{UC NIMB 046}
Use Case - Creating Tasks in Planner for all Nimbus Service Calls	_{UC NIMB 047}
Use Case - Building a properties management customer service with Nimbus, Teams and HubSpot	_{UC NIMB 051}
Use Case - Merging MS Teams usage reports into the Nimbus reporting template	_{UC NIMB 052}
Use Case - Building a Priority Service in Enterprise Routing	_{UC NIMB 053}