signal-cli-rest-api VS cronsim

n8n – Zapier alternative. I just set up a workflow that calls my SerpBear API, sends that to quickcharts to create a graph, and then sends me a message on Signal with signal-cli-rest-api. I’m thinking of building some templates through the creator’s program. Let me know what you’d be interested in seeing.

Is it a case of spinning up this, configuring it for me and then pointing Radarr at it for notification support?

There is already one at https://github.com/bbernhard/signal-cli-rest-api

They're pretty cool actually, if you didn't find out it for those 3 days when i was not available, there is a link for easy to setup REST API: https://github.com/bbernhard/signal-cli-rest-api

You can, for example, use https://github.com/bbernhard/signal-cli-rest-api if you want to send/receive signal messages via REST. Or use the underlying CLI.

I thought I could run it in a docker container on a pi4 (I don't want to install a full kde on it though) and then wrap some python around it to give it a web api similar to https://github.com/bbernhard/signal-cli-rest-api.

I've also written one: https://github.com/cuu508/cronsim

I do also value simplicity and compactness, and try hard to limit the number of dependencies the project uses. If you look at requirements.txt, there are relatively few direct dependencies. When I add or upgrade dependencies, I also check what the code quality looks like, how active is the maintainer, what unresolved issues the project has, and so on. For example, I did a bunch of testing on croniter, which resulted in a number of filed issues, PRs from me, and, ultimately, my reimplementation of the library. Of course I cannot guarantee there are no vulnerabilities in the dependencies.