Introduction to Webhooks

Hey everybody! Jeremy Redmond here with Kyle. Have you ever wondered what's the question you'd ask to help people understand they need to start with a webhook? In this blog post, we will delve into the world of webhooks and explore their significance in automation.

Understanding the Power of Webhooks

Webhooks serve as a crucial component in data exchange processes, allowing data to be sent and received through a URL. Think of a webhook as your digital mailing address where data flows in and out seamlessly, empowering various applications with unlimited possibilities.

Setting Up Webhooks with Different Platforms

Using webhooks to trigger your automation flow can be a game-changer. Platforms like TicketTailor and Stripe offer simple setups to create webhooks, enabling users to specify events and endpoints effortlessly.

Importance of Using Webhooks for Automation

Webhooks provide a versatile solution for triggering actions based on specific events, offering dynamic data processing capabilities. By setting up webhooks, users can streamline their automation processes and create more efficient workflows.

Choosing Between Webhooks and Native Integrations

When deciding between webhooks and native integrations, it's essential to consider the availability of apps and the ease of data integration. While native integrations provide convenience, webhooks offer a customizable approach for connecting different platforms.

Conclusion: Embracing Creativity in Automation

In conclusion, mastering the art of webhooks opens up a world of possibilities in automation. By leveraging webhooks effectively, users can enhance their workflow efficiency and unlock new realms of creativity in data processing and automation.

Step 1- Click on Webhook

Step 2- Copy the Webhooks link from the Column

Step 3- Paste the webhook link into the API endpoint URL

Step 4- Select set parameters- Enter first name – Enter Value – Click on Save & Send Test request

Step 5- Now Click on Check for new events

Step 6- When we click on check for new updates it gives option 1 with first name and its value—Then Click on Save trigger

Hey everybody. Jeremy Redmond here with Kyle. How's it going? Cool. So in this, we got a question posed and it was, what's the question you'd ask to help people understand they need to start with a web hook. So what? What they mean by that is a web, a web hook to me and Kyle will explain what it is to him, is data being sent and received.

Via a URL of some kind. There's a URL that lives and people are either pushing data to it, posting data to it, or sending data. Did I say that right, Kyle? Yeah. Think of it as your mailing address. Anyone in the world can send you your mailing address if they have it. Right. So a lot of apps. So this is the one thing I want to cover.

Or I'll the first thing I want to cover is using webhooks to trigger your flow is very powerful because you can, a lot of apps have. The ability to use webhooks. It's unlimited powerful, right? So if we have an app, but it doesn't have the trigger or the action you want, or we don't have the app at all, you can do this.

So say I don't see TicketTailor here, but we do have TicketTailor. You can go, I want to trigger this flow with a TicketTailor Um, it's a ticketing app. Oh, here. Ticket tailor. Do you would click webhook in our thing. Oh, sorry. And then you would, you would, all you have to do is search, right? Search ticket Tailor webhook.

So do that, Kyle, right here. Oh, you did. I did. I was trying to pull that up. Sorry. Okay. So great. Ticket Taylor. How would I create a webhook? Okay. Now walk us through how, if you, this is again, if you do not see an app that exists in ours and you want to create a webhook, this is a pretty, a fairly simple way to connect any app that we don't have, and you can connect in a webhook Kyle.

So first you search app that we don't have webhook, right? Ticket Taylor. And then you pull up something like this. Go Kyle. Yep. You want me to explain from here? Yeah. Okay. So we know now that we're going to be using webhook. So back inside of task magic, I'm going to select webhook as our trigger, just so we can see what our next step is.

And then from here, we have a bunch of directions that I'm going to explain right now. Um, but we have our webhook URL. Without this WebHook URL, you can see that there's not much more to do on TaskMagick besides click copy and check for new events, right? But we're not ready for this button. All we've done so far is click copy, but we also search for TicketTailor and we have this article.

So now from here, everything is already confusing. It gets a lot easier because on almost every platform, it's going to be a very, very simple form and you're completely done. So we saw the TicketTailor, uh, article here. And then if I scroll down, we have these directions from TicketTailor. That show what the form looks like on their side.

So these are the directions for finding that, um, whatever you're going to click, clicking webhooks, et cetera. Then we'll see inside of here. There's just a couple things we need to enter. It's some URL that we want to send data to the events and then a status, which I'm assuming you can set your ticket tailor thing to active versus inactive, things like that.

So the first thing we have here is the URL, which we can see is this. So inside of TicketTailor, we would be adding this URL in the URL field or whatever it says on that specific platform. After you add the URL, what most platforms are going to do, and I'll show you another platform just so you can see the differences, is they're going to ask you to specify one or many events.

The reason you might have many events is you're going to run very different automations for different things, right? So Jeremy, for example, if a new user buys a proxy for us, The automation is going to be, give them a proxy, right? But if their subscription was canceled, the automation is take their proxy away.

So we have two different triggers in that case, right? One is being, one is a subscription being created and another is a subscription being canceled, which means we have two different. Does that make sense that we have two completely different automations and why we'd be selecting different things here.

And again, to show you how this looks on another platform, if I go into Stripe, you can see a very similar thing where you're selecting all of your events, which these are all the account events, balance, et cetera. And then, um, after we select something in here, like every other platform, for the most part, we would be specifying the URL to send it to endpoint, webhook, same thing.

And, and that's it. Right? Very similar setup between TicketTailor and Stripe here. We have an event, or multiple events, and a URL. We had events, and now we have a URL. That's how it is on all of these. So, in this endpoint URL, you would put the thing you copied from PathMagic? You would put that webhook URL, correct.

Okay. And, again, different platforms call it different things. The more technical of a platform you get, the further away from webhook you might get. Um, but they're almost all, I mean, gonna be very, very similar. with that setup process. And can a non, a non technical person can do this with our directions, right?

Yeah, I mean, it's going to be a very simple thing. If I was to go, um. And again, this is triggering based on a webhook. So receiving data. Correct. So I'm going to actually, I'm going to sign into Pavley really quick and I'm not going to say anything and you're going to take us through the process. And then I'll find if we have any other texts to add to this page.

That way too, to make it make more sense.

Okay. I don't see it on here. Okay. I didn't realize I was on the other monitor. Um, okay. So Pavley, um, we're skipping past our trigger and we're setting up an action. We're trying to trigger task magic, right? Task magic has a trigger. Something else has an action in this case. So in Pavley, I'm going to go ahead.

I don't know what they call it. It's going to be like API or HTTP. Doesn't task magic have a Pavley app? I was looking for it. I don't see the task magic action. They might've figured out it's the exact same as the API action. I'm not really sure. They did used to have it, right? Oh, wait. Oh, there it is.

Triggers when scrape. That's not a trigger. How did they do that? Okay. Anyways, different video figuring out what that's cool. Yeah. Okay. Appreciate you guys building stuff that we don't have. Okay. Um, in Pavley, we're selecting API. This might be called HTTP. It might be called send to webhook. There's a couple different things.

This could be called. Okay, then we're going to execute the API request. I'll go ahead and click connect here. And, um, so this is their, this is their webhook. This is Pavley with sending data to a webhook. So what I'm trying to do with them, why would they call it API then? That's yeah, I don't know. They wanted to, why are you sure?

That's not some, that's not web. But yeah, I mean, we're executing an API request. Why it's called this first. Like I think Zapier calls it send a webhook. Yeah, I don't know. I think it's like if I was using a web hook, I would say, call it Web hook, I wouldn't call it api. I, yeah. This been on IT language being the same, but different things are being met.

Let me see what it is on Zapier. I'm pulling it up. It's webhook. I've used it for the trigger and the action. Yeah, yeah. It is, um, we call it htt. Well, active pieces calls it HT TP. So there's, there's different things. You might call it HGTP, api, send a web hook, et cetera. Okay. Um, and then we should change that to send a web book.

If that's the same thing, uh, in our active, yeah, we can update, we can update it to be send a webhook. Okay. Um, I think I already found one thing that you might be confused on, but I want to go through this setup. I think, because I'll find other things. Okay. And again, not everybody has these questions.

You're going to see slightly different questions than TicketTailor. Okay, so we have get. Okay. Yeah. It's an API endpoint URL. That's where we paste our URL. So I'll go ahead and do that. Okay. And then payload type, Jason, no off.

This is a, I kind of expected more of their questions to be similar to the other ones. This is a little bit different. Anyways, we'll just go through it quickly then I guess. Um, so not every platform is going to allow you to specify the, and this is kind of me asking you cause I need to work out the UX of this.

Not every platform is going to ask us. the type of event of event here. Um, a lot of platforms are going to force it to be a post request. So I know you have no idea the differences between these and I don't blame you for that. Um, we need it to be post always. So I guess that should just be set in this setup screen.

I would not give people those. I don't understand what all of those. I don't want to add all of these, but I want it to be easy. Let me. Yeah, I want it to just be by default post. Oh, well, there's your. No, I know they do this. I know they do the same thing. Well, anyways, we'll just remind people it needs to be post.

Um, we don't ask for headers. Headers are things that if they're being required, the site's probably making it super obvious and then set parameters. Um, this is where we're specifying the data we want to send, and I'll wrap this up so you can see how simple it is to send data to webhooks once you know what you want to do.

Okay, so add that post direction. Yeah, I'm gonna have that. Yeah, somewhere in here. I'll add it somewhere in there. Okay, and then as an example, I'm gonna do first name and I'll enter Kyle. Okay, so this is the, this is the label and then a value. What that turns up, that turns into, this is a variable. And this is the variables value when it comes to task, right?

So if I click save and send test request, and then it respond, whatever it gives us, right, something responded and I go back to task magic, I can click check for new events, and then the first result here is going to be what I just sent. Now, again, making webhooks make sense and why they're valuable. Now, this is going to be Jeremy and I'll send it again.

And now if I click check for new events, the latest result is now Jeremy, right? Boom. Dynamic data. So if I had at first name in my automation, it would have changed between triggers, right? Yeah. Yeah, sure. And the reason this is also really valuable is because a lot of people have, um, these automation set up and they're adding on to existing automations with task magic.

This API task is also able to use any data from other steps. So if I had my air table steps up here, I could send that air table data as a variable magic web book. And now I have extremely dynamic data. All through my webhooks set up. Okay, so that's setting up a webhook. So that's good. Are you done? Okay, so and I think any anything else to wrap up right outside of adding post and making sure that's post when you're grabbing data, right?

Yeah. So anything else to wrap up when someone should choose to trigger a flow based on a webhook? You should try to use webhooks if we don't have the app for it. Um, the other really important thing is maybe so the first step is, is there an app right? That's ideal. Is that we have an app for it? And then another thing we went over in a different video is before trying webhooks.

Can I use something like Google sheets with a native integration in that platform? That's a very, very common work around. It's a very common work around and is a lot easier than webhooks. However, after that, Webhooks is your best option. Otherwise, you're having to make decisions on the screen and compare it to some backup data.

It gets a lot more complex. So that's kind of your path is, I try to use apps. If I can't, I try to use something that can make it into apps. I try to use, like, you can just call it a spreadsheet. So it's either like Airtable or Google Sheets. Yeah, some sort of Excel. Yeah. Yeah. Those are the three non technical things, right?

Either an app or then Google Sheets, Airtable, Excel, you know, and then you can go with those with a native integration, meaning, meaning you can export your results from Airtable to Google Sheets, right? You can create that in their realm. So that's how you can kind of work around again. It's a great creativity.

So let us know if you have any problems, um, with that in the comments, give us a thumbs up, subscribe. What else are you saying, Kyle? It's important to be creative. Most of the time you're doing something that that website doesn't want you to do, which is why they don't have an API for it. So creativity always wins.

Yeah, there we go. Cool. Stay creative out there. Thanks, Kyle. Yep.