Automate hiring process

uh dale are you still on mute if you're speaking there we go sorry i lost the new button it's been how long we've locked down and still can't find them um so the context for what we wanted to do um was just that building some alternations around recruiting um it's something that has needed doing and i've kind of been playing around with it a little bit to join but haven't had anything uh like fully fleshed out so big thanks to the folks who've helped me in there and um basically the problem we've got uh is that we want to do um kind of some data analytics based on workable which is our hr system so we can look at workable and understand how many handlers how much activity do we need to do how much reach out messages do we need to send on linkedin and things like this um and at the minute the kind of analytics portion of workable is all kind of very uh reactive it's kind of looking back at what's already happened rather than giving you any information going forwards um they've got a really unfriendly api and it's kind of hard to actually get any data out of it so what we've done um is used the workable trigger that uh ricardo put together um and we've uh basically created this pipeline that pulls data through both into google sheets um and into postgres right and this is collecting uh data about when candidates created within workable as well as when candidates move for different stages right so when they move from like interview to technical test offer or whatever right um these kind of different functions will allow us to have a look at um really quick access uh spreadsheet stuff also um keeping it in postgresql we can do like much more analytics on um some sort of bi tools we're thinking like three tool at base and one of them would be really useful for us the big problem and where we spent like a lot of time today was working out okay so how do we um trigger this when it's disqualified and as you can see that's not something that workable caters for um and basically they charge money for like a bi link that enables all these other functions so we have to be able to work around um so can you see this tab now the should have changed right um so we built uh another workflow that starts with this chrome trigger and basically what this does is go through all of the data that's being pulled from uh from what we've already looks at what's in our google sheet compares it back to workable and has a look if any of those candidates have moved into disqualified stage and at that point it prompts us and adds a new line of data there we can see that we need to sync this up to postgres as well um but eventually we should just have this live database going through um and it's already started to work uh which is really cool so if we click over here we can see that like as of today we're now collecting a bunch of data about um you know when people are moving through all of these different stages so that's really cool and then um leone has been working on a workable node that's not a trigger as well yes i think you have to stop yeah yes uh can you see my screen okay so i was working on uh the workable noid um which is hopefully working now um so we can change in the workflow that they destroyed um the http request noise and use in the future our um yeah our workable noid and right now um what the note can do is um get all the candidates um and you can choose either like a specific candidate and you can filter the candidate by id or you can get all candidates