signal-cli-rest-api VS signal-cli

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.

Not official but this works darn well: https://github.com/AsamK/signal-cli

If you want one for just personal use; this works well: https://github.com/AsamK/signal-cli

Just sign up with a Twilio number (using voice call) and you can make your own bot.

Here is my docker compose, maybe it is helpful: signal: #registerung tutorial # signal-cli --username +12345678 register --voice --captcha censored # https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha # https://signalcaptchas.org/registration/generate.html IN CHROME # signal-cli -u +12345678 verify 123456 # signal-cli -u +1234567 send -m "This is a message" +12345678 #curl -X POST -H "Content-Type: application/json" -d '{"message": "bliblob", "number": "+41824174983", "recipients": ["+21412430"]}' 'http://signal:8080/v2/send' #external testing image: bbernhard/signal-cli-rest-api:latest container_name: signal restart: unless-stopped hostname: signal networks: - monitoring volumes: - /docker/prometheus/signal/client:/root/.local/share/signal-cli - /docker/prometheus/signal/client:/home/.local/share/signal-cli labels: - com.centurylinklabs.watchtower.enable=true environment: - USE_NATIVE=0 signalweb: # curl -X POST localhost:9100/api/v2/alertmanager -d '{"alerts": [{"status": "firing","labels": {"alertname": "test"},"annotations": {"message": "Test alert."}}]}' image: registry.gitlab.com/schlauerlauer/alertmanager-webhook-signal:latest container_name: signalweb restart: unless-stopped hostname: signalweb networks: - monitoring volumes: - /docker/prometheus/signal/web/config.yml:/root/config.yaml labels: - com.centurylinklabs.watchtower.enable=true

Yes, using the signal-cli program. It has a built in JSON RPC API that can be used to develop application integrations

Last commit was 2 days ago so it should still work: https://github.com/AsamK/signal-cli

Sorry to hear. Then the cheap backup may be a Signal CLI forwarded over to mqtt CLI

build, install and configure/register signal-cli. The code snippet below assumes you are running it in multi-account mode, but I'll leave a comment where it matters

No official API that is public from what I can tell, but appears this works https://github.com/AsamK/signal-cli