Answers.Body: <p>As a workaround could you create a smart group for everyone added to the group (not pending) and use that for your CiviRule?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-18T02:45:51.530Z
Answers.Text: Smart Groups don't work with CiviRules, sadly
Answers.UserDisplayName: Jon G - Megaphone Tech
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-17T21:45:57.240Z
Answers.LastActivityDate: 2020-09-17T21:45:57.240Z
Answers.UserDisplayName: Parvez Saleh
Answers.Body: <p>You should add a <em>Field Value Comparison</em> condition.  This lets you only fire the rule if a field has a certain value.</p>
  <p>For <em>Condition Parameters</em> set the following values:</p>
  <p><em>Entity</em>: <strong>GroupContact</strong><br />
  <em>Field</em>: <strong>Group Contact Status</strong><br />
  <em>Operator</em>: <strong>is equal to</strong><br />
  <em>Compare value</em>:<strong>Added</strong></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-23T08:04:02.123Z
Answers.Text: This was the perfect solution, I wasn't aware of the Field Value Comparison condition. Many thanks, Jon!
Answers.UserDisplayName: charitycase
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-09-18T02:52:10.980Z
Answers.LastActivityDate: 2020-09-18T02:52:10.980Z
Answers.UserDisplayName: Jon G - Megaphone Tech
Body: <p>I'm using Civirules to assign tags to members who add themselves to a group via public webform using the Linked Trigger 'Contact is added to group,' but the group requires double opt-in. Civirules doesn't seem to differentiate between group status types, so the tag is immediately applied to all 'pending' members even before the member has confirmed via the link in their email. Is there a way for Civirules to recognize the difference between 'pending' and 'added,' and only apply an action when one's group status is 'added'?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-09-17T20:12:52.120Z
Comments.Text: Could you use a CiviRule based on them having fired through the opt-in - not sure how that is recorded. inbound email? or does it only get recorded by changing Group member status
Comments.UserDisplayName: petednz - fuzion
Tags: <groups><civirules><tags><pending>
Title: Can Civirules differentiate between 'pending' and 'added' group status?
ThreadText: # Can Civirules differentiate between 'pending' and 'added' group status?
  
  (Asked by: username_0 on 2020-09-17)
  
  I'm using Civirules to assign tags to members who add themselves to a group via public webform using the Linked Trigger 'Contact is added to group,' but the group requires double opt-in. Civirules doesn't seem to differentiate between group status types, so the tag is immediately applied to all 'pending' members even before the member has confirmed via the link in their email. Is there a way for Civirules to recognize the difference between 'pending' and 'added,' and only apply an action when one's group status is 'added'?
  
  **Tags:** groups, civirules, tags, pending
  
  > **Comments:**
  > **username_1**: Could you use a CiviRule based on them having fired through the opt-in - not sure how that is recorded. inbound email? or does it only get recorded by changing Group member status  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2020-09-18. Score: 4 | Accepted answer
  
  You should add a *Field Value Comparison* condition. This lets you only fire the rule if a field has a certain value.
  
  For *Condition Parameters* set the following values:
  
  *Entity*: **GroupContact**  
  *Field*: **Group Contact Status**  
  *Operator*: **is equal to**  
  *Compare value*:**Added**
  
  > **Comments:**
  > **username_0**: This was the perfect solution, I wasn't aware of the Field Value Comparison condition. Many thanks, Jon!  
  
  ---
  
  ### Answer by username_2 on 2020-09-17. Score: 2
  
  As a workaround could you create a smart group for everyone added to the group (not pending) and use that for your CiviRule?
  
  > **Comments:**
  > **username_3**: Smart Groups don't work with CiviRules, sadly  
  
  ---
  
  