cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

When an event is added, updated or deleted duplicate action when an event is accepted

I am using the "When an event is added, updated or deleted (V3)" trigger to send an email notification for events that live on a shared calendar.   This flow also automatically accepts the event for the calendar account when it is added (based on the ActionType condition).

 

This is working great to send an email on any new, removed, or changed event, however it is triggering when the event is added and then immediately again when the event is accepted (which fires as an "updated" trigger).   How can I differentiate this acceptance update and exclude it from the flow so that the email is only sent once on event creation?

 

Is there some variable that represents what is actually changed about the calendar item?

 

Thanks,

Greg

1 ACCEPTED SOLUTION

Accepted Solutions
Microsoft
Microsoft

Hi  gregkegel,

 

If we want to differentiate this acceptance update and exclude it, we should know what's the differences of the reponse in flow.

1. Get the body context when the event was created and updated

email event.png

2. Compare the text, we found the responseType in the  output is different

email response.png

3. Add a condition after the trigger. If you only send once on event creation, you can set a condition like below.

Condition.png

On event creation, you can add sent email action under 'If Yes'. If the event is updating, the flow skip the ations in 'If Yes' and follow the actiona in 'If no'.

View solution in original post

3 REPLIES 3
Microsoft
Microsoft

Hi  gregkegel,

 

If we want to differentiate this acceptance update and exclude it, we should know what's the differences of the reponse in flow.

1. Get the body context when the event was created and updated

email event.png

2. Compare the text, we found the responseType in the  output is different

email response.png

3. Add a condition after the trigger. If you only send once on event creation, you can set a condition like below.

Condition.png

On event creation, you can add sent email action under 'If Yes'. If the event is updating, the flow skip the ations in 'If Yes' and follow the actiona in 'If no'.

View solution in original post

Frequent Visitor

Thank you for your reply!

 

I tried this initially, but this "responseType" seems to be static after the event is accepted, meaning any future "updates" to the event will still report the responseType as "accepted".   How do I differentiate between an event that is just being updated versus an event that is updated *because* it was accepted?

Ultimately, I worked around this one by comparing the response time to the modified time.   If these were the same (or within a second away from eachother), it can be determined that the "update" is actually the response.

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Automate Super Users!

Many congratulations to the Season 1 2021 Flownaut Crew!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

MPA Community Blog

Power Automate Community Blog

Check out the community blog page where you can find valuable learning material from community and product team members!

Users online (69,842)