Which trigger should I use?

[MelBoyer]

Hello,

I've set up a Microsoft Form to collect essential details from travelers planning to visit foreign destinations. These details include their intended destinations, departure and return dates, as well as their email addresses. With this information, we're orchestrating a series of actions (calendar event, email notification, etc). Moreover, we aim to add the traveler to a dedicated Azure travel group to ensure they have network access throughout their journey the day before their travel (flow needs to go through an approval) and a removal upon their return.

Now, I'm looking for the most efficient way to trigger these Azure actions, rather than having to monitor a SharePoint list every day, which would equate to 365 checks a year. It's worth noting that our travelers' trips can span 2 to 3 weeks, which rules out using the "when an upcoming event is starting soon" trigger due to its 7-day limit. Does anyone have any suggestions for a better trigger mechanism that would streamline this process? Your insights would be greatly appreciated!

[SudeepGhatakNZ]

@MelBoyer ,

There are several ways to achieve this.

One way is to have multiple child flows each with one specific task (such as Adding user to group, etc)

You can then build a flow that triggers on "When a Microsoft form is submitted" event and it calls all the relevant child flows on demand.

[MelBoyer]

I apologize if my previous message was not entirely clear. Allow me to provide further clarification. Currently, I have a workflow set up with the trigger "When a Microsoft Form is submitted" to handle tasks such as calendar events and email notifications.

However, I have a specific concern related to adding travelers to the Azure group. This particular task may experience a slight delay, possibly taking a few days or hours to complete. Ideally, it should execute on the day just before the traveler's departure, even if the form was submitted a week in advance.

Conversely, the task for removing travelers from the Azure group should be scheduled for the day following their return date. This ensures that access to the network is appropriately maintained throughout the travel period.

[barret]

You could potentially put in a Delay action in the flow. This action lets you Delay a flow until a specific timestamp. Just tell it the timestamp you want the rest of the flow to kick off and it will hold until then. There are limits, I believe, on how long it can delay, but I don't know what that is off the top of my head.