fbpx

Using webhooks with ClickUp to run more efficient Automations

DISCLAIMER: As you probably already know, this page may contain affiliate links. If you click on one of the product links, I’ll receive a small commission. Thanks!

If you’ve ever found yourself frustrated by the automation limits within ClickUp, and you’re looking for ways to maximize your workflows without incurring additional costs, you’re in luck! 

Webhooks offer a game-changing solution, enabling efficient and real-time communication between applications. Imagine being able to facilitate seamless interactions between ClickUp, Google Drive, and many other tools right at the moment a specific event occurs, without having to wait for periodic checks by the system.

Webhooks provide this exact functionality, making them invaluable for anyone looking to enhance their project management capabilities within ClickUp.

Using webhooks with ClickUp to run more efficient Automations story - Ask Yvi

What are Webhooks?

To grasp the full power of webhooks, it’s vital first to understand what they are. At its core, a webhook is a method for applications to communicate with each other in real time. Imagine it as a telephone line that allows different tools to relay information and instructions instantly. For instance, webhooks can facilitate ClickUp to communicate with Google Drive, Facebook, or virtually any other tool that has webhook support – even though their APIs might not be as open as we’d like.

When a predetermined event occurs in one application, it activates a webhook to send data to another application. The receiving application then processes this data as instructed. This real-time capability is what makes webhooks incredibly efficient and powerful. However, the scope of what we can do with webhooks is determined by the APIs of the tools we’re integrating with.

Why Use Webhooks in ClickUp?

ClickUp’s native integrations are definitely useful, but they do have limitations. When you hit those limits, webhooks can provide a cost-effective and flexible alternative. Here are a few reasons why using webhooks within ClickUp can be beneficial for your workflow:

  • Real-Time Automation: Unlike periodic checks by traditional automations, webhooks are triggered immediately, ensuring that tasks are updated without delay.

  • Customization: Webhooks provide the flexibility to customize workflows to a greater extent than native ClickUp automations.

  • Cost Efficiency: ClickUp’s automations have limits, but webhooks can help you stay within those limits by offloading repetitive tasks to other tools.

Creating a Webhook in ClickUp

Creating a webhook in ClickUp and integrating it with other applications like Google Drive involves several steps, but the setup is relatively straightforward. Here’s a closer look at how to set this up using make.com (formerly Integromat) for automation:

  1. Trigger Setup:

    • In ClickUp, set up a custom field that will act as your trigger. For example, change your video stage field to “recorded,” prompting further actions.

    • Configure an automation to call a webhook when this field changes. This involves pasting a URL from make.com into your ClickUp webhook configuration.

  2. Creating a Webhook URL at Make.com:

    • Go to make.com and start a new scenario. Search and select the “Webhook” module.

    • Create a new custom webhook and name it appropriately based on the process you’re automating.

    • Copy the webhook URL provided by make.com and paste it into your ClickUp automation settings.

  3. Processing the Webhook Data:

    • Configure the webhook in make.com to handle data coming in from ClickUp. Use predefined modules to fetch task details from ClickUp based on the task ID received.

    • Map the incoming data fields to ensure correct information is passed along the automation chain.

  4. Performing Actions with Received Data:

    • Add modules in make.com to perform specific actions. For instance, generate a new Google Drive folder and subfolders based on the task details from ClickUp.

    • You can configure various modules to create folders, name them according to task details, and update the relevant fields back in ClickUp with links to these folders.

How to use Make.com blueprints to streamline automations

One of the best ways to streamline this setup process is by utilizing make.com blueprints. By importing ready-made blueprints (JSON files), you can quickly set up the required automations without building them from scratch. Simply import the blueprint, update the webhook URL, configure folder paths, and ensure that all connections (like ClickUp and Google Drive accounts) are correctly linked.

✨Grab your FREE Make.com Blueprints:✨ https://bossyourbusiness.academy/dam-automation

Conclusion

Webhooks represent a transformative opportunity to elevate your ClickUp workflows beyond conventional limitations. By embracing this powerful tool, you can harness real-time automation that not only enhances efficiency but also streamlines your project management processes. Imagine the freedom of customizing your workflows to fit your unique needs without being confined to ClickUp’s native automation limits. With webhooks, you can seamlessly connect ClickUp to a myriad of applications, ensuring that every task is executed precisely when needed.

This capability allows you to build a more responsive and dynamic work environment where tasks automatically trigger actions across various platforms, such as creating organized folder structures in Google Drive or sending timely notifications. The cost efficiency of webhooks also means you can manage your automation needs without incurring extra expenses, making it an ideal solution for teams looking to optimize their operations.

As you explore the potential of webhooks, take advantage of make.com blueprints to accelerate your setup and maximize your efficiency. The possibilities are vast, and the benefits are clear—enhanced productivity, improved workflow customization, and the ability to stay well within your automation limits.

ready to take action and stop trying to figure it all out on your own?

You don’t have to do it all – or all by yourself.

I have helped many Digital Entrepreneurs scale their operations, teams, and offers!  

Let’s get you to that next level.

Video Transcription:

Yvonne Heimann [00:00:00]:
Have you ever felt frustrated by hitting your ClickUp automation limit and wished there was a way to get more out of your automations without shelling out some extra cash? Well, you’re in luck! Today we’re diving into a game changing feature that could save you both time and money. We’re talking webhooks. So stick around to find out how you can supercharge your ClickUp workflows and keep your automation limits in check. Hi, if you’re new here and don’t know me yet, I’m Yvonne Heimann, aka Yvi, from AskYvi.com, and I help digital entrepreneurs and service providers turn their passion into profit by automating their business so you can dominate your industry. Now, I got called out. As you can see right here, my Webhooks 101 apparently was a total terrible video. I’ll give him that. Yes, I didn’t dive deep into the specifics.

Yvonne Heimann [00:00:54]:
That’s exactly what we are going to do today because this is Webhooks 102. Let’s dive deep into the specifics and all the things you can do. Because even though he didn’t ask nicely and that comment was definitely not efficient to get any answers, I’ll still give you the answers because you deserve better. Before we dive into webhooks and how they can benefit your ClickUp setup, let’s first cover what a webhook actually is, and let’s revisit that. So webhooks is a way for apps to communicate. So if you want ClickUp to talk to Google Drive or Facebook, yeah, the API is not as open as we would like, but it’s there. Webhooks is pretty much like a telephone line straight to the other tool to be able to do things. Hey, Google Drive, I want you to generate a folder into this and that.

Yvonne Heimann [00:01:52]:
That’s what webhooks can do. So pretty much when a predefined event happens in one application that can trigger this webhook that says, hey, you need to do something, and that webhook then sends data over to wherever you tell it to send it to, and the receiving server app service provider, whatever takes the data, and I does whatever you tell it to do with it. Now, there is limitations. There’s limitations by something that’s called the API. API is what tools allow us to communicate with them. So sometimes you can create a task, but you might not be able to create a subtask and you can generate a folder, but you cannot generate a new gmail account, things like that. So we are limited by what the API allows us to do. Now, with webhooks, all of this happens in real time, meaning if I trigger something and I do what that initial task is to get all of this going, it happens right away.

Yvonne Heimann [00:03:00]:
And that’s what webhooks are. Now that we’ve talked about general, what webhooks are. Let’s focus on specifically webhooks within ClickUp. ClickUp webhooks lets you automate your interaction between ClickUp and other tools and services. Yeah, and all of this again is happening in real time. You might have seen me on one of the recent ClickUp webinars where I shared three of my most favorite make.com automations. You can snatch everything down there. One of those is, as you can see right here, a webhook that we use in ClickUp, when triggered, generates my folder for the videos that I’m recording right now here with you.

Yvonne Heimann [00:03:46]:
So I don’t need to name the folder, need to spend time generating the subfolders and then linking it in ClickUp and all the things. No, a webhook does that for me every single time. Meaning magic is happening on Google Drive and all I did was a little change within ClickUp. Now why use webhooks within ClickUp? First off, yes, there is some native integration between tools, but something like this we cannot build natively within ClickUp. Also, automations can run out. You have a limit on automations. Webhooks are also cost efficient. You can’t always use webhooks.

Yvonne Heimann [00:04:31]:
So for example, in this automation, I continuously have to call Google Drive to check is there a new video? Is there a new video? Is there a new video? Which is why you see the clock right here. Because if I do that constantly, I will be using up my data on make.com and I don’t want to do this. So rather than make having to go out and is there something new? Is there something new? Is there something new? It’s like your mom calling, are you there? Are you there? Let’s not do that. Webhooks are really cost efficient there because they are getting triggered by something you do. And webhooks really give you that flexibility and the ability to customize what you want to get done because you can connect so many other tools through a webhook. So let’s stick with one of my favorite automations so I can explain to you specifically how to trigger webhooks, how to build this scenario out, and how to set all of this up. And stay tuned. I will also show you how you can take make blueprints which is pretty much a template and apply them to your make account so you don’t have to rebuild all of this.

Yvonne Heimann [00:05:45]:
When we are in here, this video stage is actually our trigger, meaning when that drop down field changes, we do something. So if you look right in here, we have when custom field changes from anything to record, we are calling a webhook. Now, here’s the first thing. Calling a webhook. Great. That’s a URL. Where the hell did you get that from? Let me show you. Going into make.com and into scenarios, we are creating a new scenario.

Yvonne Heimann [00:06:17]:
And there it already is. If it’s not right on top as it is with me, you can also just search for your webhook. And we want to go with the custom webhook. That’s it. Now right here, you’re running into the next question. Great. Yvi, what the hell are you talking about? It says, choose a hook. I already have a couple hooks set up for all kinds of different automations.

Yvonne Heimann [00:06:41]:
In this case, simply add a new one and say new ClickUp hook. I like to name them specifically for the process that we are automating. And that’s it. You literally just save and you copy the address to your clipboard. That’s how simple it is to get the URL that needs to go right here into call your webhook. What that means is the automation right here in ClickUp now is set when you set the video stage to record call the webhook. Being in make cool, the moment I do something, it is going to get information, but it’s not what is it going to do with it? So first, let’s save it anyway for a second. What are we doing with this? And that’s where things can get a little bit dicey, as you see right here.

Yvonne Heimann [00:07:35]:
One of the things we always do is we pull information from ClickUp, the first thing that happens. So to show you the data that’s coming in without creating a whole bunch of mess when information comes in, this is what this looks like. Look at that. There’s a whole bunch of information, all kinds of stuff. Now, because we use the webhook, this thing knows what the task id is. That’s how we can identify anything and everything within ClickUp. So rather than assuming everything came in, because sometimes ones and zeros can go crazy, I always like to get task. Meaning again, just like we added a webhook, you do the at ClickUp, and then we do get a task. And that’s the module you’re going to add here.

Yvonne Heimann [00:08:26]:
Now, going back, you can see right here, the payload id is the task id. That’s how we can identify literally everything in ClickUp. And with that we are getting that specific task and all of the information. So if you look right here, we pulled all of the information from that specific task and then we say generate a Google Drive folder. That is my main drive folder. Now look at the magic that is happening in here. We first of all connected to Google Drive in your make. You can do all of that.

Yvonne Heimann [00:09:02]:
We then yes, it’s a shared drive. We have domain admin access, which shared drive is it? And then I choose the specific folder location, which is the path to my 2024 YouTube video. You can literally by plus find all of the folders. And it’s what I do in this is I have Google Drive open so that I know exactly the folders I need to get into and to the last folder where I want this episode folder to be created. And then I pull the information from ClickUp. As you can see right here, I can pull information and map certain information from anything that was there beforehand. So looking at this, we pulled all of the task information. So I want the episode number to be in there with a dash in between the task name because that’s the video name.

Yvonne Heimann [00:09:57]:
And then with the task id. So now the folder is generated, it is named how I want it to be named, and it’s done. Not only that, you also have flow control and you have repeaters and routers and all kinds of things in here. We use this router to now do multiple things all at once within this folder. So with that we have the main episode folder generated and then we are creating a final folder within that. As you can see right here, we pulled the folder id from that generated folder that’s in there and name it based on what we are building. So it’s the final and then the task id. I always like to put the task id everywhere just in case some folders get moved and we don’t know any more where it goes to.

Yvonne Heimann [00:10:46]:
Then the raw folder is built the same way as well as the graphics folder. Not only that, because ClickUp is our single source of truth. We update ClickUp as you can see right here with a link to the main folder we generated. So now our folders are generated in Google Drive and they are linked back in ClickUp. Now all of this happens automatically just by me saying record this video. Now. As I already mentioned, first of all, you get the templates down in the description. Let’s talk about how you can use make.com blueprints so that you don’t have to rebuild all the things that I just built.

Yvonne Heimann [00:11:31]:
So log into your make.com account, go into your scenario dashboard and create a new scenario. Then go into the more settings and go import blueprint. It will ask you for a JSON file. That’s what you are getting through the stuff in the description and you hit save and look there it is. Now once uploaded, you need to update your information, meaning generate a new webhook URL. You just saw how to do it. Connect your ClickUp, make sure the payload id is right and all the things Google Drive folder make sure it’s connected to the right Google Drive account. Make sure you have all of this cleaned up.

Yvonne Heimann [00:12:22]:
Make sure these are filled out so custom field says there is something wonky. So might what you might want to do is right click this and run this module only as you can see the webhook is the same. What it will do is you then can tell it hey, this is the task id. Pull the information and you just get the information for this task so that in here you can make sure all of this is set the right way. And that’s how you go through every single of those modules to be able to update your information. All the way to getting the link back into your ClickUp importing your JSON file creating your new webhook connecting it into your ClickUp test running by right click you’ll get the task module, give it the task ID so it can pull some information, and then double check to make sure you have the right folder. You have the right breadcrumbs for your folder in the Google Drive module, as well as the final folder, the raw folder, and the graphics folder. And then double check your last ClickUp update module to make sure everything works as planned.

Yvonne Heimann [00:13:37]:
And you’ve already seen some of my favorite webhook automations. One of them is the Google Drive folder automation. The other one is generating a task based on a short video uploaded into Google Drive. And I have one more. If you want to snatch those, including the make.com blueprints, grab the link below. Everything is there for you with a little video with the three JSON files, and a little bonus too. Now you know why I use ClickUp webhooks alongside my native ClickUp automations. It’s a fantastic way to maximize efficiency and keep costs down.

Yvonne Heimann [00:14:15]:
If you found this video helpful, don’t forget to hit that like button and subscribe for more ClickUp tips and tricks, making your business more efficient and turning your passion into profit. Drop any questions and comments below. Again, nice questions are more efficient and getting productive answers and I will nicely call you out on my video rather than making fun of you, I’d love to hear if and how you are using webhooks in your workflows. And if you haven’t yet, go check out that video here where I talk about my five must have ClickUp automations that skyrocketed my business. And until next time, happy automating and optimizing.

Leave a Comment

Your email address will not be published. Required fields are marked *