Good morning,
I'm working with the Office 365 Groups Mail connector.
I'm using the "When a new email arrives to a group" trigger. I'd like, then, to do actions only when the e-mail has the following conditions:
1) from a particular sender (who is not part of the group) and with attachments
2) with a particular subject ("topic" of the conversation), with a "start with" condition
3) to a specific recipient among the recipients of the e-mail (there may be many recipients).
I'm able to program the first two conditions, getting the conversation and thread post with the actions of the "When a new email arrives to a group": getting the conversation thread and getting the post.
However, I am not able to retrieve the recipients of the e-mail (usually, there are many addressees and I want to see if there is one specific that would trigger the actions) to look for the specific recipient: is it possible to get the recipients of the e-mail that's being sent to a group?
Many thanks.
Well, I'm close to it.
Once I get the conversation thread, I can use "compose" to get an array of recipients from the variable "toRecipients" of the object ConversationThread.
However, it looks like it doesn't work: the compose action is empty. Can somebody help?
You won't be able to use a group member in a trigger condition, I don't think, @cvig ... however, you will be able to use them as one of the Trigger conditions in the recipients, for sure. Should work with the contains() function, I reckon.
Best way to work it out is (and I'll do this now, too) to build the trigger condition as an actual expression in the flow. So get an example email, and build from that.
Easy building using the filter array (which I delete afterward):
Just tap on 'Edit in advanced mode'
There's my trigger.
Now ... like I say, that works if the email address is one of the addresses that have been sent to in the 'to' field.
If you wish to do a 'group' version of this, then you'd have to use your 2 existing triggers to whittle down the flow runs, then have the first action be to check against the group and terminate if it's not. That will at least save on action calls.
Hi @eliotcole , thanks for the feedback.
What I'm trying to do is to build a group version of the e-mail one (that I have easily managed in the past with trigger conditions). I'm reading the "conversation" and trying to get the "toRecipients" variable, as you see below, however the returned variable is empty, even though, also in accordance with the documentation, it should not. That's what's very strange to me.
In other words, there's no "toRecipients" (or equivalent information) in the xml structure of the threads / conversations / posts.
(this is, for example, the post's body I can get with a "compose" action)
To be even more specific, I see a discrepancy between Microsoft official documentation and what I get in the flow. May it be a bug? Or may it be due to the account plan? I'm using my business account given by my organization (Office 365 E5). Or is there some update / deployment of the platform ongoing?
This is what I get with get conversation thread (they call it "Conversation thread object"):
This is what they say I should get. But as you can see above, I don't actually get the last two variables "toRecipients" and "ccRecipients".
https://docs.microsoft.com/en-us/connectors/office365groupsmail/#conversationthread
If this is strayed from the trigger conditions, then I would take a stab at the logic, here.
Why not just retrieve the message id of one of (or all of) the email(s) and then call the email(s) and take the value from there to check the group and hence the membership there-in?
If (as my brackets inter) you wished to do this for all the emails, you could just build an array from each email in a conversation and check all groups included for the given ID.
This seems like a sound approach.
To speak purely abstractly about conversations ... and purely unrelated to what's going on here ... I wonder if, for conversation details, that address fields could be changeable over each email (or would that infer a separate conversation, I dunno) as people bring others into the chain. This might be a reason why that particular information is just an empty field, or why in some cases the value is empty since others were added to the chain, and thus it was wiped.
@eliotcole, fine, but the groups have a different logic with respect to e-mails, as said in the documentation. There's no "e-mail"; indeed there are conversations, threads, posts, even though indeed groups do receive "e-mails". So I think speculating too much about what you say doesn't lead to a conclusion.
In any case, there's a bug in the connector "Get a conversation thread" (which shall provide the "ConversationThread" object: https://powerusers.microsoft.com/t5/I-Found-A-Bug/Office-365-Groups-Mail-connector/td-p/862078
It doesn't retrieve the toRecipients and ccRecipients properties, except than with a GET HTTP call (which I tested and seems working).
Regards.
Except that if you can get the details of a group, then you can look up the group ... and if you can look up the group, you can see the members of a group.
... and if you can retrieve the members of a group, you can retrieve the emails of the members of the group.
But if the HTTP call does it, then it's all good. 👍
Thanks, however my request is not to retrieve the e-mails of the members of the group.
As I've said, I want to retrieve the recipients of an e-mail sent to a group.
Say that john doe sends an e-mail to OFFICE365GROUP@domain.com and to daffyduck@disney.com. So, daffyduck@disney.com is among the addressees / recipients of the e-mail.
I can access the e-mail because I am a member of the group (but daffyduck@disney.com and john doe are not; however, this is not an issue), that indeed in a group becomes a "post" or "conversation"; I actually want to get "duffyduck@disney.com" with a flow. This can't be done due to a bug of the connector. That's the story.
Regards.
Hello,
did you solve the problem with getting the address from ccRecipients?
Hello,
I haven't solved the problem yet. At the time of the above posts I've even tried with my company's IT support using the HTTP requests, but we've found the same issue: those two arguments were not passed by the engine, so we couldn't retrieve them in any way.
Honestly, I haven't tested the above routines more recently to discover if, in case, Microsoft has done some debugging and updating... did you?
Best regards!
Hey cvig,
I have been having the same issues and was able to get the "toRecipients" by following the below steps:
Trigger: "When a new email arrives to a group" (Connector: Office 365 Groups Mail)
Action: Send an HTTP request (Connector: Office 365 groups not the Office 365 groups email
- URI: https://graph.microsoft.com/v1.0//groups/{group-id}/threads/{thread-id}?$select=toRecipients
Note Remember to replace {group-id} and {thread-id}
using this specific HTTP trigger i was able to get the "toRecipients". The query in the abobe URL/URI should be adjusted to ccRecipients
Dear Community Members, We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd. During this period, members will not be able to Kudo, Comment, or Reply to any posts. On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities. What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!
We are excited to announce the Summer of Solutions Challenge! This challenge is kicking off on Monday, June 17th and will run for (4) weeks. The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities. Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”) - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024 Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods. You must enter into each weekly Entry Period separately. How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different. Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers. At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing. Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner. A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random. Individuals will be contacted before the announcement with the opportunity to claim or deny the prize. Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners. Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event. ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE** Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24 17 @Anil_g 7 @ManishSolanki 13 @eetuRobo 5 @David_MA 10 @VishnuReddy1997 5 @SpongYe 9JhonatanOB19932 (tie) @Nived_Nambiar 8 @maltie 2 (tie) @PA-Noob 2 (tie) @LukeMcG 2 (tie) @tgut03 2 (tie) Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate @Deenuji 12@ManishSolanki 19 @Anil_g 10 @NathanAlvares24 17 @VishnuReddy1997 6 @Expiscornovus 10 @Tjan 5 @Nived_Nambiar 10 @eetuRobo 3 @SudeepGhatakNZ 8 Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22 Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 4:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2 Anil_g2 SharonS2
On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners. The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights. Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.
We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for. We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer. Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together. Here's to new beginnings and endless possibilities! If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport. To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages