Signal Trigger icon

Signal Trigger

Triggers on new Signal messages via signal-cli-rest-api WebSocket

Signal Trigger

AI-generated

Summary

Listens for Signal messages over the signal-cli-rest-api WebSocket and emits each qualifying event as an n8n item. Configure the required Signal API credentials, then optionally set reconnect timing, ignore content types, and filter groups or senders.

Inputs

  • Signal API credentials (required) — Required credentials provide the API URL, account phone number, and optional bearer token used to connect to the receive WebSocket.
  • Reconnect Delay (seconds) — Wait 5 seconds before reconnecting after a WebSocket error or close; configurable from 1 to 60 seconds.
  • Ignore Messages — When enabled, skip events containing text. Defaults to false.
  • Ignore Attachments — When enabled, skip events containing attachments. Defaults to false.
  • Ignore Reactions — When enabled, skip events containing reactions. Defaults to false.
  • Ignore Poll Votes — When enabled, skip events containing an incoming poll vote. Defaults to false.
  • Filters — Optionally filter events by group internal ID and/or sender. Each filter mode can be None, Whitelist, or Blacklist; enter IDs, phone numbers, or UUIDs one per line or comma-separated. Both filters default to None.

Output shape

Emits one item for each accepted Signal event, with a single JSON object.

The object includes messageText, attachments, reactions, pollVote, sender and group details, timestamp, account, messageType, and the original envelope, plus other metadata. Empty events are skipped. Long Signal messages may be restored from their text attachment; that attachment is omitted from attachments. Duplicate envelope timestamps are skipped, and the trigger reconnects after WebSocket errors or closes until stopped.

Links

Discussion