Webhooks - Auto Send the License Email When Someone Buys White Label Suite from You

Apparently, when I was jumping in there with Sunny's question, someone thought that was my question. But anyway, all right. So my question actually is, I wanted clarification on the process for signing up, like what I should expect when I create a package and I give people the link to sign up, and if it's like 30 people or more that are signing up, I'm not clear on what they would expect and how long it would take for them to get their license so that I can integrate it into the back end.

Great question. Great question. So if you set it up using automation tools, it's instant. I'll show you what I mean. Okay. If you've got the leads tool on the menu in your lead effect so that when they buy, they can go somewhere and log in. The only thing that you have left to do is create an automation that sends them the email. And I'll show you how. So go.

Wait. So then I wouldn't give them the package link?

Yeah, you'd absolutely give them the package link, 100 %. That's the starting point. So we start in the license dashboard and we create the package. So you've got to this point, you've got your Stripe account connected, you've created a package over here. So we've got a package for sale and here's the buy link. Now, what we want to do is when somebody buys this from us, we want to send them a license email. That's the most important step. So how do we do that? We, white label suite, can't send that license email for you because they don't know we exist. We are white label. We're white label. We are behind the scenes. It has to come from you because it's your software. So what you want to do is create an automation that sends the license email for you. How do we do that? In the account settings area, the area you're looking for is this one, the integration. Sorry, make sure your high level is connected, but the area you're looking for is here is web hook. So the web hook system is what's going to make the license email work for you. Now, you can see I've set this up with Zappier.

I've set it up with Pably, but if you wanted to use the internal web hooks from GHL, have you got that turned on? Do you know if that's been turned on for you with Leadific?

Well, okay, so backing up. I went into my little states. When I look at web hooks, I see nothing, but that's because I haven't created anything, right?

Yeah, correct. So I'll delete and it will show nothing. So you're starting with a blank canvas. All right, let's go, let's go, let's go. All right, so blank canvas just like this. Okay, so all right. I want to make sure... The reason this screen exists is exactly what you're talking about. When somebody buys from me, I need them to get a welcome email. So what we're going to do is we're going to integrate back into Leadific and we're going to use Leadific, GHL, to send that license email to my customer. Okay? So what we want to do now, do you use Zappier or Pably or any of those, Dora?

I haven't had to yet, but I have a Zappier account.

Okay, you have a Zappier account? We can do it in Zappier. So GHL has turned on their own web hooks. Do you know if that is turned on for you in Leadific? So guys, just for those who are listening, what's the difference? Leadific, GHL. Leadific is a premium partner of GHL, and they've got their own brand. It is GHL. But it's branded as Leadific, which is what Dor is using.

Okay, so if I look under my agency, are you saying go to automation and see what type of... By create a workflow, what I have available?

Yeah, exactly that. So if you go to automations, the one that you're looking for is create a workflow. We want to see if you've got... There's one that says premium web hooks as a trigger. An inbound web hook. Okay, let me look for that.

Hold on one second.

Lc premium triggers.

Okay, let me type the word trigger because I... Sorry. I see trigger link clicked.

Yeah, no, type the word web hook.

Okay. You have inbound web hook. I see inbound web hook.

Perfect. Amazing. So can you guys see my screen right now? That's exactly what you're looking at, inbound web hook. Can you see that? Are you guys seeing my screen? Yeah. Okay, cool. Yes. So what we're going to do is we're going to trigger an automation via an inbound web hook. So something coming into the system is going to trigger the automation. And what's the automation going to do? It's going to send the license email. So we want to grab this web hook. And, Caroline, yes, I will happily go through that in just one second. So when we click on Inbound Web hook, as the trigger, it gives us a really big long URL. And that's exactly what we want to copy to make our system work. So I'm going to copy that URL. I'm going to come back to our licensing dashboard here, and I'm just going to paste it in there and click on Save. Okay, so now I've got this URL in here which is set up and ready to go. What I need to be able to do is I need to be able to send some test data down this web hook so that the system at the other end can receive it and we can make things work.

So we've got this test button in here which will slide out a whole bunch of test data and it will show you what we're about to send. I can change this from this screen. I can say first name, Walt. I don't need to change it. I can if I want to. So it's going to have an email address, custom123@example. Com, a partner's email, which is my own email, a dummy password, okay? Everything ready to go. So this is going to send this data to this web hook so that the web hook receives it and we can take the next step in the automation. So send. Cool. Web hook sent. Great. Now let's look again in our automations.

By the way, in the automation, would I be creating that automation in my... I created a sub account for teaching people about leads and where I have my 23 leads page and all that stuff. Is that where I create the automation?

Yeah. So wherever your main customer database is, like your primary company account, that's where you're going to create this automation. Okay. So now we've sent this test data, we need to receive this test data to make this automation work. I want to fetch the sample requests. And it says, Okay, there is one. That's the test data that I just sent. Show me it. Here it is. Walt, Johnson, 1, 2, 3, example, everything that we just sent on that test is visible here. Yay, working. Fantastic. Now I've got all of the data that was received by that web hook. I can save. As soon as I do that, it says, Okay, the only thing that you're allowed to do next is update a contact with that information. So in coming information, I need to put it somewhere. I'm going to put it against a contact, which is perfect. So we're going to say, Okay, create and update a contact. Fantastic. That's already been selected for us. And now we can just map those fields, inbound data, to the right field. Let me show you what I mean. Inbound field. So select the field. I want my first name field to come from the first name data.

Great. I want my last name field to come from the last name data. I want the email address to come from the email data. And that's really all you need. I mean, that's the data that you need to create a contact. Amazing. So when this web hook comes in, create a contact with the first name, last name, and email address. Okay? Yay. Perfect. Now my inbound hook creates a contact. What happens next? Next, add a tag example. Add a tag and that tag can be the lead's purchase. Leads purchase. Great. There we go. So incoming data, create a contact, tag the contact and then what? Send them the welcome email with their username and password. So we say, send email, and we go, obviously, all your details, mail@mail. Com. Obviously, your details, not stupid details. Subject your leads license purchase. And then insert the data. Hi, custom values, first name, first name. There we go. You'll notice that the web hook's there as well. You just bought the leads package. You got to phrase this a little bit different, Torra, but you just bought this. Login dashboard.

Your email. Hey, quick question on that. Is it a custom value for the type of package? F or example, someone might buy the 1,000 and 2,000 or the 5,000?

Yeah. So you can come back and actually look at that web hook and you can actually see what they bought somewhere in here. I think it's the event that you will see. Actually, no, sorry, my apologies. No, it is just generically you bought a package, here's your logins. So it's like whatever package they bought will be automatically applied to their account, but the username and password is what's in the system. So congratulations, you just picked up our program. Well done. Here's how to log in and use it.

Perfect.

Helpful?

Yes, very helpful. So I don't need to worry about the quantity who click on the link. Once I set the automation up, I could have a 1,000 people sign up at once.

Correct. Okay. And when that happens, when that happens, send me a bottle of champagne and we'll raise a glass together. Okay. Thank you. As many as you like. That's the great thing about software. It takes zero service to fulfill. Once you've got it set up, it's literally just running in the background. Cool.

Actually, one more quick thing. When you were working with Sonny, you showed in the... Let me see if I can go back there. Let's see. It was under automation, and you showed... Let me just go back to my automation. Okay. Under Settings, when you're in a workflow, the workflow settings, you were talking about stop on response. What I've been doing is for some reason mine are turned off, but I could turn them on, but I never turned them on. Mine are turned off. So what I've been doing is in every email communication, I have an option at the very end. It says, if you'd like to unsubcribe, whatever, click here. And then I have a whole process of removing people from the workflow. But what I do is in my workflow, I have email, email, email, wait, wait, period, wait, period. And at the very end, if they haven't unsubcribed themselves and they haven't clicked, then they go all the way back to the beginning and have a go to back to the beginning. They just keep going through that until they remove themselves or...

I call it a profit loop, and we set our profit loop at 90 days. So we bring in a lead and we send them out a few emails, go all the way through. And if they don't opt out, then the second last step is wait, and my wait step is 90 days. So wait 90 days and then push them back to the top.

Got you.

That's a good idea. That way, literally, I'm promoting to them four times a year. So once a quarter, I'm sending out this email system. And at some point they go, look, either don't send me any more emails or I'm not interested or whatever. They can opt out at any time. But if I'm doing a promotion to someone, I build in that profit loop and I'm literally promoting to them every 90 days. Okay, perfect. You might want to change that. We were talking about your supplement company the other day. Maybe you want to make it 180 days as an example. But that can be an upsell for you, by the way. If you're talking to your supplement company, you could say to them, Look, what I can do for you is build in a profit loop that these same contacts get promoted every six months. F lick me another 200 bucks and I'll set up that profit loop for you. And it's literally just wait 180 days, loop back up, go to.

Okay. So then I don't need to worry about the stop on response feature?

You don't. No. So here's the thing. Somebody might reply to you and say, Take me off my list. Take me off your list. And if you've got stop on response turned on, that will stop. But somebody might also respond and say, Wow, this sounds really interesting. Thank you for sending me the details. And if that's the response, it could be misinterpreted and it would stop. You can get really fancy depending on how... Dora, I know that you come from a tech background. You could build your wait step, send an email, wait for reply, and wait for reply time out one day. And then you could set a, Is reply positive or negative? You could actually set the interpretation and you could have a split. If reply is positive, keep going. If reply is negative, stop. You could get really technical if you wanted to. But just think about how you want that to be felt by the customer. You want to keep communicating with them until they actually say, Take me off your list? Cool. Just leave it as the opt out. If you want to be a little bit more interactive, if they say absolutely anything to you, get somebody to interact with them personally, cool.

Put that stop on reply in place. Just depends on how you want the customer experience to be, I would imagine.

Okay, thank you.

You're welcome. Great to see you. All right, let me just finish up, guys. Sorry, I'm overtime. This tends to happen with every Q&A I ever run. But, Caroline, your question.