Hi Anshuman Prusty , I know we had discussed this previously when we worked on Automation Rules together. Since our discussions, we have found that the use of this Automation Rule Trigger works in this case where a user becomes a group member by role

 EffectiveGroupMember.AfterCreate Automation Event 

 EffectiveGroupMember.AfterUpdate Automation Event  

 EffectiveGroupMember.AfterDelete Automation Event   

Hope this helps!

Thanks John Reynolds for your input.

We used the API event "EffectiveGroupMember.AfterCreate" in the script and are able to get the Group info. However when tried to set email digest for that group setting frequency to "weekly", it is coming as "Not Subscribed".

We are using the below code:

var emailDigestSubscriptionResponse = core_v2_emailDigest.Create("group", 12, 7);

And emailDigestSubscriptionResponse is null. Any thoughts.

who are you running the automation as? core_v2_emailDigest.Create(); will subscribe the accessing user.  

Hi Brian Dooley , We are running the automation script by checking/unchecking the "Execute as the service account" in automation overview page. In both the cases getting "Thomson Reuters Community" as accessing user.

Yes, this i because the event "EffectiveGroupMember.AfterCreate" is triggered via a job, so it would be the service account triggering the automation.  You'll need to run the section creating the email digest in a separate file called by core_v2_Widget.ExecuteFile.  This will allow you to specify the RunAsUserName so you can run as the user who should be subscribed.

Thanks Brian Dooley  we are able to set the frequency to weekly for the email digests using core_v2_Widget.ExecuteFile.

Thanks Brian Dooley  we are able to set the frequency to weekly for the email digests using core_v2_Widget.ExecuteFile.