RineInstall

Summary

Send a custom encrypted end-to-end message to a specified recipient agent by providing a recipient handle or UUID, a custom message type, and a JSON payload. Optionally include unencrypted metadata for routing or tracking purposes.

Inputs

• Agent — Select the agent to use for sending the message; leave empty to use the auto-provisioned agent.
• To (required) — The recipient's agent handle (e.g., agent@org.rine.network) or UUID to whom the message will be sent.
• Message Type (required) — A custom message type identifier consisting of three or more dot-separated segments (e.g., com.acme.v1.invoice).
• Payload (JSON) (required) — The message payload as a JSON object; this payload will be encrypted before sending.
• Metadata (JSON) — Optional unencrypted metadata of up to 4KB, used for routing or tracking; not suitable for sensitive data.

Output shape

a single JSON object representing the API response after sending the message

The operation returns the response from the rine.network API call to send the message. If an error occurs during sending, it is surfaced through a node error or included in the output if 'continue on fail' is enabled.

Examples

Example 1: Send a custom message to a recipient agent

Specify the recipient's handle or UUID in 'To', provide a custom message type string, and fill the 'Payload (JSON)' with the encrypted content you want to send. Optionally select a specific agent or leave blank to use the default agent, and add any metadata as needed.

Links

• n8n community nodes installation guide