AI Summarized Newsletter & GitHub Profile Analyzer [Update #01]

I had is that I think I'm going to have a little less velocity because I'm also having to document the stuff and I do want others to be able to copy these templates and use them that's going to take a little bit more time so I got to take that into account in my planning I added some stuff into the notion and Twitter on what I'm working on right now I think that totally could be automated for example when I Swit the ticket in the can band that could update a few different sources but I'll probably do that once I ship one of the first projects so I can be collecting feedback on that project getting value out of that before I'm optimizing my own Ops and then I think I might have to think about how I'm disseminating the Vlog content because the updates could be rather long if they're also tutorials so they might have some Snippets of what I'm building and then I will edit down a how I built a project video as a separate Standalone that I can link into the video so for this first update it'll be a bit longer we also built a little lday cuz it was day one there's a lot of setup that's something I'm going to have to iterate on if you have any suggestions on that please do let me know in the comments and then what have we shipped or done today in terms of like actual product building so the AI newsletter uh project this is the one that takes updates that I'm doing already across Twitter and YouTube and stuff uses AI to summarize that and sends an update email that is live or at least the sign up form is live it's on my Twitter and basically anywhere I'm posting this video you'll have a link to that so sign up for that because the more people that sign up for it the more I'm going to invest into actually building that solution we'll do that maybe on Wednesday once this profile thingy ships and then the profile thingy is the profile analyzer that is where we take a GitHub handle analyze a profile and give you some insights on that I was able to check out we web pretty cool tool front end a little bit of a learning curve but I think I've figured out what we need so status is we have a front end it's very shitty but that can accept the GitHub handle on one page it can open the results page with a unique URL route and pass a part of that URL route which is the handle to Wei web which was able to create a HTTP request to an nend workflow the nend workflow right now just sending it back some mop data but I've got those all linked up right now and I've got it swapping a static text on that results page to the dynamic mock data that I got back from n ATN so for me that's we web is validated I know I'm going to be able to style CSS and stuff on there the real question was am I going to be able to get that data from the O route and how complicated is it because velocity is important so for me it's the tool I'll use for that and since the back end for NN is established tomorrow we can focus on building out the back end for the NN uh understand what our data looks like they'll be sending back to the front end and from there skin out basically have an MVP so for this GitHub analyzer what would be great for the next 24 hours is understanding what you think I should add to it one idea I had is analyzing GitHub repos the people followed summarizing each repo feeding that into a text classifier that spits out an archetype of types of developers we could even generate some AI cool little game card avatars for that but what other things could we add there so we get H roast is something that we could have as well I don't know how much context we're going to be able to pipe in if we can analyze a lot of that code so next in this video is going to follow a bit more of the in-depth look at what I did today and we'll catch you tomorrow for day two of the 30-day AI Sprint okay so let's have a look at our splitboard

the first thing that I want to do is a AI powered newslet basically each day I'm creating all these artifacts ready like tweets and there's going to be Vlogs those Vlogs can have ai transcripts pretty cheaply these days what else a notion I could also write a little manual writer basically this all these artifacts of text throughout the week we could pipe into an AI and summarize it so that's the first thing I want to build because I think it's rather meable and I could see this being something a lot of other folks want to do as well maybe with different sources of data but the template ultimately that we can create is something that basically ingests from various sources to a certain source of Truth and then at some period again it could be based on schedule or some sort of Slash command or something takes a certain filter of that data let's say are seven days or the last X days or meeting certain criteria and then summarizes that and sends it somewhere so we'll do that as an email newsletter but again you can swap out the different PS do something different in noi here this is on my Twitter we've got the bit of a description for it so what this is going to do is it's going to have a sign up to newsletter workflow that's what we're going to build now we're going to use an form trigger to do that we're then going to have a notion database that stores the updates have different types of updates not sure if this will be useful but more context could be helpful for our AI workflow that summarizes it a workflow that populates this motion database and a worklow that runs every Friday ingests are the most recent updates from the last six days and then generates basically an email to send out a few things I already did I was setting up this is the one project that is was already setting up a little bit I've already chosen to use custom right o and I've already just set up the Goda source so it's a simple notion table and then here I have each update notion has to have a name for it so we just calling the update I have the body this is what I might manually write in here or is ingested from a source on Twitter and then the type step one of this is setting up the customer workspace so I've done that so the first step we'll build is the form trigger this is going to serve a little web form that we can Ser right F the work for we have to set up something separately of course we could use something like T form but let's use this to keep it simpler and get it out faster so we'll pick the on form submission this adds the form trigger to my canvas okay so we don't need any authentication on it the path itself let's give it a nice uh name like the 30-day AI Sprint newsletter all right form sign to 30day AI Sprint newsletter okay let's get a description in a little bit later all right so let's get the name because we need that for customer oh and then we can say high name that sort of thing is your name let's not worry about first name last name whatever they enter either way we'll use an expression to just get the first part of that placeholder EG Mason Ora let's make this required and then let's also add an email type it's also required field and we're going to want to respond when using a respond to web hook node because we could just give him response as soon as it's submitted but with this we can actually check that it was added to customer arrow and give the user feedback if it was successful or not so let's do that and then we'll use the respond to web node last okay let's quickly test this okay we can't test it because we don't have the respons to web look attached so while we're building let's switch to form is submitted and then we'll add that feedback Mo at the end okay so what is your name say naan submit that okay submitted we've got it in here I've got it in schema view perfect okay so the next thing we're going to want to do is add this user to customer o but in custom o we want a user ID so we're going to get crypto node and generate a user ID so it's generate a random string U ID we can call this ID rates okay we're going to foro the fantasy camera for now because I descript crashed and so I lost building out this quickly go over it we've got the U ID and then we need to create the customer in customer IO so we added that through here add a create update a customer action and in here basically we if I run this let's capture this oh let's do a different email so we have a unique one to run into custom Ro cuz I already added Nathan automator let's also pin this so we don't have to keep filling out the form and then in here I dragged and dropped this on here so basically we've got the same ID there I added email and I drag and dropped email in there so that's creating the customer if we run this we go to customer iio people you can see I've added nor and automat to here with the same ID yeah and then we added another custom Rio action to add that customer to a segment I created a segment in here create new segment it was a manual type of segment because we want to use the API which led me to this screen the segment has an ID of 11 I copied that paste that in here and again just mapped in the user's ID if we run this we can see it was successful go over to people here let's see VI people list we can see we've got Nathan automator 2 in there and then what I did next is these steps could fail we want to know about that we want to let the user know if they failed so in both of them I went into settings on error I changed to continue using error output which added this error output and then I added a slack node to send message so slack send message and then the error output's going to there and I'm sending it to a user I copied my own user ID to send in there and I'm just sending a static message for now if I get this message a few times we can make it more advanced and then the slack messages by default already send a link to this workflow include link to workflow set by default so I'll be able to open up the workfl in troubleshoot from there and then if they're successfully added to the segment we want to let the user know from the web form that was all good so I added the respond to web hook node and now we're configuring that so the respond withd we want to set to Json and if I go into the form trigger when it's set to respond using the respond to web hook node we get this little note that we need to have this as output data so that's the form submitted text so this is the text that we swap in the form so you've been added to the newsletter great so now let's try this let's save it let's unpin the data and let's test the whole thing okay so perform let's say my name is Max Plus test1 gmail. com as a new email okay you've been added to the newsletter so it ran it went to here great it's working there was no error let's check in here I've added let see what happened let's go in here Nathan automated plus T1 at gmail perhaps customer iio perhaps custom iio doesn't allow that interesting let's try it with a different email test that theory test one for SE oil. com let's submit that okay that worked let's go back in people here okay that's working we see the segments they're in newsletter subscribers okay so the plus thing is not working in customer AIO what we could do is check for that now it's been ifs node step and if email let's go chat GPT because we could do a plus but I'm not sure if url's support pluses because if they don't we need to make sure that we're checking for the plus before the at symbol me a reject in string let's see cuz reject is not something I know okay it's pretty simple and we should have a reject matches this reject let's see does not match this rejects because okay cuz it's a good email now let's quickly edit this and test it plus test with the other case it's going to false Branch perfect okay here we'll connect that to there and here we want to respond and try again okay so now save this let's unpin this let's also duplicate this because we need to add an error after the select message cuz here then the users won't get one if we don't add that and this is a generic error not sure exactly at least for now we won't build that out if we get more errors we could add a switch node here and check that or check for different conditions and give user more feedback for now the form Max has been notifi okay so let's save this let's test this Nathan and then let's test Max plus1 emma. com you've been added to the newsletter okay why did that work maybe it's not working for numbers so let's test that again something and then Max Plus text email. com okay that's still working let's test if we got our logic wrong if this doesn't work there's a problem okay we flipped it so let's just flip this matches rejects now if I test the workflow we should have a working let's say Max 10 email do was a problem okay great and this refresh isn't working because we're testing so it's a live form that would work but we are going to have to click that button again when we want to test okay we've got the workflow working I'm going to save it and let's see what we do next let's delete the demo dat cuz I've got my workflow it's working we activated it so I can take the production URL and it's live it's working so we can post this to Twitter we'll post the tweet in a second here and then also I forgot to record but we've updated the project because all of these projects I'm going to be working on the notion file for the project everything in there should be able to let you know about the project how to duplicated so yeah we got this first workp done here there's the Json for the workflow some screenshot and what I'm going to do for now is we're going to launch this just on Twitter might post it to LinkedIn as well so you can sign up for the newsletter but what we'll do in classic triaging is let's see how many people sign up for this because the first email is going to go out on Friday and I'm pretty confident I can build that in less than a day so let's maybe pick up this project on Wednesday or Thursday let's see how many people signed up to understand how much effort we put into the first one

n