Okay, so, uh, let's get started. Uh, welcome to today's webinar that is on the topic of how to make your invoice process a bit easier. Uh, with the help of AI and not just that, we are going to look at apps, uh, because I know that there are a lot of invoicing apps. We're going to look at those, and then we're going to look a little bit at how to enhance further, uh, and see what the apps can do. But as you can achieve with the help of Make.com. And additionally, we're going to add a layer of very trendy AI on top of that. So, uh, uh, it will be a little bit of integration with, uh, GPT. Uh, that I'm sure that many are familiar with. Maybe some have not used it in the API yet, which is fine. You're going to learn that today. Uh, but I think that everyone at least have maybe went to the GPT website and tried out the mod there. And of course, that's, uh, open up a lot of possibilities, uh, when it comes to drafting stuff for a human to just review and then, uh, click. Okay. All right. Um, so we will start with actually having a look inside of monday.com Well in front of us here. Uh, we have the, uh, monday.com app marketplace, where you have to search for invoice because we can see that there are quite a lot of, uh, app filter that helps out with the invoice automation. Many of them are connected to, uh, uh, quite popular, uh, um, uh, bookkeeping on the invoice system such as QuickBooks and, uh, Xero. Uh, I'm not sure how popular uh, Pesaro is, but it seems to be actually downloaded more often than both Xero and QuickBooks. Uh, which surprises me. Uh, but it could be that these shops are newer as well. Uh, at least one or even five new in the tag. Um, you also have another QuickBooks app here that is actually added a choice that might be even better if you're looking at, uh, integrating with QuickBooks. Uh, on top of that, we have one of my favorite apps here, Docugen, that creates PDF. And of course, it is possible to create a PDF and send it out as an invoice, but that will not help you with the bookkeeping part of it, which I think that both Xero and QuickBooks do in a whole lot of manner because they are integrated systems where if you send an invoice that's actually being, uh, accounted for as well in your books, uh, in a, uh, manner according to your local laws and regulations. And I can see that also that Eledo over here that I have, uh, tested out as well. It's, uh, quite nice platform. So Docugen is quite easy to use. Uh, but Eledo opens up for even more use cases. Uh, generally, if you want to tailor the, uh, PDF that you get out, uh, even more than Docugen permit. So it could be an option as well. Uh, except for that, uh, we're gonna use make today anyway, which you can see here. I have my Make scenario here in front of. And the good thing with make is that, uh, make also connect to quite a lot of other, um. Uh, other services as well. So actually, if we just open a new tab here, go to Make.com And we can quite easily have a look in the apps and services section. And if we search for invoice here. You can find quite a lot of invoices such as Zoho Invoice. I know that many use the full package. Uh, I haven't reviewed the rest of these, to be honest. Uh, but I know also that, uh, the if some, uh, category here, which where one of them should be about finance, right? Okay. Maybe not. Anyway, I know that, uh, for Swedish, for my Swedish audience, we have the quite popular, uh, Fort Knox, uh, system integrated with Make, and it works really well. Uh, and in this one, we can, of course, also, uh, create invoices. So let's see, we have retrieve an invoice. Uh, we have updated invoice. I know that we have create invoice as well somewhere. Yeah. You can find it now at the moment. Um, apart from that, uh, additionally, for the Swedish market, we have, uh, with my accounting. And, uh, if you are lacking your service of choice, then just have a search in Make. And if you're quite advanced Make user you can even create your own connections, which, uh, we have done at Omnitas, uh, before, for example, with, uh, economic in Denmark, Danish service and others as well. So have a look if you're unsure. Uh, so let's go back to the webinar page. So. After you install an app. Uh, probably what you're going to notice. So we circle in here again. Ah, I was not in the app marketplace. Here we go. So search for Invoice. And, uh, what? You know, if, if that many of the, if they require you to have a board. So if you click on how to use for any of these. Okay. This one did not seem to work. Okay. They didn't allow it to have their help page embedded. Uh. This one did not have a help page at all. Yeah. That's a, uh, some homework for the app developers to fix the help pages, actually. Uh, but, uh, I know that usually how it works is that you have, uh. Uh, yeah. That's. You can create invoices. Uh, um, and you can connect to clear billing here, for example, in theory, invoicing. Yeah, that's the one that I was thinking about. So, um. Uh, check it out and try it yourself, because. If I'm going to use it now, uh, then I will need to install a bunch of stuff that I didn't intend for this webinar anyway. Uh, but, uh, in the end, if I have a client to use with. The Xero app from Luxitech Then I know that they have a recipe for, for example, uh, where the main item is an invoice and then a sub items are basically or invoice lines, right? Um, so what we see in front of here is one of the very basic board. Uh, and typically if you, you have to have that app installed, uh, and then maybe it will look something like this. And then you create a new invoice, you add an item, you have the price, add a description. Uh, you had a quantity unit. Uh, maybe a discount if you want to. Uh, and then you get the total. So you can display the total in a regular way, as you do in any monday.com board. Um, then you can usually just click on send to whatever service. And then inside that service, there could be automations to send it to the client. Um, and you will get back a PDF. So basically that's how those apps usually work. Uh, and then of course, you can also connect it to any clients as well. But the thing is that, uh, that's quite tedious, at least if you're, uh, working with the invoicing customers, then you have to, you know, manually. Uh, look at. Okay, what have we done for this client in my production space here? Okay, so we did for green screen. We did this project where we have, uh, not started yet. Uh, except that I know, uh, and that these are done, for example. Uh, but we have these left, so I know that I can, uh, um, invoice roughly a third of the project. Uh, if all of these are equal in, uh, dollar amount. Um. Or pound, whatever you prefer. But right now, I have a dollar fine in front of all my, uh, numbers here. That indicates that it's about money, right? Um, and then you go back to the invoice board and maybe you say, okay, this invoice one is for the project are what was it called again, I forgot. And then you go back to the portfolio system again, okay. Of course you will have this open in two different tabs. Probably. But still. This is how your eyes Work, right? You fetch information from one of the tabs and then you bring it over to the other one. So basically manually moving information from one word to another, uh, step by step. Uh, and also maybe you want to check in the account here to see, okay, who should I send it to? Even I should send it to, uh, David Johnson. Uh, and maybe I also want to check. Okay, maybe we have another deal upcoming here. Uh, then I have to maybe take that into account and not, uh, so I marked the invoice to say, okay, this is about the probability that we already have. This is not an accidental invoice that we've done ahead, uh, when we haven't found the deal for the next project yet. Uh, so then you can have a look here at the opportunities as well. But, uh, basically what you're doing is that you're flipping between a lot of boards and. Maybe not ideal. Uh, so that's basically your situation, right? Um, that you're basically working manually with, uh, doing all that. Uh, what we're going to do today is that instead of doing it manually, we're gonna have to fetch the data from the project system. In this case, the portfolio management board, which is built of one project, is one row. I know that, uh, in some PMO systems, you have external boards where all the tasks are. But in this quite simplified example, I have just put all that off, uh, as a sub items of that. On the Project row itself. So you still get kind of this high level overview where you can see which are done and not star, that you can see which time span, how much expensive so far, and so on. Uh, this project board is also connected to an opportunity quite always connected to an opportunity because in this, uh, example, uh, of how a company could look like and if, of course, could be quite, uh, vary a lot between each company. But usually what you have is two parts. You have a failed part where he sells things to people, and then you have a production part where you actually start doing stuff that's you have to find a deal for. And this is the, uh, doing stuff part, uh, for the CRM, we have a connection to the opportunity that sold the project. And in this one, just, um, we have, uh, a project brief. That carries over, as we could see with a mirror column earlier that carries over to, uh, the other board. Uh, I think it's quite relevant for the whoever is going to lead the projects to know the brief of what's it going to do. And the opportunity in turn is connected to a account which is in a third ward. So basically we have a three part chain. We have, uh, project that is connected to an opportunity that is connected to an account. So I made it a little bit more complicated. But this is actually, uh, how many systems are built up. So it's not unique, but I made it a little bit more complicated because many have this kind of complicated relationship between the production and the CRM space. Uh, so that way I can show you a little bit on how to fetch data from several levels away, which is something that even experienced developers have a, uh, sometimes a difficulty or to grasp, uh, fully, uh, because the connect column is, uh, not easy to work with unless you have a little bit of monday.com experience. Okay, so no direct connection to the client. Instead, there is a connection to the opportunity which is connected to the client. Very important to remember. All right. Uh, so we, uh, at least I for for this case, I want to be, uh, situated here in the account section. And I want to say create an invoice for this date and fetch whatever, uh, information that, uh, we, uh, uh, factual information for, for what we've done from the portfolio management system. And what we can see here is that, uh. We could in have two or even more projects per client running at the same time that need to be invoiced. And we don't want to send one invoice per project so that the client gets two invoices. We want to merge them together into one invoice. Which is why this is actually the draft if actually, uh, created from the account base. So all you do in the draft, they say that. Okay, I want a, uh. Uh, drafts invoice for the last of January. Uh, and I want it for that client. HSBS. Uh. And of course, that requires a little bit of, um, information to be populated in the account section. But I assume now that you have a good enough CRM. If you don't, then look at one of our other webinars where you can build a CRM, uh, to actually have this quite populated as I have here, I even have a special, uh, column saying, okay, where should I send the invoice to? Should I which python should I send it to? Because as you can see, there could be several contacts, uh, for one account. And then it could be good to have a, uh, different, different column to show. Okay. Of the people who should I send it to? Or should I send it to a third party? Even who should I send it from? So it will fetch my name from here? Uh, not the picture. Fortunately, we don't need that to be sent over. Uh, we also get actually the, uh, invoices that are currently on that client. We can feed them in here so we can see the total that have been invoiced, total that have been paid and paid until the left been overdue. And that is due to when we create a draft, it automatically connects directly from the account. To the draft invoice. So if I want to see here vet labs, for example. So they had a. Yeah. They have a item card with general, uh, company information. Uh, some connections to contacts and so on. But I want to see, when it comes to invoicing, what's happening with the money that we're supposed to get for this. And we can see that are actually, there was a invoice sent from my colleague Julia here, and it's overdue. And, uh, we can see that the amount overdue is 585,000 and so on. So we can see a list of invoices actually in this view, uh, as well as create a new invoice if we want to from this view as well, which is quite nifty. Uh, unless we want to batch create then you of course select a lot and then you select create after selecting a date and then you select the create. Um, which could also be a good idea, but then you have to leave. The I-10 quarter view, which is good for looking at One single company at the time. All right. Um. So when I click create here, what I want to see if that's there is a webhook. There we go. When creator off the invoice, you change it to create. Send a webhook that's being sent to my make scenario. Uh, so typically I make scenario will look like this. And I think that most people know that. Who is on this call. And we can see that there is a queue because I have not put the scenario on. But if I have, uh, activated for a second to and processed the old data that I have sent over. Uh, then we can actually see, uh, that it features are now got an error. I was supposed to get an error later to show you how to solve it, but. Okay, but then it would create a invoice over here and, uh, populate that with, uh, what we were looking at. So let's dive into that bit directly now. Okay. Now we have create. So what's happened now? Was that the, um. Uh, I had accidentally selected the a very old ChatGPT engine, so let's directly change that to. Okay, so that was the only one that I could choose, which is quite odd anyway. Um, that is quite recent that I have depreciated it. Uh. But, uh. Shut up. Still have quite a lot of other model models that currently are not showing in Make it seems, but, uh. For example, they have the GPT. For some. But it could also be by a different connection. Let me try this one. Nah. Okay, that's not much true about that. Um, but, uh, we can see that the webhook. It arrived here from monday.com of, uh, we expected HSBS, which is the one that I triggered from monday.com. We can see that because it's staying on creating instead of automations to switch for demonstration purposes here. Then what happens is that we actually get the whole row of that client. Uh, in order to find out, uh, what opportunities are connected to it. Um, in this case, we can see that that is one opportunity, uh, connected, uh, which is, uh. Now we can only which if we can be in monday.com instead of from there. But let me have a look. Ah, there we go. And HSBS deal this time. Uh, and so then we have moved one layer in the chain from account back to, to, um, opportunity. And then we're going to go to project later. But first on the opportunity we want to fetch the um, uh, project scope document because as you might remember, there was. A, um. Project scope monday.com Lock in here. Uh, that all of the contains a little bit of text. And I have put the shortest possible summary one sentence. But if, if ideally fleshed out a bit more to give a bit of context to chatGPT. Seems a good prompt should have the context. Uh, what kind of information is receiving? Uh, what kind of, uh, uh, um, output that we want and so on. So the context, uh, comes from a project brief summary. Uh, so what we do in the main scenario is that we offer, we fetch the opportunity or the opportunity if. Then we get the, uh. Document itself with a specialized GraphQL, and this is quite nice as well. So this is based on monday.com's new API version, the 2023 ten. Even though I did not select it, it is based on that. And you could do it also actually in some of the old versions that you could get a document. And then for each of these blocks in a documents and a block or object. But an object or a block. That would be, um. For example, here is one block or object that you can move around like that. Uh, so. Quite often it is a. Uh, my, uh, cursor got stuck there. Okay. So quite often. It is a, uh, paragraph. And you can even do some quite cool regex here for a standardized document like this that you between each, um, block, uh, between the block summary and specifications. You should fetch everything, all the paragraph, and then you can fetch all of them as summaries, which would make sense in this case. But for this, uh, webinar I have made it more, uh, simplified. So we iterate on all the blocks. We filter out the block, in this case with only one block, one paragraph. Uh, but as we advanced, we can get more that we're interested in. Then we parse out because the block it will give us, you know, the alignment or the text. We again give us the, uh, delta format, uh, whatever that is. But what we are actually interested in is the text itself, which is inside the insert, which is part of the delta format. Okay. So we, uh, we need to parse that out of the Json and then put it in to a variable. So this variable with which we call summary we have to do development blah blah blah. And then we fetch it. Directly to have that with us right now when we're collaborating with. Okay. Um. Off the dots. It checks that the opportunity, uh, actually have a project connected to it, because if we haven't started any work, then it would make sense to create an invoice anyway. So if we don't, if it doesn't have any project connected, then it will actually give a error message to, uh, monday.com. So it will show up. And when we are in an account page, this will just take a second and it will show up. In our update section. After user feedback as an error message in here. And that is one way of sending, um, error messages back to, uh, monday.com. Uh, typically it's also combined with you changing the status to error. You have to make it super clear for the user. Or you can find it up here because the graphical parameters of a notification. So you can get a notification with the error message, but that's a lot shorter. The text that you it allows. And most people actually miss out on the notifications if they are not using monday.com a lot. So it could be safer to just have it here. It depends on your workflow and what people are used to in your system. Uh, when we check that. Okay. They actually have a connected project. Uh, then we get all the projects. Uh, in this case, we have one called Project Papa. And then on that project, we start iterating on the sub items and remember that the sub item on the project or the tasks. So they are basically, uh, all the things that we want to, uh, do on a project. In this case, we have the same for all of them. They are quite general, uh, some kind of construction company that investigate the site and contacts, uh, from stakeholders. We have, um, development happening in stages and so on. But it could be anything that you could possibly imagine. And for Project Romeo, for example, we have, uh, actually progressed a bit on a project. So we're in the execution phase. We design development. So we have left the planning phase. That was previous, uh, we have a budget of 380,000. We have spent 2980. We have called them a little bit, uh, we have a lot of days left, but we have progressed a bit on the timeline, right when it comes to actual date. And so we want to invoice this project. Uh. A for f we, uh, for all are done, uh, tasks. And we don't want to invoice those that have already been invoiced. So we have that tag that we just automatically, with the help of Make. Uh. So next, uh, when we have found a task that actually we want to put in the invoice, uh, that is not invoiced. Uh, and actually, I'm going to put an ad in there that it's, uh, status should also be done. So I'm going to copy that text. And, uh, date of. Oh. There we go. Status text equal to Done. Uh. Then we're gonna ask ChatGPT on elaborate on the topic name on a in a scripted way. The whole reason for that, if that's okay, we might have that off investigate site, but nobody, of course. Uh. Some stakeholder that is supposed to be kept informed, but, uh, doesn't have all the, uh, doesn't need to be involved all the time in a project. They could just have a look at the invoice. Okay. What have we actually paid for here? And in this case, investigate site, investigate sites. Well, what I mean, if we have three projects going on and they get the invoice together and we want each, uh, row here. To be, uh, one task, for example, or one part of the project. Then maybe we want a longer description. And that's where I had GPT confirm it can elaborate a bit on the task. And we are lucky because the other day when this actually worked, then I managed to create an item or two. Um. So let's bring one of them back. That actually had, uh, this kind of description on them. So. Okay. Let's see if we can refresh this page. Great. So this is a draft that was created by this scenario the other day. Uh, so when we have the investigate sites, um, for the, uh, very short description of, of that earlier, uh, we had a in, in Netherlands, uh, we had a sidewalk or something that needed to be fixed, uh, even shorter, the development and refurbishment of the sidewalks in the Netherlands. Okay, perfect. Uh, quite general, uh, probably going to be a longer text, but it's enough just to demonstrate this point, which is that it will elaborate automatically with that and investigate, decide that it will have a refurbished sidewalk facility and and a public square. Okay. It started hallucinating quite directly. So you have to see the first draft as i said and investigate the site, including determining what parts need repairing and how we should make sense. And then maybe when I read that if we are okay, actually when we investigate, um, we also, um, we also took some basic measurements. Of. Um, have faith level on the sidewalk. And maybe we have to remove the bit of, uh, where ChatGPT start started hallucinating so we don't have that, and then that's enough. So we had a draft and we just put a little bit extra on there. Uh, a quick review, but we avoided. Writer's block by having a suggestion. Probably just stopped. Quite nice. I do that a lot, which, I mean, it helps so much to not start and stare at the blank page, right? And the same goes here. So that happens for every line. And um, then we also fetch the ID of the invoice itself. Uh, that we have created over in this board in order to create the sub item somewhere because, uh, the, uh, actual, uh, invoice line. Get create that. Hmm. That's. You know. Ah, there we go. It gets created up here. So they actually invoice line with a, um, the main item in monday.com This one, it gets created with one, uh, with some information, such as the date that we fetched directly from the um, account line. We get also creates a connection here automatically with the ID to the account, because we fetch that earlier and we get the, uh, um, sent from and we automatically select that. For me, we go, uh, and actually we could have had a text value saying send to and so on. That depends a lot on the system that you're using, how your setup is in your bookkeeping and invoicing system. Because some people, they have the bookkeeping and invoicing system as the master and then have monday after slave. So basically the invoicing system, let's say QuickBooks, say that we have these clients. This is the client information. Uh, this is all it needs to know. And shovel that over the money. Or you could have a setup where you actually create the client registry from monday.com. So in monday.com, the salesperson enters all the information. And then when the sale is done, that it automatically, automatically creates a new client over in QuickBooks. You see the difference there? It depends on your approach, whether it's the economy department who creates the client info, or if it's the salesperson who is working in monday.com. Uh, I have worked with both types of clients. Um, and they both have their up and down sides. So that's quite unique for each company. You have to remember that. Um, when the, um. Uh overall item main item have been created. Then we immediately set that uh variable in modified that we fetch over here. And then we also create the first sub item. I did it quite lazily this way. Yes, I know, but what is important to know here is that we also create a, um. Uh, the, uh, text that we get from, uh, the author or GPT. We get that quite easily. You can see refurbished cyborgs, facilities, blah, blah, blah. You get that as a value to put in some money just like this. Um. And when you create this, you can also, of course, if you have a price list, you can connect that earlier in the scenario and automatically get the price in this case. Uh, I set the price manually for maybe 200. Uh, maybe you have set the price on the project. Then of course, it would make sense to actually take maybe a portion of this price based on a set of rules here. It could also be that you're selling, uh, number of hours and then you have an hourly rate. Then you could have an hourly rate, maybe on the account or on the deal. Uh, so the possibilities are quite endless on that, on how you get price in there. But in this case, I left it manually because anyway, you could batch select and or you could, uh, when it comes to construction, I have a hunch that maybe you want to fit the price of, uh, uh, a bit, uh, customized for each row, actually. So that's why I left the day. But for other use cases, uh, then it makes sense to just fetch the price from the entity that, uh, make that. I have seen some clients that have advanced setup where they have a deal board, whereas sold a deal to a person, and what are different prices depending on the role. Uh, and then uh, they fetch the time report from somewhere else and they attach the depending on, uh, the reported time, what role that was on. Then they fetch the roll price for that particular deal, and then they combine those to create invoice. So that is, of course, maybe the most advanced example I've seen. But yes, uh, it is uh, uh, there are a lot of opportunities that way. Okay, I'm just going to take a quick break here to see if anyone have any questions. Not at the moment, it seems. Okay, good. That must mean that I'm quite clear at explaining, and I take that as a compliment. Thank you very much. Anyway, uh, let's get going. Uh, next after the main item and the sub items have been created here on monday.com. Then we also aggregate all the descriptions into one text. That's what we're doing here. So we have for this project here, the description of the tasks. And then you also get the summary and the invoice ID, because we specify those as variables earlier or earlier in the, uh, scenario. And then you offer ChatGPT again in the context of this project summary. Then you have the summary, write the short description of 2000 letters or what has been completed in each project, or an input of the input in a professional tone. Yeah, okay. In the prompt, the tone is actually quite an important bit as well, no matter what portal ChatGPT use. Usually I have GPT four, which is fantastic at uh, picking up tone. So if you say professional tone, then it does quite a really good job. Then I give it the input. Um, and I also put the temperature. So the temperature is quite interesting if you put it high, uh, for example, one, which is the default email, which if uh, crazy, uh, then it will uh, almost uh, and uh, like it will almost for sure start hallucinating or making up stuff. If you put it on two, then it uh, zero, then, uh, it will basically have no wiggle room to interpret anything. So you will get quite a robotic answer. Um. And what? We can see that. Uh Make recommends uh if in at least in another module and it's 0.2 um. And the same goes for the other variables. I'm not going to get into that now, but I really recommend you to look at the top p and the N variable as well. They are very interesting. And I can and most of all you should try it out. You should tweak these variables a little bit each time that you test your scenario to see where do I hit the sweet spot? Okay, now it sounds like I want to. Or if you maybe you want to change professional tone to playful tone because you're selling toys or whatever, uh, whatever fits your brand, right? So that was the most important. Uh, of course, prompting is a whole science in itself. Uh, but the whole purpose of doing that, to collect all the information, all the tax information we have and give it give us a 2000 letter, uh, summary if to. Get. 2000 letter summary is to get div free text for the invoice. Now this is maybe, um. A bit long, actually, to be honest with you. Like, I'm not super happy with this outcome. And for this webinar, I was hoping also to generate another outcome together with you guys if and not look at this old example. But yes, the um, uh, project description, is first of all a bit stiff. Um. It. It's also hallucinating. It's a bit. You know, I want to say it right if a to me in a fluent text or something. Uh, so there definitely some tweaking that needs to be done in the, uh, uh, instruction here or in the prompts, uh, to be honest with you. But, um. That is also quite easy to change. Um, but anyway, so the whole idea is that in, uh, in, uh, the, uh. Account section, you either select your customer that you want to invoice this particular moment you select the date. You select. Create, or you select a bunch of customers and then click create. Whatever way you prefer the scenario. Go to the opportunities section and fetch the project summary from a monday.com doc, which in itself is uh, could be quite tricky with GraphQL because, um. It's something that many are not very used to when it comes to the API. Then it also fetch, uh, the task information, such as. Uh, what have been invoiced before and not, uh, what have been completed or not, and so on. And since we have such nice, uh, permission for monday.com, we can even, uh, lock or hide this column so that the people who work with these tasks, they don't need to see whether it's invoice or not. Only the automation. So maybe this should be actually hidden for everyone. But the board owners, of course, who can see anything on the board. And a result of all that information. And a bit of chat. GPT. Um. Magic, you could say, because you're basically just take this text and say, this is the context for it, right? More of a description and then it just, uh, right, a very nice description that took, you know, seconds and was created with the, uh, invoice row. And is also with minimal review, could just be sent over to the economic system. That's the gist of it. Okay, so you will avoid writer's block. As I said before. You will also. Pilot invoicing gets even more fun. It's of course, already fun to actually feel a satisfaction to ask for payment for something that you're proud of, but it also gets much more easier. Nobody has to enter data twice. You only need to review a bit of data, which takes much less headspace and, uh, much less kind of mental capacity than just then fitting with two types of I did in the beginning of this webinar. Uh, you still get the chance to manually review, because it's quite important that you don't over automate your workflow because you don't want to send a invoice to clients where the item description is far off, and saying that it's a public square. When it was sidewalks that you were, uh, that you were supposed to do some renovation on. Right? Um, so that is a very important to know. Not over automate so that you lose control, but you should still have the, uh, correct and relevant, uh, checkpoints, uh, in all your workflows. And then with one click, you just have this real invoice being sent to the customer. One click, you have to click send here. That's all you do because you already have whatever. If your favorite invoicing app I'm not gonna endorse any of them, but the okay, I installed that one. Uh, you have already, -uh. -Connected to. Uh, your invoice, uh, software, either through an application or via Make. And with Make. Of course, you can also do the event custom calls to a invoice system that you basically billed yourself like. The possibilities are endless. To just have a one click draft send, uh, one click, uh, invoice sent to the invoice system. And either then it could be reviewed again by the economic department, or it could be directly sent to the client if you know what you're doing. Like, uh, if you're the CEO of the company and you have built it yourself, then probably you want it to be sent directly to the customer because you don't want to review it twice unnecessarily, right? Okay. Um, and I think that was it. Something that I do recommend as a homework. Except for getting inspiration from this webinar. If that's you actually have a look at all the temperature and so on. So for example here default to one which uh, made shut GPT make up. That was a uh part of the public square that need repairing. And also you have the sidewalk. Um, so this should be set ideally for me as well. You should also try experimenting bit with the top p and N. And if you're a very handsome kind of person, that's all you need to do. You only need to experiment and then get a feel for it, right? Other people, they are more academically inclined and want to find out exactly what each of these mean. And then I recommend that you check with OpenAI who actually created it, and do it that way. Uh, it's not the most fun read, but it could be enlightening and actually lead to some new ideas. If you are quite interested in, uh, machine learning, AI and all that kind of stuff, that's what I recommend. Definitely. I also recommend you to, uh, before you do any kind of integration like this to map out properly. What's your monday.com setup? Where can I find the information for the item description? Where can I find information for the free text? Where can I find the information for each line? Maybe you don't want each invoice line to be one, uh, topic or one part, or the project as it is now. It's basically milestone or whatever you will call it for a construction company. High level, uh, gate or milestone. Uh, but rather maybe you wanted to say. Okay, we worked 30 hours with monday.com for this price. And five hours, we'd make those come for that price. Uh, and that's it. So maybe you want to, uh, actually aggregate the data. Remember that we have quite nice aggregators, not only text aggregators, we also -Have -At any point that we want, we can put a, uh, numeric aggregator that could be set up like, uh, okay, I'm just going to, uh, the sum -of. -Each. Uh, could be any variable here. It could be each. I was thinking. -Of picking. -Projects, but. Okay, so you can get basically the whole project value, uh, for, uh, each row instead. So you don't maybe you don't want it as low level as this one. Instead, you want it to be. More high levels of one line. If one project project alpha project and then price and quantity. So that could be an idea, too. -So. -Uh, don't feel afraid to, um. Come up with an additional idea. Most of it can be solved like that. But what is important is that you do it in a structured manner. Uh, by first looking at what information do I want an invoice. Where should I fetch it from? Uh, do I also want to connect, for example, the client registry between Monday and, uh, my invoicing system? That is actually what most people do. I would say some even, uh, connect another entity, for example, a project or a, uh, some other accounting entity, uh, to have automatic accounting, uh, on a whole other level and reporting a financial reporting as well. So many, many things can be quite automated that way. Okay. I think that actually I have, uh, said everything that I wanted to say today. Uh, I'm going to fix my OpenAI connection. Uh, that if broken for some reason, uh, so that next time I have an AI webinar, I will use, uh, the chat GPT uh, for. I think it's cool, isn't it? Yeah, I think so. And not to do all Da Vinci stuff. Um. And, uh, that will I think, uh, also give a bit more context, but for people who like Make and monday.com, uh, then I think that, uh, you can figure it out what would have happened anyway? Okay. So thank you very much for today. And, uh, I'll see you next time in, I think, March in an unannounced webinar. I haven't even decided the topic yet, so we will see. All right. Okay. Bye bye.