FGRibreau/n8n-nodes-signal-cli

Sending a receipt does not send timestamp correctly

Closed

#14 opened on Nov 8, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (11 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (35 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

When I receive a message in a workflow and want to send a receipt, it fails with the error message:

2025-11-08T14:41:26.691Z [pool-7-thread-2] DEBUG o.asamk.signal.jsonrpc.JsonRpcReader - Received json rpc request, method: sendReceipt
2025-11-08T14:41:26.695Z [pool-7-thread-2] WARN  LibSignal - [SignalServiceMessageSender]: [1762612886695] Hit unknown exception: b598d90b-fec0-4da4-a0aa-581e124d47a4
java.lang.NullPointerException: Parameter specified as non-null is null: method org.whispersystems.signalservice.internal.push.ReceiptMessage.<init>, parameter timestamp

The timestamp parameter is correctly set in the "send a receipt" node. Neither a static timestamp nor a timestamp taken from the received message (dataMessage->timestamp) works, it results in the same error.

I looked through the source code of signal-cli and this project and the messages look consistent at first glance.

Any idea on how to get the actual message sent to the signal-cli service logged? Looks like even with --verbose, signal-cli is not logging the incoming JSON message.

Contributor guide

Research direction
Investigate the ReceiptMessage constructor call in the signal cli client to understand why the timestamp parameter is null when sending a receipt. Check if the receipt timestamp is being correctly passed from the n8n node to the signal cli service.
Tech stack
typescriptnodejs
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitNode.jsn8n
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60