Build Your Perfect Content Pipeline: A Comprehensive Workflow Guide

1. Introduction to Content Workflow Management: Hree years ago, I created a skill share course on managing content for film productions and freelancers. Initially, our focus was on commercial projects, but now we run multiple YouTube channels with plans to create even more. Each YouTube channel, though, and content process is unique, which makes it challenging to establish a universal workflow. Initially, I recorded this course to give my producers an outline that they can follow to build effective processes. But let's just say the traditional workflow wasn't the best fit for them. To overcome this challenge, I develop a versatile workflow centered around click. This tool allows us to manage multiple projects effectively from commercial work to YouTube channels. While we have tried out other tools such as Smart See, Notion Airtable, ClickUp has consistently provided the flexibility and efficiency we need. This course is designed to help you adopt our proven methods to fit your unique projects, ensuring you can manage any content type with confidence. This course isn't just another basic click up tutorial. You can find those in my previous videos. Instead, I'll share our experiences and strategies to help you build and optimize your own workflow. Whether you are starting a YouTube channel or managing content for your small business, this guide is tailored for you. Templates are a good starting point, but knowing how to customize them is crucial. Here is what we will discuss in the course. Understanding the complexity levels of different projects, recognizing the strength of popular tools, the difference between data management, project management and documentation. A real world level one example using AI to simplify the starting process, a level two example, setting up a workflow for a video podcast show and basic automations to enhance efficiency. 2. Setting the Foundation: Essentials: This course, I'll guide you through creating your own content pipeline from scratch. The goal is to equip you with the knowledge to make the informative decisions about the tool you use and to understand the underlying principles of effective workflow management. We won't focus on providing a one size fits all template. Instead, we'll dive into the decision making process, helping you tailor your workflow for your specific needs. Maybe Click up is fine enough for everything. Maybe you want to use notion. But by understanding the strength and the weaknesses of those different tools, you'll be able to adapt and optimize your workflow efficiently. We currently use click up and Airtable most frequently, but our journey has involved experimenting with many tools. And if I mean many tools, Yeah, I mean many tools. Let's explore strength and weaknesses of the main tools we have used to make the best decision for your workflow, it's essential to understand the basic of each tools. While my top recommendation for versatility is notion, the principles I'll share apply to any tool. Not just click. Choosing the right tool depends on your specific needs and understanding the core features, and strength of each option is crucial. It doesn't matter if you run a film production or an agency or You just want to produce content, and maybe you just run your YouTube channel. There are three critical categories to consider. Project management. This involves assigning tasks, setting deadlines, tracking processes, and facilitates the team communication. It's the backbone of managing any project efficiently, data collection. It's about organizing and managing data such as potential film locations. Talents, and other resources. Effective data collection tools help you filter, view, and manipulate data to suit your project needs. Documentation. This includes writing scripts, developing ideas, and documenting processes. Good documentation tools allows you to structure and format your writing in a way that enhanced clarity and productivity. Here is a list how I would rate those tools from data management aspect, project management and documentation. So you can just take a screenshot and we go from there. Airtable. Airtable is exceptional for data collection. It allows you to efficiently gather, organize and manipulate large datasets. However, it falls short in project management and documentation capabilities. Notion is a robust documentation tool. It's versatile and user friendly for writing and organizing content. Notion is good at data management and project management. Though not as strong and specialize in those tools in these areas. SmartSe combines features from both ClickUp and Airtable. It's strong in data management and project management, making it a well rounded option. However, it doesn't excel in documentation such as Notion does. Click up cals in project management. It's designed to streamline tasks, assign team communication and overall project organization. While it's decent for documentation, it doesn't match the specialized capabilities of notion, and its data management capabilities are its weakest aspect. For data management, Airtable is really our top choice. It efficiently handles large volumes of data, making it ideal for collecting and organizing extensive information such as location scouting, talent databases. It doesn't matter if you have 30 or 50,000 records, it can handle it quite easy. For project management, click Up stands out. It's really built for task assignment. It's also great for communication and project tracking, making it the perfect tool for project management. We've found that click up allows us to maintain clarity and efficiency in our workflows, which is critical for managing multiple YouTube channels and commercial projects. While Notion is literally all in one tool. There is one core strength. Notion is exceptional for documentation. Click documentation features are for us fine enough, and it's integration with our project management workflows makes it a convenient choice. So let's dive in and start building a workflow that works for you, leveraging the best aspects of the tools available to create streamlined and efficient production pipeline. 3. Understanding Complexity Levels: Start from the very beginning, understanding the structure of hierarchy of ClickUp, which includes spaces, folders, lists and tasks. This understanding is crucial for creating an efficient workflow. And yes, it is really, really important. Spaces serves as the overarching container for all projects and workflows. Everything within a space can be seen and managed collectively, folders, subdivisions within spaces, used to organize related lists. Folders helps to group similar projects or phases of larger projects. Tasks, or I call them items, the most granular level, representing an individual work item within a list. Tasks can have subtasks, attachments, commons, and action items, and many things more. Okay. Let's just do one example. Content creation could be the space, and it contains a folder, feature film production. That contains a list, pre production. And inside this list, we have a task Task one. This is just an example. In this setup, Task one is nested within the pre production, which is inside the feature film folder, all under the content creation space. I hope this is clear so far, but don't worry by showcasing some examples, it will be more clear. But again, this is the fundamental, this is something that messed up basically a lot of our creation and by just applying any template. Well, it can work in the beginning, but Yeah. Let's just start trying to understand really the hierarchy here. When setting up a click up structure, aim to keep it as simple as possible. Again, as simple as possible. Really? This one number one rule. Complexity can be categorized into three levels. At least this is how we teach it. Simple, medium, and high. This helps us already to categorize what and how we should build it. We must understand what kind of project we have here because we tend to just take a template that maybe is best for category medium, but indeed we might just need simple, use case one, simple. This is level one, and I assume if you are a content creator, this might be enough. We do not need medium or even high, but we need to understand the differences. Use case for projects with only a few variables. If you run a podcast with the host and a guest where each episode is a single item with a few subtasks, then you want to use level one. How would it look like? For a simple podcast production, you might create a single task for each episode. Within this task, you would include a sub task for scheduling, the guest, preparing the question, recording the episode, editing, and publishing. This keeps everything streamlined and easy to manage level two medium projects with more variables, a commercial shoot with multiple locations, talents, and crew members is a medium sized project. But if you run a podcast, again, it's simple, you have only a couple of variables. That's the difference. For a commercial shoot, you create separate items for each stage of the project, which you can then batch into different stages. For example, pre production, production and post production. Inside those stages, you have tasks, such as script writing, storyboarding, location scouting. Inside of production, you could have tasks for shooting, scheduling, and crew member assignments. And for post production, you could have lists such as editing, color grading, and final reviews. This helps to manage the difference faces and ensures that nothing is overlooked. But to be clear, we do that also because we are assigning maybe multiple members to multiple tasks. So that means that One task is really dedicated for one member. This is really just for a few people out there, and probably none of them are watching my course here. But if you shoot a feature film or you shoot a very big documentary, then this is what you want. Level three high. A folder, that's called feature film production might contain lists for development. And inside those lists, you have the tasks for concept, development, script writing, budgeting, pre production, and so on and so on. Or another example is if you are filming on multiple location, you want to create sub lists for each location to manage crews from different countries or cities, and you want to schedule it maybe separately. Okay, but here's the thing. A lot of projects fall somewhere in between the complexity levels. It's not always clear if a project is level one or two or maybe somewhere in 2-3, and sometimes you need a mix and match different elements. That's That's where the challenge begins. For example, our show off the record, which we currently producing, we initially created several lists. But after some time, it became clear that the lists were getting too large and unmanageable. Each list had around 16 items and managing multiple shows at the same time led to confusion. So we rethought our entire pipeline. Our goal now is to compress everything into one subject or theme. The idea is to produce one subtopic per month, resulting into three subtopics per subject or theme. This means each month, we aim to create one small documentary, and each week, we aim to interview two people and post these interviews on our channel. These are fundamentally different tasks, but when we simplify the process, it becomes manageable. We had to figure out where it made sense to create a list and what to include in that list. Let's break it down inside of clicker. Create a folder. Off the record 2024. This folder will contain all our lists for the year. Create a list. Each list will focus on one big theme. That's it. For example, our big theme for the next quarter is addiction. Create a new task and name it appropriately. We have two task types, guests and topics. We aim for 24 guests and three main topic. This could be too much for one list, but if we keep it simple, it will work. Now we have to outline the tasks. Start with a task name. Use an open bracket to denote the name of the guest and the topic. This provides a clear starting point. In the past, we have used ID records for each episode, but this approach was not dynamic enough. We decided to remove ID records and only include them after the episode is done to keep things simple, setting up the views. Understanding the views is essential. We need to consider the calendar view and list view. In our case, we don't really need the activity view, but we keep it there. Even the task name and the list name are important starting points, description and common elements. The first thing to add is a description. What are common elements that everyone working on this project needs to know. For commercial, it might be the target date, the budget, the project name, the agency name, the client name. But for our theme addiction, it's a bit different. We need theme description that remains consistent. For example, if we're talking about addiction, and we have multiple guests who are addicted to different substances. The central theme remains the same. We add this description to ensure everyone is on the same page, subtasks and action items. The next big question is, when to use subtasks and when to use action items. There is no right or wrong answer, but there is a rule of thumb. If other people are involved, use subtasks. Action items are simpler but limited. You can't open them. You can't create subtasks within them, or you can't attach documents. Subtasks, on the other hand, allows for more complexity and details. For example, if we create a task called scheduled guest, we might have a subtask for each step involved. Contacting the guests, arranging the interview, sending a contract, et cetera. Each subtask can have its own description, priority and tags, templates and SOP links. To speed up the process, we can copy templates and descriptions that include SOPs, links or other relevant documents. This helps to maintain consistency and provides clear guidance for everyone involved. For example, in the task description, we can include a toggle list that links to important documents. This keeps the task description clean and organized action items for specific roles. This might be specific, but in our show the show owner who also shoots the soot has specific action items like preparing questions, scheduling guests, and checking equipment. These action items are divided into stages, pre production, production and post production. Sub tasks can be created for other roles involved in the production process. Okay. So here a conclusion. The key takeaway is to keep things as simple as possible. Use the right level of complexity for your project. Whether it's simple, medium or high and always be ready to adjust and optimize your workload as your project evolves. So we could have used more subtasks and completely skip the action items. Which would also work. But again, the philosophy here is, keep it really as simple as possible. If level one is working, use level one. If action items are working, use action items. But then when they hit the limit and you need like a subtask, then use a subtask. If you need a list, then create a list for every project. This is the key takeaway that you have to remember. 4. Level 1 Example - AI Assistance: Starting with Helpers: For those who are asking like, Hey, can I just have please a template? I have something better for you. I've created this AI chat tool here that transforms any description into a workflow. Is it working perfect? Not really, but it's fine enough. It gives a great outline, which we can take and of course, enhance. Let's just provide it with some basic information here. I think it's fine enough, and it's definitely helping us here in a lot of things. So it's already breaking everything down for us. What views could we use a list view for task management, a board view view for the visualization of the workflow stages. Then of course, it suggests the tasks, the steps, and so on. Everything that we could build here, here a subtask breakdown. Let's test for another template. Let's say we want to create a daily stream for gaming channel. No other description here. Let's see what he provides us or she. Complexity level medium, giving us here the suggestion here, create a space and folder with the name of the channel and then folder daily streams. Inside this folder, we have a list view for task management, and we have here basically all the views for the list. And then we have the task management here, pre streaming, schedule it, game selection. He thinks quite complex here. Probably, if we would give it no more information, we just recorded, we do not need to schedule anything. We do not invite anyone. It's just like this simple, but it gives you already a quite good setup here. We have to think about the thumbnails, the graphics, the OBS settings, and so on. Understanding here the pre stream, livestream, post stream, publishing, and so on. Thinking really about all those steps. Which helps us really to get a starting point. This is not something that provides you with the perfect solution. Again, this is just the starting point if you don't know where to start because every project is different. Let's take this one here, really simple actually. What we want here. This one is quite good. Let's just take this one here. We need to define the views. What we want is the task name. This is good, so that we can then copy basically all those files here. Okay. Now, actually, we do not need Merro for this. We can also utilize click up directly. But again, this is just something, whatever tool you are using here. It's just like to write down what information you want to use. Here, this is quite good here, Tas statuses. I would take it. And then let's see what we have, and let's copy just some information here. This is looking good. So I have this one here. Okay, so now we are here inside of click up on the one side and on the other side, we still have Merro open. What we want is the interview name. And the original title. Now inside, we just want to attach one single SOP. Again, we keep it simple for this one. So SOP, and then here we go. That's it. One document that contains one simple instruction with a video and some login credentials, some links. That's it. This is the simplest it can get. But this is fine enough. Okay. And now we do not want to create subtasks, or we need our action items. Here we can create action items. For that, we can create a checklist, and call this one here. Production. Again, I would give it maybe another name, but that's fine. The first thing they have to do is download the assets, then they have to build the storyboard and then edit the storyboard, and then finalize the storyboard and update the Airtable base. That's basically it. For the status, we do not take the recommendation. We just take what we have here. This is our default setting. So we have in progress, ready to review. On hold and approved by head. So all we need here is basically them to know when they are done here, updated everything, check everything. They just put it on ready to review. And that's basically it. We have created our very first simple template. Really, the simplest template we can get there. Now, when it comes to the views, let's just do here some of those basic views. We have here already our calendar view. The next view we need is the board view, and we just need to set it up on status, which is by default, and that's it. Here we can then change the status, depending on the progress of this specific content piece, from to do to in progress, ready to review or is it approved by the head? Now, that's really simple and we can just create a template out of it, and this is how we do it. Inside this view here, we can just Save this here as template. Now, what we want is we change the due date, we leave it blank. Now what we need to do is go to the template here and save it as a template. And now we can just give it a name OTR stories. And here we go. Now we have the template. But pause here and let's dive in into a more complex scenario. And then we will come back later so that I can give you some ideas on how we can automate certain things. But that's a little bit too complex for now, So let's just take another view, another template, which we break down without the AI, but just from scratch, everything from scratch. Now, if that was too fast, the next one will be even a little bit slower here. Okay. 5. Level 2 Example - Building from Scratch: A Comprehensive Guide: This is maybe how your click up is looking if you are starting click up for the very first time. As you can see, I do not have any space. I do not have any folders or any lists. We are starting from scratch, really slow, everything live. So the very first thing, of course, is we have to create a space. It doesn't matter if we just want to create a list. We need a space that's a must. Here we can just give it a name, content creation. Now we have here basically different templates, which we can choose from We can also make the task status, and we can also define which lists and board views we want to have. It might be helpful to configure those and take the time. In this course, though, we will only cover the content creation pipeline. And also, as I've mentioned before, we will keep it as simple as possible. So here we just need the list view. We can include the board view. What we definitely want also here is the calendar view, and this should basically be it. That's fine enough. Inside of our task status, we have here already different templates, so we can check them out. This is pretty good for content. Open ready writing approval, reject publish, but we want to keep it simple. But this is a pretty good starting point, which we can then delete or make those decisions also later on. Our case, let's keep it, so we're going to apply this one here, and then we can make a decision on what click apps do we want? Do we need a priority? In my case, most of the time for content creation, really. We tend to not use it. Do we need tags? Not really, yes, in some cases, but for this purpose, we leave it off. Multiple *****? Yes. Do we need time estimates? Not really. If we are talking about real project management, then yeah, we are also using sprint. But again, we will cover only the content creation pipeline. So we also de select time estimates. We can say, Okay, this is fine enough, and this is what we want. Now we have our very first content creation space. And here we have our very first list. But I would recommend to create a folder. Like even if you run just one show or if you just have one pipeline, it would make sense. Even if you just run one show or if you just have one pipeline, it also would make sense. Maybe you then want to create folder for every quarter to keep it clean, or maybe you want to create a folder for every year, or maybe you have two channels. So by separating it through a folder, that would make sense. Let's create a folder and let's name it template. For here, we just create a folder where we store all our templates because at the end of the day, this tutorial is about creating your own templates. We will discuss two kind of templates. The first one, as we have showed in our real world example, off the record, one of our shows that we create. Here we can do the same thing. We batch this here through themes here inside, let's just rename this one here, and then we want maybe to include the quarter. Q two. 2024. Okay, now we have the list name. Now let's pin this view here, and now let's create one single task. Again, one task represents one guest, one task, one guest. To speed up the process here, we can just use this one, which is pre written and here we can just give it a task name. Now that we have give it a name, we can then create a description. Okay. And here is something pre written, which we can just copy and paste for now, and of course, we can adjust that later on. In the description, it basically includes all the important documents such as SOPs, but also all our connections through our airtable base, also our setup guide, our equipment checklist, editing guidelines, and so on. So basically every document that is important to complete this task is included inside the description. Why? Okay. Imagine you are working with several freelancers. You do not want to explain them over and over again how to get things done. You just include the documents, which makes the process easier. How can you create a document. If you are starting. The easiest way would be, of course, to go here and create a document here inside. But if you like to create a document inside your description, all you need to do is press this plus sign here, and here you can then go to DC and give it a name as OP for OTR. Now you have your dog and inside your dog, you could include all your instructions. Of course, you can then also create sub instructions or sub docs. Let's just create here SOP for OTR. This could be a document that is connected to OT R here. Now inside your OTR, you have sub documents. You have inside your SOP OTR sub pages, which you can then open and close and you can then create whatever you need. Here are just some examples. And again, those are just dummy SOPs. We are not using those. But just to give you an understanding for what we are using those SOPs. Here, inside your document, you can then create, let's just say SOPs for the specific show, which you can then categorize into let's say video production or marketing or social media. However you like, we will not cover on how to create good SOPs here. You can then go one layer below, inside the video production, you have, for example, an SOP for the video editing process where you can document the entire process, and then you can go on and do the SOPs for social media and so on. Now, why is this so helpful? Because inside your template, you can attach those documents when you have multiple tasks that are distributed across all and different lists inside of your click up base. You just have to update this single list here, this single document, Everything and everywhere else, the document will be updated. Therefore, you do not need to update here inside your description something which you then have actively to change all the time. But now what you need to do is basically you can now connect those documents here. For example, here, you have the detailed steps for this specific show. Here inside, let's just connect it by three times. Now you can connect the document that you need for this description. So now you have this document. And as I said, it doesn't matter if you change now something, it will be updated on every task that this document has been assigned to or attached to. So we go here, we can open it, and here we go. Let's create a subtask here editing. So SOP four editing and now three times. And here we can now attach only the editing video content here. Okay. So now, when you assign this to the editor doesn't see everything else, but just this one here. So when he opens it, he's focused only on this document and on this process. But how does it look like when it's done? After spending some time here, This is what we have built so far inside of our task name, the name of the guest and the topic as our main template here. So that means here inside, we have connected our documents. We have connected basically everything needed, and we have created subtasks and checklist items. Let's go over those single items. This is the default view of click. This should look something similar than how it should be on your end. And here is how we can change the default view, which I prefer more because here it's like two cluttered to messy. So here under settings, we can then go to section tabs and enable this one here. This one is clearly separated. The details, the subtasks and action items are now into tabs. This is the idea behind the template. Inside of our subtasks are tasks that are mainly done by other people. That means like those tasks are distributed to specific freelancers, and therefore, we created those subtasks that contains their own description with their own action items. But Inside the action items here, we have checklists that are for the main responsible person for this task. It's basically things he has to think of. It's more like a reminder list here. He has basically just check them off to make sure that he didn't forget anything when he's working on the project here. So here inside, we have divided the action items by stages. So everything that he needs to think of when he's doing the pre production, then the production, then the post production. Again, those are just for the main person responsible for this task. Inside our subtasks, though, we have different action items for different freelancers. This is how it could look like when we, for example, open the guest request, Then this task will be assigned to another team member who's responsible to look out for a potential guest. Here he can find how he can reach out to them, and here he can find a database of already existing guests, but also a database of people he could reach out to. When he's opening this base, he is right into the airtable base that contains hundreds and thousands of records of potential people. As we can see here inside, we do not have any subtasks. Why? Because we keep it as simple as possible. If I'm mentioning it now, the fifth time already. Again, I want to emphasize on this one, keep it as simple as possible. We could, of course, create another subtask and another subtask inside a subtask, and that can go forever. But then it's also hard to keep track of all those subtasks. Therefore, we just create action items. First, and this are the checklists that the person who is in charge of Getting those people into our show has to do. He has to post social media posts on different forums. He has to create threads and read it. He has to write people based on existing posts. He has to contact people on existing shows. For that, again, we have different bases where he can just check. Those are the existing shows that are our competitors. Maybe we want to reach out to those guests. We will not cover it now here. But here we have basically a checklist, which is again divided into segments. Okay. Now we have 24 possible guests. Now we just have to create topics, and now we can save this entire list as a template. So every time we have a new theme, For a new quarter, we can just take this here and start from here. Of course, we can change the status here and make the status as the starting status to do. Now, let's start talking about what views we have here. Now inside this calendar view, we could take the guests that are scheduled for specific days, so we can just drag them and basically create here, let's say, for every guest, we have 2 hours. And now we could start and schedule those guests here inside of our calendar view. Okay. Now, We could continue and do this here across the entire month. But I think the purpose is clear. We can use the calendar view here to just have an overview of what's going on and we move on to the next important view, and that's the topic chat. Why is this so important? Because here inside, we can talk about the specific theme only. Now, this might not be useful if you are having your board where you are alone or where you just have someone else. But if you are working with multiple people and you would like to discuss something outside the specific tasks, you could, of course, write here with someone. Hey, do this, also, please. But the problem is if this comment is assigned only to this task. But what if something completely is changing? For that, you have a topic chat. This is amazing. Inside the topic sheet, what makes it so powerful is that you can assign documents and tasks. And this is amazing because let's say you are collecting ideas or something has changed and now you would like to include a document. You can just include whatever document you like. Here for example, you could include this random document here. Or you can assign someone or you can just assign or include a task. Let's say we include this task here. Now, we do not have to look and we do not have to figure things out. We can just go and click to the task, and now we are inside the task. And here we could, of course, connect it to other documents as well. I would recommend using this view for the editing stage because most of the time, the editing takes more than 2 hours, obviously, and some editing processes takes one to three or four days for our episodes here. Therefore, we can then display and lay this out here because we have only a limited amount of editors. So here we can really assign the editors to the specific days here. Now, this is a view that's I think only for the paid version. So if you are using the free version, this is what I would do. Go to a board view like this here. Change it by due date, so here you can change it. This is how it looks like when you are using it natively. But here, what you can do is change it to due date. Now what you can do is assign specific editing tasks for specific days. For example, you want this one to be edited until tomorrow, so this is always the due date, not the start date. Therefore, I would really recommend this view. But again, this is for the free version, I think that's the best what you can do. Of course, you could also utilize the calendar. But this one for me, at least, makes it simpler to have an overview here. Now you can basically assign the specific tasks for specific days and here you can have a great overview of what's going on. Okay, I hope this was helpful until here. Okay. 6. Automation - Final Thoughts and Next Steps: Not cover all the content types, and there are so many different possibilities, but I hope until here we already have a basic understanding on how we could create our own content pipeline. Now, I want to talk about a more unique content pipeline that we are currently creating. I will not discuss this, but if you are interested, let me know and then I can cover the automation process more in detail, maybe in the next courses. We have a channel where we just interview guests. And we let the automation turn those videos automatically into storyboard stories. How does it look like? So here is how it's looking like. This is a video before. So as you can see, this is just the interview. Now, this interview will be transformed into this storyboard content, almost automatically. And yes, there are a couple of steps involved, but basically from the transcription to the finished video, it takes around 30 minutes manual work. That's it like the script, the voice over, and also the shot list for the storyboard will be generated automatically. While ClickUp is our project management tool, we store everything inside of Airtable. Now, Airtable is more than just a database. We can connect it with YouTube, that it can basically get the transcription automatically. So we can see the transcription. But also we can get the transcription. With the timeline and timestamps. We can generate them from those automatically summaries, topics, title, social media posts, and so on. Now, this year looks super confusing, and we have, of course, another view where it's way better and easier organized. But it's also allowing it's generating automatically an update. For example, it takes the view count and the likes from some of those videos and refresh that every second week or every month, it depends a little bit on the channel, and now we have an overview for our videos. Now, the great thing is we build an automation where we just have to press one button. So when we press this little button here, it triggers something and that generates basically a whole chain reaction. So we are using multiple automation tools such as make.com, which is our favorite automation tool, but we are also utilizing the scripts that are built in inside of Airtable. But then we are also using active pieces. I'll just give you the understanding that when a new record has been created a voice over by generating with a prompt will be generated automatically, and then also an automatic translation into Tagalog, storyboard, and then we save the files. So this is just one automation pipeline that turns now those interviews into those records here. Again, all automated. So now the editor has this list that he knows about. And here he can just download the shot list, which has been generated automatically, and he can see the voice over script. And when he download the shot list and upload it to this tool, and once he's done, he just needs to upload the zip file. Why do I mention all of this? Because We have this interview that has been turned into this storyboard. But there is one missing thing that we can start to build. What we want now is to create an automatic task inside of click up. I want to connect Airtable with click up. And how are we doing it? Currently, this has been done manually. Because this channel has been just there for a week. And we just wanted to test out if this is working or not. So the automation process was not really the priority. But I'm going to show it here so that you have an understanding how to utilize automations and what is possible and what not. So that we can make sure that we bring in the best tools possible here. The first step I want to do is once a record has been completed by the AI and everything is done inside here, inside of Airtable, I want this basically to be reflected also inside of click up because then the editor could say I'm done and we could give them feedback, and that would just make it easier. The easiest tool would be Zapier but make.com is a little bit cheaper and you have a little bit more flexibility. So I would highly recommend using make.com over zap here. And if you want to save money and if cost is the most important, then you should look into active pieces. That's the cheapest from them all. The very first thing in connecting those apps would be create a starting point, that can be through a web hook. Now this is quite technical. Let's keep it simple for now. Let's just go and grab Airtable. What we want here is to watch a record. Here, we just have to select now the base, the right table, choose the trigger field, and we have to choose the view. In our case, we want to choose all OTR episodes. And we can limit this one here to ten. The goal is to upload maybe two or three videos per day. Regarding the limit, this is up to you, I'll leave it here for now on one, and then later on once we know the automation is working, I'll increase this and put a higher number here. But generally speaking, I would rather recommend to create a webhook, but for this story, it's a little bit too technical. So I'll just choose from all. And now, what we are basically saying, Hey, if there has been a new record inside the space that has been triggered before already, then please create also a task inside of click up. Now we have just to choose click up. And we create a task. Here, we have to select, of course, the right workspace, the space, the folder, and then inside the list. We do not need any parent task. For the task name, which can just leave it like the original name from Airtable. But here's the problem. This whole course was about how to create a template. Now, when we just use com, we cannot unfortunately apply any template here. But don't worry, we will cover that as well. That's all we can do from here. Let's see. Very simple automation here. Let's just test it out as we have done it before here, only one. There is a limit. Let's see if it's working and it seems to work. Let's see which episode has been created inside of clickup and here we go. We have our new task created. What we want here, of course, is to create and apply a template. How are we doing it? This is something we have to do then inside of clickup. So the idea is simple. Every time a new task has been created, we then apply a template. Now, this is super helpful, and this is something you can apply for everything as well. All we have to do now is go to automation. And create and add an automation. Here, what we want to look for is every time when a task has been created, task or subtask has been created, we can just leave it. What we want then is to apply a template. Here we have our template that we created just in the beginning of the course. Let's just choose this one here. And for now, we are using this template. We have created our very first template. There are so many other things we can do with automation, which I covered also in the previous video, we can create email automations, every time we uploaded an episode, then send an automation to a guest. Pay or episode has been uploaded or we want to update status. There are so many, I can't cover them all here. But let's just test this one for now. Now, let's just run it one more time and let's see if all the automations are working. Here we go. One automation, and there we go. As you see that has been basically created. Now, the automation has been working, and one template has been applied. Here it moves from to do to in progress, which we do not like, so we can adjust the template, but we have the checklist. We have the SOP, and that's great, because this is working, and now we just have to adjust the template and then we run it a third time. Okay. So this is what we have created before, and the reason it put it on progress was because it was set on progress. But now, let's just change this one here into to do. Add this little thing here. Again, this is something we need to refine and to redo and to improve. But just to make sure that the template is also working. Now we want to save the template. Update existing template. Okay, now we have updated this template. Let's see for the third time. Let's run it one more time. Here we go. And here we go. Perfect. It's working. We have an SOP that we can just click on dummy SOP here, but it's fine enough for now. Then we have our checklist for the editor, and that's perfect. Now we can increase the number here and put the limit a little bit higher so that we can really work on multiple projects at the same time. Let's just put it on ten. And change this duration here. I think once per week actually is enough at 3:00 A.M. In the morning, we can update our click up days here. Looking for new records inside of Airtable. Let's run it one more time. So now we have set the limit to ten. Now we should see here quite a lot of new records. One, two, three, four, five, six, seven, eight, nine, ten. Here we go. It's working fine. Now this is something we can do on scale. We could do it one more time, just to double check and tripple check if everything really is working. As we can see here, the templates are also being applied one by one. It takes some time on click upside here. But when we refresh it, we should see all the applied templates. Now, this is a really basic automation. I hope that was helping to get the basic understanding of why we are using airtable and some basic understanding of make.com and also click up when it comes to automation. If you want to know more on how to automate things, we can create another course for that, but this is a little bit too advanced for the content pipeline itself. I hope by now you have more than just a basic understanding on how to create a pipeline. So we have discovered on how to set up a pipeline using level one. Again, level one means one item, one project. Level two means one list one project. That's the difference. We haven't talked about level three because mainly the focus here are for people who are applying level one and level two type of content. You can always have a look into different templates. Try to understand them, but take the time really to create your own templates. Take the time to create your own pipeline because ultimately, that saves you more time than just applying any template, and then messing it up over time where it gets more and more complicated. Please give some feedback. If you want to see specific things, we are now starting to record more tutorials, hopefully coming soon. Thank you very much and see you soon. Okay.