In this use case, we're going to show how you can create your own (additional) Trigger Events in a Nimbus workflow. By doing so you get more opportunities to manipulate or save data via the Nimbus Power Automate Connector in your flows, e.g. to do storage operations in the background before Nimbus clears all data objects after a Workflow has concluded. The main trick explained in this use case is to use the Conversation Handling > Save to Parameter activity.
Show Icon Legend
|💡 = A hint to signal learnings, improvements or useful information in context.
|🔍 = Info points out essential notes or related page in context.
|☝ = Notifies you about fallacies and tricky parts that help avoid problems.
|🤔 = Asks and answers common questions and troubleshooting points.
|❌ = Warns you of actions with irreversible / data-destructive consequence.
|✅ = Intructs you to perform a certain (prerequired) action to complete a related step.
Prepare in Nimbus
Create two parameters as follows:Create two parameters. One is having a "NotSet" default value which we're going to overwrite during the workflow.
💡 These paramaters act as "Trigger name" examples. You can of course change the names to something that implies the intent or position in your workflows, e.g. "BeforeDisconnect" or "AfterAnnouncement".
- With your parameter(s) ready, go to the workflow editor, open or create a workflow, and locate the place, where you want your custom parameter "triggers" to be called.
Add two "Save to Parameter" activities to that location.
- The first "Save to Parameter" will save the value of the trigger for post processing in Power Automate
- The value can be in json format to store more than one string.
- The second "Save to Parameter" will store the trigger name, overriding it's default.
Two "Save to Parameter" activites for storing name and value
Create the Power Automate Flow
In Power Automate, you can catch your new trigger called "MyCustomTriggerName" by using the trigger GetOnUpdatedTasks with the event Parameter Updated event.
|Start the flow with the GetOnUpdatedTasks from the Nimbus Connector and select the event Parameter Updated.
Then add a Condition element to the flow where you verify if you get the custom trigger.
Set the fields to the following:
In the YES branch add a Compose element with
Use the Generate from sample button to generate the schema with the data set in the workflow.
✅ Now you are ready to implement the rest of your flow under the YES branch.
You can use the Parse JSON object which holds the CustomTriggerValue values for further processing.