Skip to main content

​
Node Overview

Nodes are the building blocks of your Kaie workflows. Each node performs a specific function and can be connected to other nodes to create complex automation flows.

​
Message Nodes

​
Text Message Node

Send text messages to customers through any connected channel.
  • Message Content: The text to send
  • Channel: Which communication channel to use
  • Formatting: Bold, italic, emoji support
  • Variables: Insert dynamic content using variables
  • Welcome messages
  • Confirmation messages
  • Status updates
  • General communication

​
Rich Media Node

Send images, videos, documents, and other media files.
  • Images (JPG, PNG, GIF)
  • Videos (MP4, MOV)
  • Documents (PDF, DOC, XLS)
  • Audio files (MP3, WAV)
  • File Source: Upload or URL
  • Caption: Optional text description
  • Thumbnail: Custom thumbnail for videos

​
Template Message Node

Send pre-approved message templates (required for some channels like WhatsApp Business).
  • Must be pre-approved by platform
  • Follow specific formatting rules
  • Include required parameters
  • Template ID: Select from approved templates
  • Parameters: Fill in dynamic values
  • Language: Choose appropriate language

​
AI & Intelligence Nodes

​
AI Response Node

Generate intelligent responses using the AI Brain system.
  • Response Type: Conversational, structured, or hybrid
  • Knowledge Base: Select which knowledge base to use
  • Personality: Set tone and style (professional, friendly, etc.)
  • Context Length: How much conversation history to consider
  • Confidence Threshold: Minimum confidence for auto-responses
  • Fallback Behavior: What to do when AI is uncertain
  • Learning Mode: Enable continuous learning from interactions

​
Sentiment Analysis Node

Analyze customer sentiment and emotions in their messages.
  • Emotion Detection: Happy, sad, angry, frustrated, etc.
  • Sentiment Score: Positive, negative, or neutral
  • Urgency Level: Low, medium, or high priority
  • Route frustrated customers to human agents
  • Adjust response tone based on sentiment
  • Prioritize urgent issues

​
Intent Recognition Node

Identify what the customer wants to accomplish.
  • Information Request: Asking for product details
  • Problem Report: Reporting an issue or bug
  • Purchase Intent: Showing interest in buying
  • Support Request: Need help with existing product
  • Intent Categories: Define custom intent categories
  • Confidence Threshold: Minimum confidence for classification
  • Fallback Intent: Default when intent is unclear

​
Logic & Control Nodes

​
Condition Node

Make decisions based on customer input or workflow data.
  • Text Contains: Check if message contains specific words
  • Variable Comparison: Compare stored variables
  • Time-based: Check current time or date
  • External Data: Query external APIs or databases
  • AND: All conditions must be true
  • OR: Any condition can be true
  • NOT: Condition must be false
  • Complex: Combine multiple conditions

​
Switch Node

Route workflow to different paths based on multiple conditions.
  • Input Variable: What to evaluate
  • Cases: Different values and their corresponding paths
  • Default Case: What to do if no cases match
  • Route different product inquiries
  • Handle multiple language preferences
  • Direct to different departments

​
Loop Node

Repeat a section of the workflow multiple times.
  • Count Loop: Repeat a specific number of times
  • While Loop: Continue while condition is true
  • For Each: Loop through a list of items
  • Loop Condition: When to stop looping
  • Maximum Iterations: Prevent infinite loops
  • Loop Variables: Variables available in each iteration

​
Data & Integration Nodes

​
Variable Node

Store, retrieve, or modify workflow variables.
  • Text: String values
  • Number: Numeric values
  • Boolean: True/false values
  • Object: Complex data structures
  • Set: Assign a value to a variable
  • Get: Retrieve a variable’s value
  • Update: Modify an existing variable
  • Delete: Remove a variable

​
API Call Node

Make HTTP requests to external APIs.
  • Method: GET, POST, PUT, DELETE
  • URL: Endpoint to call
  • Headers: Custom headers
  • Body: Request payload
  • Success Path: What to do on successful response
  • Error Path: What to do on error
  • Response Parsing: Extract data from response

​
Database Node

Query or update database records.
  • SELECT: Retrieve data
  • INSERT: Add new records
  • UPDATE: Modify existing records
  • DELETE: Remove records
  • Connection: Database connection settings
  • Query: SQL query to execute
  • Parameters: Dynamic query parameters

​
Time & Delay Nodes

​
Delay Node

Pause workflow execution for a specified time.
  • Fixed Delay: Wait for a specific duration
  • Random Delay: Wait for a random time within a range
  • Business Hours: Only wait during business hours
  • Duration: How long to wait
  • Unit: Seconds, minutes, hours, days
  • Conditional: Only delay if certain conditions are met

​
Schedule Node

Execute workflow at specific times or intervals.
  • One-time: Execute at a specific date/time
  • Recurring: Execute on a regular schedule
  • Business Hours: Only during business hours
  • Cron Expression: Advanced scheduling syntax
  • Time Zone: Specify timezone for scheduling
  • Conditions: Additional conditions for execution

​
Utility Nodes

​
Log Node

Record information for debugging and monitoring.
  • Info: General information
  • Warning: Potential issues
  • Error: Error conditions
  • Debug: Detailed debugging information
  • Message: What to log
  • Variables: Include variable values
  • Timestamp: Add timestamp to logs

​
Notification Node

Send notifications to team members or external systems.
  • Email: Send email notifications
  • Slack: Send Slack messages
  • SMS: Send text messages
  • Webhook: Call external webhooks
  • Recipients: Who to notify
  • Message: Notification content
  • Priority: High, medium, low priority

​
Best Practices for Using Nodes

  • Group related nodes together
  • Use clear, descriptive names
  • Add comments for complex logic
  • Keep workflows readable and maintainable
  • Always include error handling paths
  • Use fallback nodes for critical operations
  • Log errors for debugging
  • Provide meaningful error messages to customers
  • Minimize unnecessary delays
  • Use efficient data structures
  • Cache frequently accessed data
  • Monitor node execution times