Workflow Nodes

​

Overview

Start → Validate → API Call → Transform → Condition → End
                                              ↓
                                         Error Handler

​

Node Types

​

Start Node

​

Configuration

inputs:
  order_id:
    type: string
    description: The order identifier
    required: true

  include_details:
    type: boolean
    description: Whether to include full details
    default: false

outputs:
  - name: order_status
    type: object

​

Accessing Inputs in Downstream Nodes

​

End Node

​

Configuration

1. Custom Name: Enter an appropriate name for the node.
2. Name (key): Select a key from the Manage Output section.
3. Value: Map to a node output using {{context. and select the variable.

// Example value mapping
{{context.steps.summarization.output}}

​

API Node

​

Key Capabilities

• Protocols: REST and SOAP
• Methods: GET, POST, PUT, DELETE, PATCH
• Auth: Pre-authorized tokens or per-user runtime authorization
• Modes: Synchronous or Asynchronous
• Body formats: JSON, XML, Form URL Encoded, Custom
• Testing: Preview API responses before finalizing setup

​

Common Use Cases

• Data enrichment (fetch user, order, or product details)
• Webhook triggers based on workflow decisions
• Identity verification, fraud checks, or compliance validation
• Sending alerts or updating external dashboards

​

Configuration

• Pre-authorize the integration: Use system-level credentials shared across all users.
• Allow users to authorize: Each user authenticates at runtime (for example, Google Drive).

​

Accessing Output

{{context.steps.APINodeName.output.data}}
{{context.steps.APINodeName.output.status}}
// Or via Start node reference:
{{context.steps.Start.APINodeName}}

​

Function Node

​

Key Capabilities

• Write Code: Author inline scripts in the built-in editor
• Custom Function: Invoke a function from a deployed script library
• Memory Access: Read/write Agent Memory stores for stateful logic
• Supported languages: JavaScript (async with await), Python (synchronous)

​

Common Use Cases

• Data transformation and format conversion
• Custom validation and business rule logic
• Mathematical calculations and statistical analysis
• String manipulation and regex operations

​

Option 1 — Write Code

1. Select Write Code and open the script editor.
2. Choose JavaScript or Python.
3. Use context variables for dynamic inputs (see syntax below).
4. Click Run to test the script.

const order = context.steps.FetchOrder.output;
const transformed = {
  id: order.order_id,
  total: order.items.reduce((sum, item) => sum + item.price, 0),
  itemCount: order.items.length,
  formattedDate: new Date(order.created_at).toLocaleDateString()
};
return transformed;

​

Option 2 — Custom Function

1. Select Script: Choose a deployed script from the Script name list. Deploy scripts via Settings > Manage custom scripts.
2. Select Function: Choose a function from the Function name list. Only one function per node; only deployed scripts are listed.
3. Map Input Arguments: Assign static or dynamic values to each argument. Select the correct data type (String, Number, JSON, Boolean). Type {{ to trigger context variable suggestions.
4. Test: Click Test, enter values in the Input panel, then click Execute.

Output (result key) is saved to {{context.steps.functionnodename.output}}. Errors (stderr) are saved to {{context.steps.functionnodename.error}}.

​

Agent Memory Access

# Read from memory
retrieved = memory.get_content(memory_store_name="my-notes", projections={"note": 1})

# Write to memory
memory.set_content(memory_store_name="my-notes", content={"note": "Updated note.", "timestamp": "2025-05-15T10:00:00Z"})

# Delete
memory.delete_content(memory_store_name="my-notes")

​

Accessing Output

{{context.steps.FunctionNodeName.output}}
{{context.steps.FunctionNodeName.error}}

​

Integration Node

​

Key Capabilities

• No-code: Embed prebuilt third-party actions without custom code
• Secure connections: Tested and authenticated service connections
• Auto-generated JSON: Prebuilt payloads from action parameters
• Visual configuration: Configure directly on the canvas

​

Common Use Cases

• CRM and marketing automation (for example, trigger campaigns from captured leads)
• Workflow automation across apps (for example, create a task when a ticket is raised)
• Payment gateway processing
• SaaS tool integrations (CRM, email, e-commerce)

​

Prerequisites

​

Configuration

1. Add Node: Click Integration > + New Integration in the Assets panel or drag onto the canvas.
2. Select Service: Search or browse the integrations list.
3. Node Name: Name the node (letters and numbers only).
4. Connection Name: Select an active, configured connection.
5. Add Action: Click Add Action and select one action (only one action per node).
6. Action Parameters: Fill in parameters for the selected action.
7. Connections: Set On Success and On Failure paths.

​

Managing Actions

​

Accessing Output

{{context.steps.IntegrationNodeName.output}}

​

Condition Node

​

Key Capabilities

• Condition types: IF, ELSE IF, and ELSE.
• Operators: ==, !=, >, <, >=, <=, contains, startsWith, and endsWith.
• Logic combinators: AND or OR for multi-criteria conditions.
• Dynamic references: Context variables and previous node outputs.

​

Common Use Cases

• Route based on classification, type, or priority
• Fallback logic when no match is found
• Validate data before proceeding
• Multi-step filtering with combined conditions

​

Structure

​

Configuration

1. Add the node to the canvas.
2. Node Name: Enter a descriptive name.
3. IF Condition: Enter a context variable (for example, {{context.ambiguous_sub_categories}}), choose an operator, and enter a value or another variable (for example, {{context.steps.NodeName.output}}). Combine multiple criteria with AND/OR.
4. Routing: Set Go To (IF met) and ELSE (IF not met) nodes.

// AND
context.steps.Order.amount > 100 && context.steps.Order.status === "pending"

// OR
context.steps.User.tier === "premium" || context.steps.Order.amount > 500

• A Condition node can be called a maximum of 10 times in a tool flow.
• Standard error: If a condition path has no connected node, the error “Path not defined. Please check the flow.” is displayed.

​

Loop Node

​

Key Capabilities

• Array iteration: Execute child nodes once per item in an input array
• Flexible child nodes: Add Function, API, AI, Condition nodes inside the loop
• Output aggregation: Collect per-iteration results into an output array
• Three error handling strategies: Continue, Terminate, or Remove Failed
• Debug support: Per-iteration inspection in the Debug panel

​

Common Use Cases

• Batch processing (invoices, documents, records)
• API calls on multiple inputs (fetch data per customer ID)
• Bulk notifications (personalized messages to a list)
• Report generation per item in a dataset

​

Configuration

​

Error Handling Options

​

Inside the Loop

// Reference current iteration item
{{currentItem}}

// Current index (via loop context)
{{context.loop.index}}

Only nodes placed inside the loop block execute per iteration. Nodes connected outside run after the loop completes.

​

Accessing Output

{{context.steps.LoopNodeName.output}}
// Returns: [result1, result2, result3, ...]

​

Troubleshooting

​

AI Nodes

​

Text to Text Node

​

Key Capabilities

• Prompt options: Write your own prompt, or choose from the Prompt Hub with version selection
• Model selection: Choose from pre-configured LLM models
• Hyperparameter tuning: Temperature, Top-p, Top-k, Max Tokens
• Structured output: Optional JSON schema for parseable responses
• Tool calling: Enable the model to call up to 3 external tools during execution
• Timeout: 30–180 seconds (default: 60s)

​

Common Use Cases

• Summarization (transcripts, logs, documents)
• Tone or style adjustment
• Content rewriting and reformatting
• Error explanation and log analysis

​

Configuration

• System Prompt: Sets the model’s role. Example: “You are a helpful assistant.”
• Human Prompt: The task or question. Example: “Summarize this error log.” Use {{context.variable_name}} for dynamic values.

​

Accessing Output

{{context.steps.AINodeName.output}}

​

Text to Image Node

​

Key Capabilities

• Positive Prompt: Define what the image should include (style, elements, setting)
• Negative Prompt: Specify what to exclude from the image
• Aspect Ratio: Up to 2048 × 2048 pixels (GPU-dependent)
• Steps: Refinement iterations—25–30 recommended for quality and performance
• Batch Count: Up to 5 image variants per run
• Output: PNG format returned as URLs

​

Supported Models

​

Common Use Cases

• Marketing banners, ads, and promotional visuals
• Content illustration for blogs or newsletters
• Visual prototyping (UI mockups, storyboards)
• A/B testing with multiple image variants

​

Configuration

The node uses an input scanner to detect banned words. Banned topics cause an error in the Debug window.

​

Accessing Output

{{context.steps.TextToImageNodeName.output}}
// Returns PNG image URL(s)

​

Audio to Text Node

​

Key Capabilities

• Model: OpenAI Whisper-1
• Multilingual: Transcribes multiple languages; translates non-English audio to English
• Input: Audio file (upload) or audio URL; max file size 25 MB
• Timestamps: Optional; records when each dialog segment was spoken
• Structured output: Optional JSON schema

​

Supported Formats

• Files larger than 25 MB must be split at logical points to avoid mid-sentence breaks.
• Inverse translation (English to other languages) is not supported.
• Only URLs are supported as input variables—direct file uploads via input variables are not supported.

​

Common Use Cases

• Meeting, lecture, or interview transcription
• Customer support call analysis
• Subtitle and caption generation
• Voice command processing

​

Configuration

​

Accessing Output

{{context.steps.AudioToTextNodeName.output}}

​

Image to Text Node

​

Key Capabilities

• OCR: Extract embedded text from scanned documents, screenshots, and photos
• Image Understanding: Answer questions or generate descriptions from images using prompts
• Multi-model: OpenAI and Anthropic models supported
• Structured output: Optional JSON schema for parseable responses

​

Supported Models

• OpenAI: gpt-4o, gpt-4o-mini
• Anthropic: Claude Sonnet Vision

​

Supported Image Formats

• Only one image URL can be provided at a time.

​

Common Use Cases

• Document digitization (receipts, invoices, scanned forms)
• Image-based content moderation
• Multilingual OCR (printed or handwritten text)
• Extracting insights from diagrams, posters, or infographics

​

Configuration

​

Accessing Output

{{context.steps.ImageToTextNodeName.output}}

​

DocSearch Node

​

Key Capabilities

• RAG-powered: Combines document retrieval with LLM-generated responses
• Search AI integration: Connects to a configured Search AI app to query indexed content
• Dynamic queries: Accepts static text or context variables as input
• Meta filters: Narrow search scope to specific documents or sources (optional)

​

Common Use Cases

• Retrieve relevant policies, manuals, or help articles based on user queries
• Context-aware Q&A grounded in indexed documents
• Internal knowledge base search (wikis, technical docs, training material)

​

Setup Prerequisites

1. Set up a Search AI App: Configure a Search AI application and enable the Answer Generation API scope.
2. Link Search AI in the Platform: Go to Settings > Integrations > Search AI > Link an App. Enter the app credentials, test the connection, and confirm. Use https://platform.kore.ai for the Search AI URL.

​

Configuration

​

Accessing Output

{{context.steps.DocSearch.response.response.answer}}
// Path may vary—check the sample Search AI response for the correct key

​

Human Node

​

Key Capabilities

• Custom input fields: Define fields for the reviewer (Text, Number, Boolean, Date)
• Timeout handling: Set a timeout duration or wait indefinitely
• Sync and Async modes: Determined by the tool’s endpoint configuration
• Three outcome paths: On Success, On Timeout (Terminate or Skip), On Failure

​

Common Use Cases

• Approval workflows (expenses, leave requests, procurement)
• Quality assurance checkpoints before publishing AI-generated output
• Compliance review for sensitive or regulated steps
• Exception handling and escalation for edge cases

​

How It Works

​

Configuration

• Supported types: Text, Number, Boolean, Date
• Set default values and mark required/optional
• Pre-fill with context variables: {{context.user.name}}
• Click Payload preview to inspect the full payload

• No timeout: Waits indefinitely.
• Set timeout: Default 120 seconds (configurable in seconds, minutes, hours, or days).

​

Accessing Reviewer Responses

// Full response payload
{{context.steps.NodeName.output}}

// Specific field
{{context.steps.NodeName.output.Approval}}
{{context.steps.NodeName.output.Comments}}

• Inside Loops: The loop does not advance to the next iteration until the Human node receives a response.
• In Parallel Branches: The branch merge waits for the Human node to complete before continuing.

​

Managing Nodes

​

Adding Nodes

​

Connecting Nodes

• Drag from a node’s output connector to another node’s input.
• Use the Connections tab in the node configuration panel.
• All nodes must connect to Start (directly or indirectly).

​

Constraints

• Maximum 10 outgoing connections per node
• No duplicate connections from the same parent
• No backward loops (prevents cycles)

​

Deleting Nodes

​

Auto Arrange

​

Debugging

• Execution status per node
• Input/output values at each step
• Error messages
• Timing metrics
• Iteration details (for Loop nodes; click the loop icon to drill into individual runs)