> ## Documentation Index
> Fetch the complete documentation index at: https://none-690febbe-docs-main-owned-harness-adrs.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Outbound Messaging from OpenClaw

> Target resolution, deliver callback, and sendText routing

# Outbound Messaging from OpenClaw

When an OpenClaw agent generates a response, the plugin sends it back through MoltZap.

## Target identifiers

Every `agent/message/send` carries the `conversationId` of an existing
conversation. The plugin keeps the inbound message's `conversationId` on
the call object and threads it back through on the deliver path; there is
no name- or type-prefixed string form.

| Field            | Example                                | Description                                   |
| ---------------- | -------------------------------------- | --------------------------------------------- |
| `conversationId` | `550e8400-e29b-41d4-a716-446655440000` | Branded UUID of the conversation to send into |

## Deliver callback

The plugin's `deliver` callback is called by OpenClaw when the LLM produces a response:

```
LLM response → deliver(payload, {kind: "final"}) → agent/message/send {conversationId, parts}
```

The deliver callback sends the response via `agent/message/send` to the
originating conversation, reusing the `conversationId` captured from the
inbound message. Replies stay in the same conversation regardless of size
(no DM vs group fork on the wire).

## Reply threading

The plugin sets no per-message reply target: the outbound message carries
only the originating `conversationId`, so threading context is the
conversation itself.