We set up a workflow when someone applies to be a part of our community. Once a contact has been "Accepted" it is supposed to trigger an email to me to manually add them to the community. For some reason the emails aren't coming through. This is how it is set up. Does anyone have any tips as to how to resolve? Is it not set up correctly / is there another way to set it up so that when the property value changes i get the email? or should i branch after accepted? thanks so much in advance for any help you can provide.
@ASalerno5 are you expecting the task from step 5 to be completed before the check on the SAL decision happens? If so, there is currently no delay and the check from step 6 happens pretty much immediately after the task is created.
You would have to add a fixed delay (e.g. 48 hours) or a delay until the task is completed.
Currently, I would assume that all contacts simply go down the rejected route. You can easily check this by looking up the property value set in step 7 or 8.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Can you please share a screenshot of the full workflow? The branch isn't enough context to identify a potential issue.
If you could also describe what you're expecting each enrollment trigger and action to do, that'll help.
What I'm currently seeing is a property value changed and a notification. However, the value doesn't trigger the notification, it's simply preceded by it.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
Thanks for your help @karstenkoehler ... attaching the full workflow screenshots here.
Form fill triggers lead source, community list, and status update in contact property value. email is sent to two individuals saying someone has applied. task is created for an individual to check if they are a fit. brand based on whether they are a fit or not, property value updated depending on whether they are accepted or rejected. if accepted, trigger email to individual to add to the community.
re: your comment, how do i ensure a trigger if a property value changes?
@ASalerno5 are you expecting the task from step 5 to be completed before the check on the SAL decision happens? If so, there is currently no delay and the check from step 6 happens pretty much immediately after the task is created.
You would have to add a fixed delay (e.g. 48 hours) or a delay until the task is completed.
Currently, I would assume that all contacts simply go down the rejected route. You can easily check this by looking up the property value set in step 7 or 8.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer