Honeypot – Add an Extra Layer of Spam Protection to Forms

[Anton]

Hi Community,
Here’s a workflow example that I’ve “developed” a while ago:

The honeypot

What is it?

Technically speaking a honeypot is a extra layer of spam prevention.

How does it work?

Adding a hidden field to the form you’d like to protect against spam/bots. If the field is empty on form submission it means that the sender was a human since he/she did not see this field. If it’s not empty it’s a bot. Super simple

Requirements:

A new text property called honeypot (you can call it how you want) and add it to your desired/all form(s) as a hidden field.

Workflow build/logic:

Check if this field is unknown. If it’s unknown proceed to the next action/workflow. If it’s known → do nothing.

Screenshot of the workflow:

Tipp: You could create a list like “bots” and put all of the submission with a “known value” into it.

p.s.: Here’s my “steal this workflow” post I’ve posted on LinkedIn describing it a bit more in detail

cheers,

Anton

[JMartin1094]

That’s so sick. Really clever.

[CLee42]

Does this work on HubSpot forms embedded in WordPress?

[jeroenbeelen]

Can/will a bot not see the field is hidden and just for that ignore it?

[STravelstead]

So how did you actually get the “honeypot” rich text field on the form since HS doesn’t currenly allow this property type to be added?

[STierney]

Hey @STravelstead,
Thanks for following up here!
Re-tagging @Anton to see if he has any follow-up context to share.
Shane, Senior Community Moderator

[Anton]

Hey @STravelstead,

just tested it in a free account (to make sure it’s available to any tier)

If you go to the Properties (Settings / Data Managmenet / Properties), you can create a new property with the “Rich- Text” Field Type. Naming is completely up to you, but it should be something that you/your team will know about.

Once created, it should be possible to simply add it as a field to any form and hide it

best,

Anton