Claw Messenger for n8n

Use this package to send one controlled plain-text message from n8n to a registered E.164 phone and prove the same thread works when the matching reply reaches a named WebSocket consumer, webhook, or backend.

The node returns the full send.result status so a workflow can distinguish accepted, failed, retryable, and not-confirmed sends. Inbound reply triggering is not included.

Install

Install the community node in a self-hosted n8n instance:

npm install @emotion-machine/n8n-nodes-claw-messenger

The package does not add an inbound trigger. Keep a WebSocket consumer or webhook connected for replies.

Credentials

Create a Claw Messenger credential with:

• the API key from your Claw Messenger dashboard;
• wss://claw-messenger.onrender.com/ws as the WebSocket URL, unless your environment uses another Claw Messenger endpoint.

n8n stores the API key as a password credential. Don't paste it into workflow fields, exports, screenshots, or logs.

Send a message

1. Start with one phone you control and can answer.
2. Add the Claw Messenger node after a Manual Trigger.
3. Choose Send Message.
4. Enter the controlled phone in E.164 format and a short plain-text message.
5. Leave Service on Automatic for the first proof.
6. Run the workflow, then reply from the controlled phone.

The node's result reports what Claw Messenger knows about the outbound request. ok: true, accepted, delivered, or read is not setup proof. Setup counts only when the controlled reply reaches your workflow, webhook, or backend.

Current scope

• Send a plain-text message to one registered E.164 recipient.
• Return message, chat, selected-service, fallback, delivery-stage, retryability, and setup-proof fields from send.result.
• Preserve n8n item linking for every output.

Inbound reply triggering isn't included in this first package. Keep a WebSocket consumer or webhook connected for reply handling until a trigger node is added and live-tested.

Release verification

Each release must pass the same checks used by the LangChain and CrewAI packages:

1. Keep the package metadata and bundled LICENSE file on the approved Apache 2.0 license.
2. Use package-scoped npm publisher access without placing credentials in the repository, workflow export, screenshots, or logs.
3. Regenerate a test-tenant API key specifically for this proof. Never reuse a production key.
4. Name one controlled registered E.164 phone, a person ready to reply, and the WebSocket consumer, webhook, or backend that will observe the reply.
5. Build, test, pack, and install the generated .tgz in a clean self-hosted n8n instance.
6. Run one Manual Trigger -> Claw Messenger Send Message workflow with Service set to Automatic, then reply once from the controlled phone in the same thread.
7. Retain only sanitized evidence that matches the outbound thread to the reply at the named observation point. Accepted, delivered, or read outbound status alone does not pass this gate. The n8n node does not observe the reply itself because inbound triggering is not included.
8. Revoke the regenerated test key.
9. Publish only after explicit approval. n8n community-node submission, release notes, and maintainer contact remain separate decisions.

Claw Messenger documentation: https://clawmessenger.com/docs