Welcome, everyone. So today we're gonna integrate monday.com with some external services such as Typeform and Mailer Lite. We're going to do that with the help of make or integrations. If you're more familiar with that term, we are going to look at how to save a snapshot of project in monday.com for today. So say that you have started a project already, or you have finished the planning, or is at least and you have all your tasks in a project working monday.com and you want to save a snapshot in order to have future reference of that. The project on how it was when you had it readily planned. Then after that, you can save more snapshots as you go along with the project. Of course, in order to compare it during different, uh, phases of the project or at different milestones, for example. So that is quite a useful, uh, scenario that we are going to look at where we actually save that kind of snapshot in a Google Sheets. So it will be one, uh, Google Sheet file created in a Google Drive where each row is a monday.com, uh, item or a multi task and uh, it progress up to that point. So the scenery itself looks like this, that we get a webhook from monday.com The webhook will signal for make them to retrieve the data from monday.com The whole row that from the project overview of the project that we're interested in. Then we will create the new spreadsheet in Google Sheets for that project and add one row titles of, uh, the task columns, for example date, status, name, order to alpha, and so on. After that, we will iterate and all the 12 that are connected to the monday.com project overview. Get each of that off data in the next, uh, module that we see here in front of. And after that, of course we will in our newly created spreadsheet, uh, create one row per task of that order. So it's quite easy if we have a look at the project overview that is quite familiar from the webinars that I have had. Then we have a column here on the very right called Create Snapshot Sheets. I am going to do that on this project wiki. So when I click the create snapshot, then after while, we will have a new snapshot saved in my Google drive that contains all the topics that are connected here to all 25 of them. And that snapshot will be called project with key and today's date. Let's have a look here in my Google Drive. For here we can see that it created. And we see now also that talks are ticking in. So we can see earlier when I talked about the scenario itself we got product with key up here in the name snapshot. And then the today's date we had one row created for all the titles of all the columns in the monday.com board that if the that have the task of this particular project and then we have all the data ticking in as expected. Okay. So that is great for having a snapshot created. But if you also wanted to keep it quite organized, then you want also a specific folder for your project in your Google Drive where these snapshots if failed, especially if you're going to create many snapshots for one and the same project. Of course, want all of them in the same folder, together with all the other project files that you might have created or material that you have created before the project, or even received from someone else that you want to save in there. So in our next scenario, then we are going to create a folder in Google Drive, and we're going to put the link of that folder back here in monday.com. We can see that we have two examples here already. We don't yet have an example for project with key. So we are have right now a webhook that on the project ID column because I want to create folders looking like this where it says the project ID project files. Simple as that. So I am going to give it an ID, and I think that 0009 is not taken. That's the idea I'm going to give it. So we will see the result of the make scenario quite directly in our Google Drive. So now we have this project file folder created. As we can see here in Google Drive. And the way that they make scenario worked. Well, if that webhook was received from monday.com as usual, then we got a whole row of the monday.com project, and that is in order to get the column data from the project ID column. Then we use the simple create a folder in Google Drive where you can put it wherever you want. Of course, if you want it in a sub folder and so on. And of course, in theory, you could even create a whole structure of subfolders directly for your project that you have snapshots in one subfolder, you have a previous material in another, and so on. You can do quite a lot of stuff here if you really want to. When it comes to the folder structure. But in this case I just had it simple. So we can see here it says Text Project files. And it takes this project ID column in monday.com. After that we have another monday.com module that takes the ID of the newly created folder and put it on the end of a URL. Well, if the name of the folder to put up the text, then we get this really nicely formatted URL back into our monday.com board. You can see it right here. If we go back to the board here again. That is being put back here of fear of 009 projectiles. That was our second scenario, and what is very nice about these two scenarios is that they could go together. As I said earlier, we could have an advanced structure with a lot of subfolders, and after that we can have all our snapshots actually created if we have a look in here. In the other scenarios that you have created, a snapshot, we could have it's ordered into our Google Drive however we want, so we can have it automatically put into a specific folder. So move a file and then we can have the file ID could be the spreadsheet ID that we have created, and a new drive location could be mapped in with the help of that URL for our newly created folder. The next we are going to have a look at another scenario. This scenario will the contact information from all the people that are involved in a project. Actually, in your contact registry, you can connect your projects to specific contacts in order to have them set as keep posted here. Or they could be called stakeholders. For example. Let's change that name now already, but these stakeholders should be kept posted about updates for the project. Over in Typeform I have prepared a registration form. So Typeform is one of the nicer looking and easy to handle integration with at least, uh, formulary services out there. Quite easy to get all the metadata connected to each question, and then we can just map it in easily into monday.com. Again, we can fill this registration form in now. Already we can say we go. Let's have the last name testing in order to differentiate it a bit from the other test row that I had for myself. We can put any phone number here. And then my role would be senior implementation consultant. There we go. So after that, Typeform have been submitted. Now we can actually have a look inside, both make and Inside monday.com to see where it landed in monday.com Webinar content registry board that I created here. As you can see, we got all the answered answers in here as I typed them earlier, which is expected, of course, from this kind of integration. We will now have a look at the scenario on that happened. And as you can see it is quite the simple scenario. All we do is to have a webhook set up against Typeform, which is very simple to do. It's called Watch Responsive then and it will be automatically created more or less inside Typeform. When you select it here in make, then it will create an item directly in monday.com in the specific contact registry board. You can see here that I put the first name and the last name after the item name. And then we have some of the other information mapped in here on our array of column values to change. You can see also that it's quite easy, as I said, how to map all the questions and their answers because all of them are under mappable answers here in the bottom. We also have a monday.com module update with that in that registry to a label called webinar. We're going to get more into that later because that will trigger another make scenario, which in turn will send that contact information over to Mailerlite When we want to connect this with every contact person to a specific project, then we go to our project overview and we have to select. In this case we go Tufting. But we could also select more people here. For example my colleague Fredrik. This is quite useful for another make scenario that I'm going to show, which is to keep these two people posted about things that happens in the projects based on actual actions in the project overview. So I have another webhook set for when you change the state of to execution in monday.com, because then it will send an email to all the stakeholders that we have selected. So let's take the top project here, which are two people have taken in it, myself and Fredrik. So when I select execution there, then we can see. Then the item is asked for the in the project overview. And then we start iterating and getting all the contacts that are actually connected to that project. Similarly as we did for the create snapshots. So in the webinar context registry, we're actually getting the emails of the two top people here that were connected here in the project overview. Those group. And then after that, an email is automatically sent to those two persons. Now we're going through all but one of the scenarios that I was going to talk about, and I mentioned it earlier, it was the one that was chained to the Typeform where the Typeform first landed into monday.com as a new contact sheet or a contact row recorder. And then we saw that the same scenario also triggered a status change in the contact registry. That trigger, as I mentioned, briefly triggers another scenario which puts that contact into mail or light. So mail or light if you've more as a marketing tool to send out automated emails and in order to manage marketing campaigns and so on. So let's have a look at that make scenario. We have one webhook going in from the start, the change that was made by the previous make scenario. And that one gets the whole contact registry item. So in this case it will be for example, the top row here. And then it simply adds that subscriber to a specific group. In this case, I selected group that I have created here temporarily for my own webinar. I simply map in the email, in the email field, and then of course again in the custom field email if there is one. And then we have the name. In this case the item name equals the contact name. I don't have a last name column. I could have done that in the if I want to in the Typeform make integration scenario, but I wanted to put both of them in the same name column. But one way to get both the first name and the last name a separate entity in monday.com would be to have them in hidden text columns, and then they could be pulled from those hidden fields, while the identity could still be the full name. Then we have the company that's a monday.com text column, and then we also have other fields here that we could have pulled from Typeform. But then, of course, that always how much do you want people to feel informed and how much do we want their email address. Right. So this one will be triggered when. This specific row gets the status webinar. Now you can see that I'm doing this manually so that we can see the full output that may lowlight actually have created this specific contact. Let's have a look here in my lowlights. So here we now have two contacts. Rather we have one Fredrik at Omnitas. And as you can see, even though two Typeform forms were imported with the same email address, we go at omnitas. That is not possible. Have a duplicate later in Mailerlite which is why we still only see one mailer light contact for that. We could also do the Typeform to monday.com scenario. Have a look at how that duplicate check could have looked like if we want to do one already today. So that would be for example, if we have. Another module here. Search. I don't in the board by column values. Then we can actually search for the same email that was inputted already in the registry that exist. And then we could map out that if, for example, ID exist. Then it would, uh, do nothing. But if it doesn't exist, then it would keep on creating an item and so on, and then send it over to Mailerlite. So they always actually to manage duplicates also when using integer mode. And that has a wide range of applications that we often do for several of our clients. So I hope that if, if of uh help for you when you're making your own make scenarios and otherwise, please feel free to reach out to us and we could give you a helping hand. That's it. Thanks for watching and please subscribe to the Omnitas YouTube channel.