I would like to request the addition of Signal integration to n8n. Signal is a highly secure messaging platform that supports encrypted text, voice, and video communication. Integrating Signal into n8n would allow users to automate workflows involving Signal’s secure messaging services.
My use case:
I use Signal for secure communication in various scenarios, including sending automated notifications, alerts, and updates to teams or individuals. Currently, there is no direct way to integrate Signal with n8n, which limits automation capabilities when it comes to secure communications. An official Signal integration would allow me to send messages directly from n8n workflows, retrieve Signal messages for processing, and trigger workflows based on Signal communication.
I think it would be beneficial to add this because:
Enhanced Security: Signal is known for its strong encryption and privacy features. Adding Signal to n8n would provide users with a secure messaging option, essential for workflows requiring confidential communication.
Broader Use Cases: With Signal integration, n8n could cater to a wider audience, particularly those in industries where secure communication is a priority (e.g., legal, healthcare, finance).
Increased Automation: Automating Signal communications would streamline many processes, such as sending automated alerts, customer service responses, or operational notifications, all while ensuring privacy and security.
Me too. the main concerns are around E2E encryptions and Telegram Bots don’t provide enough privacy and security on Bots compared to normal user to user messages.
Slack doesn’t upload files and therefore. the really functioning Chat app is Telegram, which is risky as defined above. Even hancing Slack would be great
it looks like this wouldn’t be to hard to provide a public API endpoint but it would cost $ to maintain it… but I want to use Signal as well because I don’t need the CIA reading every telegram message I put through a system.
I’ve just set it up and everything’s working so far. No long time test yet, but the first impression is very good.
It’s a lot depending on the selected mode of the REST API, see the README.md in the linked repository. So far I had the best experience with json-rpc mode.
I linked this repo in my original post and I am using it for sending notification (as this is simple enough). But using the API does not provide a first-class experience, like with other integrations n8n offers.
Shame on me @Shalak I had the browser tab open for a while and just read the last message here before I posted my reply. I will do a better job next time, sorry!
But to give some context here as well: I don’t think n8n will deliver an official node for something that doesn’t offer a public API. It doesn’t make sense to them, from my point of view. So somebody could build a community node to deliver a better experience, but users would still have the responsibility to host the API theirselfs.
Correct. This is a good case for creating a Community Node. Right now, these have the drawback of only being available on self-hosted instances and not on Cloud (for performance and security reasons), but that’s something we’re working on.
I too would be very interested in this. I was starting down this rabbit hole with loading signal-cli on my aging MacMini server that I locally host n8n on and of course, my versions of Xcode are too old to finish compiling. Anyways, it just means I need to upgrade my entire setup sometime soon but also the usefulness of a Dockerized version of the Signal API would be great. It is a bit outside of my technical ability to build a custom node (but I was going to try with AI assistance) but I think I probably would have beat my head against the wall for way too long. I don’t really want to use Telegram at all and using WhatsApp Business account is also a non-starter. We know in 2025 there is nothing more important than privacy so Signal it is…just hope we can find a great way to integrate it with n8n!!
I had the browser tab open for a while and just read the last message here before I posted my reply. I will do a better job next time, sorry!