LLMMessagePublishedEvent
Section ID: DOC-API-EVENT-u1s768tpmf#overview
Domain event published when a new assistant/tool message is produced. Use this in a guide: Event catalog · Automate recurring agent work
Payload
Section ID: DOC-API-EVENT-u1s768tpmf#payload
Payload fields: LLMMessagePublishedEvent.
Payload examples
Section ID: DOC-API-EVENT-u1s768tpmf#examples
These are illustrations of the selected payload Schema, not complete delivery envelopes. Transport metadata is supplied by the platform.
event-llm-message-published
Section ID: DOC-API-EVENT-u1s768tpmf#example-event-llm-message-published
Illustrative payload, not a captured delivery. Identifiers, tool names and outcomes are examples; omitted fields depend on the event.
API JSON uses JSON field names (camelCase).
{
"message": {
"role": "ROLE_ASSISTANT",
"content": [
{
"type": "CONTENT_PART_TYPE_TEXT",
"content": "Here is your daily briefing."
}
],
"messageId": "924ad207-f757-4b1f-bf41-8344ce32dd01",
"sequence": "2",
"generatedBy": "9d4c2e1f-27b1-4304-ae54-af7fe876df31"
}
}
Notes
Section ID: DOC-API-EVENT-u1s768tpmf#notes
In the live conversation view, messages append to the message history. Message sequence identifies each entry; repeated delivery updates the same entry.
Event-specific delivery guarantees, ordering, retention and lifecycle status are unspecified.
Audiences
Section ID: DOC-API-EVENT-u1s768tpmf#audiences
-
Audience: Live view Current conversation client projection.
-
Audience: Tenant webhook Sent to subscribed tenant webhook endpoints.
Delivery and lifecycle
Section ID: DOC-API-EVENT-u1s768tpmf#declared-intent
- Live write intent: Append
Live destination meaning
Section ID: DOC-API-EVENT-u1s768tpmf#live-destination-meaning
Conversation message view, with each message addressed by its sequence.
Live child key meaning
Section ID: DOC-API-EVENT-u1s768tpmf#live-child-key-meaning
Message sequence identifies the entry; repeated delivery updates that same entry.
Document ID: DOC-API-EVENT-u1s768tpmf