reCAPTCHA v3 is a free service from Google that protects your site from spam and abuse. And the Bubble.io official reCaptcha only supports v2 (the one with the checkbox).
So I made the Invisible reCaptcha v3 open source plugin to provide an easy way to integrate the reCaptcha v3 (the invisible one).
You can find step by step instruction in the description (this plugin does not have anything to do with the bubble one, this is for the invisible recaptcha v3).
The following instructions explain exactly what you need to do to make it work:
Go to the Google reCaptcha service page with your Google account.
Create the app by filling the form. You MUST select the reCAPTCHA v3, not v2.
Once submitted, Google will provide you with the following two information.
Site key
Secret key
Set these two keys in the plugin settings.
Place the “reCaptcha v3” element on the pages where you want to protect.
Now you can run the “Verify reCaptcha token” action on the event “reCaptchav3 A Token retrieved”, or whenever you want to verify the reCaptcha.
You can check if the verification was successful from the action results.
I appreciate the plugin, but it’s not working for me. No matter what I do, I always receive a NO on the token verification. I tried different minimum scores from 0 to 1, but nothing worked. Any idea what might be wrong?
Hi @imlorenzo - it also doesn’t appear to be working for me. I placed the v3 icon on the page and have the following workflows in place. Did I miss something?
I am trying to make a form “submit” conditional on reCAPTCHA.
Please share the verify recaptcha action and element settings, not the email action, otherwise I can’t tell if there is an problem with your settings or not. And did you set the recaptcha api keys on your plugin settings?
Hi @imlorenzo.
I’m new to bubble and I’m trying to implement captcha on a typical submit action in a form. I came across your plugin but I failed to understand how to use it. As for v2 we can deactivate the submit button based on checked value of checkbox here I’m not sure how the dynamics are, how will it prevent the triggering of submit action by bots.
Thanks in advance,
Paulo
So far the plugin seems to work well. Are there any plans to extend functionality so we can use the full capabilities of v3?
I don’t have a lot of experience with setting up reCaptcha, but I’m assuming 0.9 is a pretty safe to stop whatever I need to stop, however is it possible this is too high?
Will the plugin show additional challenges if the user does not get the appropriate score? and how would I then re-validate anad allow the user to continue the operation they were trying to do?
First of all, thank you so much for building this!
I do have trouble implementing it, though. The token comes up as empty when I run the workflow. Site and secret key are implemented. Element is on the page. Not sure what I am missing here.
To explain to those who never have contact with reCaptcha v3
It is invisible to the user (there is no challenge to the user), so you (developer) recieves a score, and should decide what to do.
score 0.5 - everyone will pass
score 1.0 - none will pass
I suggest you start with 0.8 and keep collecting data.
Thanks for the good plugin, but it looks like the plugin stopped working on our side. While the setup and integration were done quite some time ago, at the moment the plugin is throwing an error related to API keys though it was set and worked perfectly, I even tried new ones but still am getting an error even in Bubble’s debugger.
@mulleralice984 Are you saying the reCaptcha element needs to be visible on pageload for the token to be created? Right now I have it as hidden to the user and I can’t seem to get any values.