As promised Help Scout Integration Plugin | Bubble, this plugin allows you to generate a SHA256 signature and attach it to a request to help prevent impersonation of legitimate users.
Please note:
We will be adding new features to this plugin frequently, and it currently has limited features as we just wanted to get the plugin out to you guys.
When securing a user, you must first use the action Generate Secure SHA256 Token. Once completed, please attach it to the next step, generate or update user (Helpscout).
I’m not sure that it’s working properly. With the signature, it should be displaying all the user’s Help Scout conversations regardless of the platform, but I don’t see that happening with the plugin.
The purpose of the Help Scout Secure Mode is to pull the user’s help scout customer profile that has all the conversations from help scout into the help scout beacon on your app.
The signature you have right now doesn’t seem like it’s working properly
Please make sure you are generating that SHA256 signature on the login. It will pull the related signature (Or generate a new one) for that user and propagate the beacon with any associated conversations.
No, don’t save the signature; generate it each time a user logs in.
That way, the script can check for the associated user and assign him his signature or generate a new one if the user is unknown. There is no need to store the signature within your database.
How did you implement? Since if you use a plugin you need to run a workflow but if you do it with JavaScript you can do it on page load automatically right?