Signal

Interact with Signal CLI API

Actions8

Overview

This node integrates with the Signal CLI API to perform various actions related to Signal messaging, groups, contacts, reactions, and receipts. Specifically for the Reaction - Send operation, it allows sending a reaction emoji or symbol to a specific message in a Signal conversation. This is useful for automating responses or acknowledgments to messages without sending a full text reply.

Practical examples include:

  • Automatically reacting with a thumbs-up emoji when a certain keyword is detected in incoming messages.
  • Sending a reaction to confirm receipt or agreement in group chats.
  • Removing a previously sent reaction if conditions change.

Properties

Name Meaning
Account The Signal account phone number used to send the reaction.
Recipient Phone number or group ID of the recipient who will receive the reaction.
Reaction The reaction emoji or symbol to be sent (e.g., 👍, ❤️).
Target Author The author (phone number) of the message being reacted to.
Timestamp The timestamp of the message being reacted to, identifying the exact message instance.

Output

The node outputs a JSON object containing the response from the Signal CLI API after attempting to send the reaction. This typically includes confirmation details or error information returned by the API.

Example output structure:

{
  "jsonrpc": "2.0",
  "result": {
    // API-specific response data confirming the reaction was sent
  },
  "id": "some-uuid"
}

No binary data is produced by this operation.

Dependencies

  • Requires access to a running Signal CLI API endpoint URL configured in the node credentials.
  • Needs an API key or authentication token set up in the credentials to authorize requests.
  • Uses HTTP POST requests to communicate with the Signal CLI API's JSON-RPC interface.

Troubleshooting

  • Common issues:

    • Missing or incorrect Signal CLI API URL in credentials will cause the node to throw an error.
    • Invalid or missing account phone number or recipient identifiers can lead to failed API calls.
    • Incorrect timestamps or target author values may result in the reaction not being applied to the intended message.

  • Error messages:

    • "Signal CLI API URL is not set in credentials": Ensure the API URL is correctly configured in the node credentials.
    • "Error interacting with Signal API": General failure communicating with the API; check network connectivity, credential validity, and parameter correctness.

Links and References

Discussion