AI Flowchart Nodes
Last updated
Was this helpful?
Last updated
Was this helpful?
With this new node on your Modeler Palette, you can enable your application to start up a new conversation or send messages to existing conversations with an AI Agent. Each interaction with an Agent is part of a conversation with its own context. So each user interacting with an Agent starts up their own conversation and its own context first, this makes sure users can not access each others conversational context.
To start up a conversation, the AI Agent Conversation node is used, this node gives two options when used in the flowchart.
Create conversation: This is a required step to set up the conversation between user and Agent. This may in future change to show "Start Agent".
Send message: Send a prompt or message to an Agent without the user's interaction. This can be used to invoke an Agent's function for example. This may in future change to show "Prompt Agent", or "Call Agent" or something similar.
Creating a conversation is essential for the first time a user interacts with an Agent. This conversation establishes the conversational context using the context fields from the Agent's properties, which can be set as part of the create conversation node. Each time a conversation is created, it is specific to that user. When the user returns to the conversation, it needs to be started up again, but it will use the same context.
Conversation ID: This unique identifier tracks the conversation, ensuring that each session is distinct and can be referenced independently. This field is required and must be mapped to a writable Text field in your Data model.
Exits
Default: used when the conversation is successfully created.
Error: used when issues arise during the creation.
Assign Context: This button opens the Assign context overlay, here you can set the values of the Agent's conversational context fields.
The Send Message node is used when the application needs to send a message to the Agent or invoke a function on the Agent, without requiring user interaction. This node allows for interaction with the Agent within an established conversation.
In our next update, the Send Message may get an option to operate asynchronously - to indicate that a direct response is not awaited and the work may be completed and feedback provided through functions.
Properties
Conversation ID Expression Field (Text): This field specifies the unique identifier for the conversation, ensuring the message is sent within the correct session.
Message Expression Field (Text): This field contains the text of the message to be sent to the Agent.
Response Message Datafield (Data Model Field): This field captures the Agent's response, storing it within the application's data model.
Future implementations may provide different fields to provide the input to the Agent:
Prompt: what you want the Agent to do - most likley static text;
Payload: a json-like structure to pass to the LLM in conjunction with the prompt.
Exits:
Default: Used when the message is successfully sent and a response is received.
Error: Used when issues arise during the message sending process.
