Feature Request - Add ability to receive a webhook to trigger refresh of a specified collection about kometa

[meisnate12]

for real thinking on this any way you rerun the collection even 10 minutes after you run it the first time the trending list will change. so I think the best option is to have it save what movies were added. I've got an idea of how to do this I'll try and get it in the next release

[meisnate12]

tbh im not sure how to set up something in python that radarr could hit with a webhook. I'll look into that but depending on what it would take to do that I don't know if I would.

What I know I could do is create a way to run specific collections again after a user-defined delay, possibly even multiple times with different delays.

Well, now that I think about it there's also the problem that for some people it takes hours for it to run I think my average run time is 4-5 hours. Maybe I could add a feature where you can automatically run collections again at the end of your run so like you have Trending run first and add movies to radarr and then give it a run_again: true option and then it would run again at the end hours later hopefully now adding your movies to radarr.

But the trending list might change by then anyway, so a third option is to have the program remember the exact TMDb IDs that it sent to radarr for each collection and have it try and find those and add them to the collection either at the end of your run or after a delay.

What do you think?

[doctarrwho]

There's some good info here about webhooks with python: https://blog.bearer.sh/consume-webhooks-with-python/

Yes, it's not an easy problem to solve and keep everyone happy. I did think about trending list changing on each run, and was going to suggest having an option in webhook to override add_to_arr to avoid repeated collection updates, BUT I didn't want to make this request too convoluted :)

Having said that, run_again: true option for a collection does work - My average run time is around 30 mins, so that's plenty of time for arr to download a trending item. This is probably going to be easier to implement, but someone like you with an average run time of 4-5 hours might want it on a specified delay instead of at the end of the run.

For me, either of these options would work so I'd be happy with you adding whatever is the easiest for you.

Also, worst case scenario, the ability to override add_to_arr via a command line parameter would help, because then I could just run a script on a schedule that docker exec's and updates the trending collection every couple of hours or so but I would only want trending items added to arr on the full run at 9pm.

[meisnate12]

you can add run_again: true to a collection to have it try and add the missing items to the collection after the daily run.

If you want to add a time delay after the daily run under the settings attribute in your config file you can have the run_again_delay attribute which takes a number of minutes after the daily run to run the collections again and it defaults to zero.