Start (Agentflow Node)

The Start node is the entry point for every Agentflow workflow in InnoSynth-Forjinn. It defines how the workflow initiates, whether through a direct chat input or a structured form, and allows for initial configuration of the flow's state and memory behavior.

Purpose

The Start node is crucial for:

• Defining Entry Point: Marking where the workflow begins execution.
• Input Handling: Specifying whether the workflow expects a free-form chat message or structured data via a form.
• Initial State: Setting up initial variables or a runtime state for the workflow.
• Memory Control: Configuring whether the workflow should start with a fresh memory or persist state across sessions.

Appearance on Canvas

(Image: Placeholder for the Start node icon/appearance on the canvas)

Configuration Parameters

The Start node offers several parameters to customize the workflow's initiation.

1. Input Type (Required)

• Label: Input Type
• Type: options
• Default: chatInput
• Options: Chat Input, Form Input
• Description: Determines how the user interacts with the workflow at its start.
  • Chat Input: The workflow begins with a standard chat message from the user.
  • Form Input: The user is presented with a form to fill out before the workflow proceeds.

2. Form Title (Optional for Form Input)

• Label: Form Title
• Type: string
• Placeholder: Please Fill Out The Form
• Description: (Visible when Input Type is Form Input) The title displayed at the top of the form.

3. Form Description (Optional for Form Input)

• Label: Form Description
• Type: string
• Placeholder: Complete all fields below to continue
• Description: (Visible when Input Type is Form Input) A brief description or instructions for the user filling out the form.

4. Form Input Types (Optional for Form Input)

• Label: Form Input Types
• Type: array of objects
• Description: (Visible when Input Type is Form Input) Define the individual fields of the form that the user needs to complete.
  • Type: The data type of the form field (String, Number, Boolean, Options).
  • Label: The user-friendly label displayed for the input field.
  • Variable Name: The internal variable name (must be camel case, e.g., firstName) that will hold the input's value in the workflow's state.
  • Add Options: (Visible for Options type) An array of string options for a dropdown or radio button.

5. Ephemeral Memory (Optional)

• Label: Ephemeral Memory
• Type: boolean
• Description: If true, the workflow will start with a fresh memory for every execution, meaning past chat history from previous sessions will not be retained. This is useful for stateless interactions.

6. Flow State (Optional)

• Label: Flow State
• Type: array of objects
• Description: Define initial key-value pairs that will be added to the workflow's runtime state when it starts. These can be accessed as variables throughout the flow.
  • Key: The name of the state variable (e.g., userName).
  • Value: The initial value of the state variable (e.g., Guest).

7. Persist State (Optional)

• Label: Persist State
• Type: boolean
• Description: If true, the workflow's state will be persisted across sessions, allowing the workflow to remember information from previous interactions with the same user. This is often used in conjunction with memory.

Inputs & Outputs

• Input: The Start node does not have a visible input port, as it is the beginning of the workflow.
• Output: Produces the initial input (chat message or form data) and the configured flow state, which can then be consumed by subsequent nodes.

Example Usage: Customer Onboarding Form

Imagine an onboarding workflow that collects user details via a form.

1. Drag a Start node onto the canvas.
2. Configure Input Type: Form Input
3. Set Form Title: Welcome to InnoSynth-Forjinn!
4. Set Form Description: Please provide your details to get started.
5. Configure Form Input Types:
   • Type: String, Label: First Name, Variable Name: firstName
   • Type: String, Label: Last Name, Variable Name: lastName
   • Type: Options, Label: Role, Variable Name: userRole, Options: User, Admin, Developer
6. Connect to an LLM node: The LLM node can then use {{firstName}}, {{lastName}}, and {{userRole}} variables to personalize a welcome message.

This setup ensures that the workflow starts by collecting structured information from the user.