izz.ONE icon

izz.ONE

Fetch data from izz.ONE

Overview

This node interacts with the izz.ONE API to continue an existing chat session by sending a message to it. It is useful for scenarios where you want to maintain conversational context across multiple messages, such as customer support chats, interactive assistants, or ongoing dialogue systems. For example, you can continue a chat by providing the chat ID and a new message, optionally specifying datasources, agents, language models, system messages, behavior styles, tags, and whether to stream the response in real-time.

Use Case Examples

  1. Continuing a customer support chat by sending follow-up questions or responses.
  2. Maintaining an interactive assistant session where the conversation context is preserved.
  3. Sending messages to a chat with specific behavior styles like friendly or technical tone.

Properties

Name Meaning
Chat ID The unique identifier for the chat to continue. If not provided, a new chat will be created.
Message The message content to send in the chat.
Datasources Select datasources to use for the chat. If not selected, automatic datasource selection is made. Mixing automatic with other datasources defaults to automatic.
Agent Select an agent to use for the chat. If not selected, no agent will be used.
LLM Model Select a specific large language model (LLM) to use for the chat. If not selected, automatic model selection is made.
System Message A custom system message to influence the chat context or behavior.
LLM Behavior Behavior styles for the language model, such as conversational, friendly, informal, creative, etc.
Tags Optional tags to categorize the message, entered as a comma-separated list.
Streaming If enabled, the response will be streamed back in real-time; otherwise, the full response is returned at once.

Output

JSON

  • msg - The message sent in the chat.
  • id - The chat ID if continuing an existing chat.
  • datasources - Datasources used for the chat.
  • agent - Agent used for the chat.
  • llm - LLM model used for the chat.
  • systemMessage - Custom system message for the chat.
  • behavior - Behavior styles applied to the LLM.
  • tags - Tags categorizing the message.
  • streaming - Indicates if streaming is enabled for the response.

Dependencies

  • Requires an API key credential for izz.ONE API access.

Troubleshooting

  • Ensure the API key credential is correctly configured and has necessary permissions.
  • Verify that the chat ID is valid when continuing a chat; an invalid or missing ID may cause errors.
  • Check network connectivity and the base URL configuration for the izz.ONE API.
  • If streaming is enabled, ensure the client supports handling streamed responses properly.

Links

Discussion