Create a Mattermost bot for daily standups

uh what we decided we wanted to take a look at uh was the really the problem really the challenge of standups at nan said well you know right now stand-ups can get a little bit chaotic some stand-ups are scheduled per project they can happen multiple times a week and engineers are creating written stand-up notes but oftentimes these are being shared during a synchronous meeting so that it's a little bit harder for folks across different teams or who aren't in a stand-up to see what's going on uh so we went ahead and saw the sat down and when i say we um really my lovely colleagues in the group had this great idea ready to go when we started so we went ahead and set up a cron job that monday to friday at 10 a. m we'll just go ahead and ping all of the engineers and say hey are you ready for a stand-up would you like to do a stand-up have a queue ready to go and at 10 a. m it'll go ahead and check hey which are what engineers are in these stand-ups and need to be messaged um you may notice that we did this through mattermost and don't have a mattermost oh we do have a mattermost note but we went ahead and used the webhook here instead because we decided to work with the interactive messages we thought that would be a really good feature and that's not currently built into the n8n the mattermost node for n8n but if anybody's taking suggestions on things we'd love to see in this that's definitely something that came up executing this workflow please work please hey everything's fine uh we get a hey there it's time for stand-up note in from our stand-up bot we're able to provide an update and tired things more things uh one challenge we hit early and often so that should come up here automatically one challenge we hit early and often is that the matters most documentation was a little bit challenging in this space so getting this up and running really relied on the goodwill of strangers we had a challenging time with some authentication finding some of the ids was a little bit challenging but also the interactive messages menus just were not returning any value i found a ton of other people with the same questions and some beautiful stranger who for absolutely no reason discovered that you need to mirror the id of what's going on to have it work there's no documentation around this there's no explanation why this works but this beautiful stranger absolutely made it happen um we thought that we'd yeah we really liked having something that we felt we was going to be able to we'd be able to use as soon as this was done but would love to do a little bit more work coming out of it um really the biggest challenges we hit and continued to hit were around modern most documentation but at one point we did have to reload the ui um the n8n ui and discussed how it would be really useful to have a pinning function the ability to have the node hold on to some of the information it needed when we were going to repopulate fields i believe that might have been here in the web hook saying um when we need to add an expression after we had reloaded the ui all of that information being gone was briefly a little bit frustrating but yeah not too terribly stressful for the very first hack day for all three of us