maestro
latest
false
Maestro user guide
- Introduction
- Getting started
- Building with Maestro BPMN
- Understanding Maestro BPMN modeling
- Opening the modeling canvas
- Modeling your process
- Aligning and connecting BPMN elements
- Autopilot for Maestro (Preview)
- Process Repository
- Implementing a simple BPMN process
- Implementing a complex BPMN process
- Debugging
- Simulating
- Common implementation scenarios
- Building with Maestro Case
- Introduction to Maestro Case
- Maestro BPMN vs. Maestro Case: when to use case management
- The Maestro Case lifecycle: from event trigger to app experience
- Build your first case with Maestro Case
- Build a Maestro Case with a coding agent (preview)
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Exit rules and early stage termination
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Case Manager input and output contract
- Maestro Case component dictionary
- Building with Maestro Flow
- Integrations
- Operating
- Monitoring
- Optimizing
- Reference information
Node that retrieves the latest conversation context, including recent chat history and user profile information.
What it does
Retrieves the latest conversation context — the recent chat history and user profile information.
Important:
Wait for Message already returns the conversation context as its output after the user sends a chat message. The Get Conversation Context node is generally not needed for building chat loops, and should only be used for rarer cases where a downstream node needs the current conversation state but shouldn't pause for the next user message.
Inputs
| Field | Description |
|---|---|
| Conversation ID | The ID of the conversation to read. Bind to the conversation trigger's output, for example $vars.conversationTrigger1.output.conversationId. |
| Exchange limit | Maximum number of past exchanges to include in the returned conversation history. Determines how many past messages in the conversation history are returned. |
Output
| Field | Description |
|---|---|
conversationContext | The latest conversation context, including the message history. |
The conversationContext contains the following fields:
| Field | Description |
|---|---|
latestExchangeId | Identifier of the most recent exchange (back-and-forth turn). Use as the Exchange ID input to Send Message when replying to the conversation. |
messages | The recent conversation history, including both the user's and Flow's messages. Exchange limit determines how many past exchanges to include. |
userSettings | User-level profile fields, configurable by the end-user on the channels. |
Usage examples
Reference the full context in a downstream Conversational Agent node:
$vars.getConversationContext1.output.conversationContext
$vars.getConversationContext1.output.conversationContext
Reference the latestExchangeId in a downstream Send Message node:
$vars.getConversationContext1.output.conversationContext.latestExchangeId
$vars.getConversationContext1.output.conversationContext.latestExchangeId
Related pages
- Wait for Message — the default way to read conversation context.
- Chat — full palette of chat conversational nodes.
- Build a chat agent workflow — end-to-end walkthrough.
- Chat deployment — publish and expose the Flow through various channels.