HS keeps notifying us about the same form, even if a different form has been filled in
SOLVE
I've set up a basic automation to inform us on Slack when a form is filled in. It goes:
Trigger: A form is filled in > If/Then: Branch: which of our four forms was it? > Send slack notifications to the relevant people based upon which form it was.
I've got a problem when someone comes back to fill in a different form on the site. Slack sends us notifications about the first form they filled in again, rather than the most recent one. So, if they previously filled in form A, then come back and fill in form B, we will get a second notification about form A again. We won’t get anything for form B, because it believes it resolved the automation by notifying us about form A.
I know why this is happening, just not how to solve it. It's because the If/Then Branches checks the forms one at a time. So they fill in form B, and it starts the process. The branch goes, "Have they filled in form A?" and the answer should be "No, not this time", and then it should move on to form B. Instead, it asks if they filled in A, and the answer is technically yes because they have done it previously. So the automation goes, "cool, they did form A, so I'll notify about that. Automation done".
How can I tell the automation to ignore previous form entries that it's already resolved and just acknowledge the latest one?
HS keeps notifying us about the same form, even if a different form has been filled in
SOLVE
You could refine the submission to look for when it was submited (ie: submitted < 1 day ago). But that wouldn't solve if someone submits a form again too soon.
You could try an if/then branch looking at the recent conversion field and use the contains value to look for the form name for your branches instead of looking for form submissions as that field will be overwritten by the submission.
HS keeps notifying us about the same form, even if a different form has been filled in
SOLVE
You could refine the submission to look for when it was submited (ie: submitted < 1 day ago). But that wouldn't solve if someone submits a form again too soon.
You could try an if/then branch looking at the recent conversion field and use the contains value to look for the form name for your branches instead of looking for form submissions as that field will be overwritten by the submission.