logo
Documentación
OverviewUser GuideAPI ReferenceBest PracticeCHANGELOG
Buscar
Español
User Guide / Agent / FlowAgent / Flow Component
Flow Components
Última actualización：over 1 year ago

Flow Components

LLMs

Supports multiple vendors and versions of LLM models, such as OpenAI, Claude, Gemini, ChatGLM, llama, and other mainstream commercial/open-source models. LLMs can provide AI responses and output results based on role prompts, context, tools, and reference knowledge settings.
image-20240923154124533

Knowledge Retrieval

This component supports multiple Embedding models and can retrieve knowledge through semantic/keyword/hybrid search, with rerank models optimizing the final ranking. It retrieves the most relevant and matching reference knowledge data from the knowledge base to effectively address LLM hallucinations and deficiencies in professional knowledge.
image-20240923154421149

Branch Judgment

This component uses input information, based on component configuration and LLM capabilities, to determine the input's intent through natural language and outputs via corresponding branches. The branch judgment component may trigger one branch or multiple branches, extracting content with varying intents from the user's query and passing it to the respective branches.
image-20240923154556054

Conditional Judgment

This component uses LLM to determine whether conditions are met based on user-defined "rules for condition fulfillment." If conditions are met, the if branch is triggered; otherwise, the else branch is triggered. Users can define "rules for condition fulfillment" using natural language, regular expressions, or mathematical expressions.
Unlike the Rule Judgment component's regular matching approach, this component leverages LLM's natural language understanding capabilities to comprehend the input content and make judgments based on the results of natural language understanding.
image-20240923154747121

Card Messages

This component does not receive input information from upstream components. When triggered, the Agent can respond with card messages, enhancing the user experience. Card message types include text cards, image-text cards, video cards, map cards, and form cards. It also supports capabilities such as making calls, sending emails, and waking up apps.

  • Text: Outputs text information.
  • Card: Outputs card information. Cards can be configured with rich information such as titles, images, videos, locations, button actions, etc.
  • Form: Outputs form information. Forms can be configured with input fields and submission addresses.
  • JSON: Outputs in JSON structure, suitable for scenarios where submission to APIs is required downstream.
    image-20240923155340785

Human Service

The human service function enables developers to integrate third-party customer service systems to respond to FlowAgent users' requests for human support. Currently, it supports integration with third-party customer service systems such as Intercom, Livechat, Sobot, Zoho, and Webhook.

How to Enable Human Service

  1. Add the "Human Service" component to the FlowAgent canvas.
  2. Complete the authentication configuration of the third-party human service system to ensure successful message communication.
  3. Set working hours, supported message types, etc., in the human service component according to the actual situation of the enterprise.
  4. In the FlowAgent chat window, users can initiate human service requests to access human support.

Configuring Human Service Authentication

Currently, integration with third-party human service systems such as Intercom, Livechat, Sobot, Zoho, and Webhook is supported, enabling users' human service requests to be transferred to human customer service personnel.
Please refer to the configuration steps in Agent-Human Service to complete the authentication process.

Configuring Human Service

In Flow, multiple human service components are allowed to exist simultaneously. When multiple human service components are triggered, the system only allows the first triggered human service component to be activated normally.

  • Other triggered human service components will not be activated and cannot provide services to users.
  • Once a human service component is successfully activated, the subsequent Flow process will no longer proceed.
    Please refer to Agent-Human Service to complete the configuration of the human service component.

Triggering Human Service Requests

Unlike Agents, the human service component in FlowAgent is triggered by upstream connected components. When trigger conditions are met, the human service component will automatically run.
Once the human service component is successfully activated, the system will forcibly interrupt all other components with unfinished responses and directly enter the human service business process. Users can exchange unlimited rounds of messages with the human service system, and both users and human customer service personnel can actively close the current human service conversation.