Skip to main content
GraphTypes are specialized data types used for input and output between nodes in the Inworld Node.js Runtime graph system. These types provide structured data handling for various AI processing workflows including LLM interactions, audio processing, tool calls, and more.

Import

import { GraphTypes } from '@inworld/runtime/graph';

// Usage examples
const audioData = new GraphTypes.Audio({ /* audio data */ });
const content = new GraphTypes.Content({ /* content data */ });

Available Types

NameDescriptionCommon Usage
AudioAudio data type for speech processing operations.- Input for RemoteSTTNode
- Output from RemoteTTSNode
- Audio data handling in custom nodes
ClassificationResultClassification analysis results from text or content analysis operations.- Output from classification nodes
- Input for classification-based routing
ContentEncapsulates LLM response content with optional tool calls. The primary output type from LLM chat nodes.- Output from RemoteLLMChatNode
- Input for processing LLM responses
ContentStreamStreaming content responses from LLM nodes, providing real-time text generation.- Output from streaming LLM operations
- Input for real-time response processing
CustomGeneric data type for custom node implementations.- Input/output for custom nodes
- Flexible container for application-specific data
- Used when standard types don’t fit the use case
GoalAdvancementGoal tracking and advancement data for monitoring progress toward objectives.- Output from goal tracking nodes
- Input for progress-based routing
KnowledgeRecordsKnowledge base query results containing retrieved information and metadata.- Output from KnowledgeNode
- Input for processing knowledge base responses
ListToolsResponseResponse containing available tools from MCP (Model Context Protocol) servers.- Output from MCPListToolsNode
- Input for tool selection logic
LLMChatRequestChat request data type for LLM processing, containing conversation history, tools, and configuration.- Input for RemoteLLMChatNode
- Built by LLMChatRequestBuilderNode
MatchedIntentsIntent detection results from natural language understanding.- Output from intent classification nodes
- Input for conditional routing based on detected intents
MatchedKeywordsKeyword matching results from text analysis.- Output from KeywordMatcherNode
- Input for keyword-based routing
MemoryStateMemory and conversation state information for maintaining context across interactions.- Input/output for memory management nodes
- Used for stateful conversation handling
TextChunksOutput from text chunking operations, containing segmented text data.- Output from TextChunkingNode
- Input for processing segmented text
TextStreamStreaming text data for continuous text processing operations.- Input/output for text transformation nodes
- Used in streaming text processing pipelines
ToolCallRequestTool execution request containing function calls and parameters.- Output from tool call parsing nodes
- Input for MCPCallToolNode
ToolCallResponseTool execution response containing results and status information.- Output from MCPCallToolNode
- Input for processing tool execution results
TTSRequestText-to-speech request containing text content and voice configuration.- Input for RemoteTTSNode
- Supports both direct text and streaming input
TTSOutputStreamStreaming audio output from TTS processing operations.- Output from streaming TTS operations
- Used in real-time audio generation scenarios