Isaac  
This is the email we will use to send leads to once the forms have been connected. 
info@luxbae.com

Isaac Alyssa  
Good morning.
We need this leadsheet set up when you get a chance. 
Client's ads are already live. 

Thank you. 

Hector we aren't on the final URL yet, so not ready for the primary lead sheet yet.

We are doing a DM campaign on FB/Instagram right now, but I believe Vania has already been in contact with Isaac about this. Isaac did create a lead sheet 'shell' for training purposes but I know Vania & Isaac are working on a solution for if the DM campaigns can have a webhook integrated for tracking leads in a sheet. 

Isaac we are ready to set up the lead sheet for the ads website 
https://go.luxbae.com/, that said, I don't see a webhook installed. 
 
Kristabel was the primary developer for this site if you need to loop her in. 

Alyssa - We already have all the static forms on this website connected the sheet and also to the client's GHL sub-account.

Below is the the link to the sheet.
https://docs.google.com/spreadsheets/d/15xtagIt9-QgJ0eWvUl33oaHsawxtiD2g1_wgsqSVvZY/edit#gid=0

Also can we include to rename the "webhook" name in the checklist when our devs create a duplicate of the forms on the website? Thank you.

Screenshot 2023-07-01 at 10.47.16 AM.png 11.5 KB • Download

Isaac thank you for confirming and providing the leadsheet. Renaming the 'webhook' name is notated in the developer checklist, I will let the developer know it was missed.

I couldn't find the webhook in the form settings otherwise I likely would have caught it.  Where is the webhook located? Normally it is in the form settings under 'personal data', but this is what I see:

Screenshot 2023-07-02 at 8.59.04 PM.png 132 KB • Download

Isaac I figured out why I couldn't see the webhook before. I was using this login provided for development that was also given to me for auditing: medstar-custom / Letmein123#@!

This is also likely why the developer missed checking the 'webhook' name during the checklist. I had to use this login to see it: medstar / Letmein123#@!

How can we ensure developers can see the webhook settings if you set up a limited-access login for them? Will you always be creating a username 'medstar' login option with higher-lever of admin access? I will just default to using that instead like I normally have. 

Also, I am curious, what was the limited access login created for? Will that be a standard now? 

Alyssa  

OK. Got it. I will check if we can provide access to the webhook on the limited access user account.

Yes. I will always be creating "medstar" login.

We have started creating limited access to restrict installation of unsecured or problemantic plugins by our devs. Recently many of our websites got malicious files or caused compatability issues on the website third party author plugins.

Thanks for explaining and confirming, Isaac . That makes sense. Hopefully, you are able to find a way to provide access to the webhook with limited access. I will default to using the 'medstar' login when I audit so I can catch it.

Hector here is the leadsheet: https://docs.google.com/spreadsheets/d/15xtagIt9-QgJ0eWvUl33oaHsawxtiD2g1_wgsqSVvZY/edit#gid=0

Alyssa - Yes. I was able to find a way. I have now updated the "medstar-custom" user account. Below is the new password.

New pw:  #jcfN$b0dH!9