Hi @Jhart4595 , That is a good question and not off-topic at all.
Normally a honeypot field (hidden) that is populated, is evidence of a bot filling out a form and on submit, the form would be rejected by the server as spam.
With Webflow, there is currently no support for honeypot spam tests. Google’s recaptcha is supported as a more effective alternative since bots have gotten smarter about getting around simple tests.
If you did have a hidden field you used as a test, the value would need to be captured with the submit; either null or a value. If you had notifications on, the notification recipient would already have received the mail message obviously.
You don’t indicate what mail client you use or server so I can’t elaborate on how to test for the string and I don’t know the string that would exist in the message body. If your mail client supports regex, you could write a regular expression that would trip a flag or act on the message.
I could see how it would be possible to listen for an event on that field before the submit fires but I don’t think it would be very effective. I have never bothered trying on the client side since there are so many ways around it for spammers. It is much more effective to process spam on the backend.
If you are getting lots of form spam, you may want to consider a third-party form server. I switched clients over to usebasin.com when they were getting hammered and now only a few manual SEO fills ever happen. Basin uses Akismet, Google reCAPTCHA, and their own code to keep the forms spam free. The “_gotcha” honeypot is also supported. I would add that you can selectively use reCaptcha on a form by form basis versus Webflow’s “On For All Forms” setting. I am pretty sure formspree does offer similar features as well. Both are trivial to integrate with Webflow as are others listed in the Third-Party Integrations page in the university.