Skip to main content

Overview

Kinbox Automation enables you to build sophisticated workflows that handle routine tasks, qualify leads, route conversations, and integrate with external systems - all without writing code. Create intelligent chatbots and automation scenarios that work 24/7 to improve efficiency and customer satisfaction.
Automation in Kinbox includes Bots (conversational flows) and Scenarios (backend workflows) that can be triggered by events or scheduled.

Key Features

Visual Bot Builder

Drag-and-drop interface to create conversational flows

Scenario Workflows

Backend automation for complex business logic

Multi-Trigger Support

React to events, schedules, webhooks, and API calls

External Integrations

Connect with CRMs, APIs, databases, and third-party services

Bots (Conversational Automation)

Bot Capabilities

Bots can interact with customers through structured conversations:
Available Bot Actions:
  • Send Message: Send text, media, or rich content
  • Data Entry: Collect and validate user input
  • Decision: Branch logic based on conditions
  • CRM: Create or update deals
  • Integration: Call external APIs or CRM systems
  • Assign Conversation: Route to agents or groups
  • Apply Tag: Categorize conversations
  • Update Contact: Modify contact information
  • Delay: Wait before next action
  • Transfer to Agent: Hand off to human support
  • End Bot: Complete the automation

Creating a Bot

1

Design Conversation Flow

Map out the conversation journey from greeting to resolution
2

Add Actions

Drag bot action blocks into your flow
3

Configure Logic

Set up decision points and conditions
4

Connect Integrations

Link to external systems for data sync
5

Test Bot

Use the simulator to test all conversation paths
6

Deploy

Activate bot for specific channels or all channels

Bot Actions in Detail

Message Options:
  • Plain text with variables
  • Rich formatting (bold, italic)
  • Media attachments (images, videos, documents)
  • Natural typing simulation (appears human-like)
  • Typing delay configuration
  • Quick reply buttons
Variable Substitution:
Hello {{contact.name}}!

Your order #{{order_number}} is ready.
Total: {{currency}} {{total_amount}}
Collect User Input:
  • Text input
  • Number input
  • Email validation
  • Phone validation
  • Date/time
  • File upload
  • Button selections
  • Custom validation rules
Validation Options:
  • Required fields
  • Format validation (email, phone, CPF, etc.)
  • Min/max length
  • Numeric ranges
  • Regular expressions
Rating/Evaluation:
  • Collect customer satisfaction ratings (1-5)
  • Request feedback reasons
  • Trigger actions based on rating
Conditional Branching:Create “if-then” logic based on:
  • User responses
  • Contact attributes
  • Custom field values
  • Business hours
  • Agent availability
  • Conversation count
  • Deal status
  • Tag presence
  • Integration responses
Multiple Conditions:
  • AND/OR logic
  • “Any” option for flexible matching
  • Nested conditions
  • Default/fallback paths
Deal Management:Create Deal:
{
  "action": "create_deal",
  "funnel": "Sales Pipeline",
  "stage": "New Lead",
  "name": "{{contact.name}} - {{product_interest}}",
  "value": "{{quoted_value}}",
  "custom_fields": {
    "source": "WhatsApp Bot",
    "urgency": "{{urgency_level}}"
  }
}
Update Deal:
  • Change stage
  • Update fields
  • Change owner
  • Select specific funnel(s)
  • Add products
API Requests:
  • HTTP methods (GET, POST, PUT, DELETE)
  • Headers and authentication
  • Request body with variables
  • Response parsing
  • Error handling
  • Test mode for debugging
CRM Integration:
  • HubSpot: Create/update contacts, deals, custom objects
  • RD Station: Create contacts, send conversion events
  • Zoho: Create opportunities, update fields
  • Bitrix: Field mapping, custom operations

Bot Triggers

When Bots Start:

New Conversation

Automatically start when customer sends first message

Keyword Trigger

Start when specific keywords are detected

Manual Start

Agent manually starts bot from conversation

Specific Stage

Start bot at a particular step (useful for deals)
Channel Configuration:
  • Enable for all channels
  • Select specific channels
  • Different bots for different channels

Bot Features

Simulate Human Behavior:
  • Typing indicators before messages
  • Configurable delay based on message length
  • More realistic customer experience
  • Reduces perception of automation
Great for maintaining conversational feel while automating responses.

Scenarios (Backend Workflows)

What are Scenarios?

Scenarios are powerful backend automations that run without customer interaction:
  • Process data from external sources
  • Schedule recurring tasks
  • Sync information between systems
  • Trigger complex multi-step workflows
  • Handle webhook events
  • Integrate multiple services

Scenario Actions

  • Find Contact: Search for existing contacts
  • Create Contact: Add new contacts to database
  • Update Contact: Modify contact information
  • Find Conversation: Locate conversations by criteria
  • Create Conversation: Start new conversation
  • Send Message: Send messages to contacts
  • Create Deal: Generate CRM opportunities
  • Update Deal: Modify deal information
  • Apply Tag: Add tags to contacts or conversations
  • HTTP Request: Call external APIs
  • Conditional Logic: Branch based on data
  • Variable Assignment: Store and manipulate data
  • Loop: Iterate over arrays or lists
  • Error Handling: Catch and handle failures

Scenario Triggers

Inbound Webhooks:Receive data from external systems:
POST https://api4.kinbox.com.br/v3/workflows/webhook/{webhook_id}
Content-Type: application/json

{
  "customer_id": "12345",
  "event": "purchase_completed",
  "amount": 150.00,
  "product": "Premium Plan"
}
Use webhook data in scenario variables.

HTTP Request Action

Make API calls to external services:
{
  "method": "GET",
  "url": "https://api.example.com/users/{{contact_id}}",
  "headers": {
    "Authorization": "Bearer {{api_token}}",
    "Content-Type": "application/json"
  }
}
Response Handling:
  • Parse JSON responses
  • Extract specific fields
  • Use response data in subsequent actions
  • Error handling and retries

Automation Rules

Classic Automations

Simple trigger-action automations: Common Triggers:
  • New contact without recent conversation
  • Conversation assigned
  • Conversation closed
  • Message received outside business hours
  • Tag applied
  • Custom field updated
  • Time pending (conversation waiting)
  • Deal stage changed
Actions:
  • Send message
  • Start bot
  • Assign conversation
  • Apply/remove tag
  • Update contact
  • Create task
  • Save messages to CRM
  • Send notification

Auto-Assignment

Distribute conversations automatically:

Round Robin

Distribute evenly among available agents

Load Balanced

Consider current conversation count per agent

Last Agent

Assign to last agent who served the contact

Group Based

Assign to specific groups or teams
Assignment Rules:
  • Only assign to online agents
  • Respect availability status
  • Consider business hours
  • Filter by agent groups
  • Priority-based assignment

Advanced Features

Delay and Scheduling

Bot Delays:
  • Delay next action (seconds, minutes, hours, days)
  • Maximum delay: 7 days
  • Continue bot after delay
  • Cancel delay if customer responds
Use Cases:
  • Follow-up sequences
  • Drip campaigns
  • Reminder messages
  • Scheduled check-ins

Variables and Context

System Variables:
  • {{contact.name}} - Contact name
  • {{contact.phone}} - Phone number
  • {{contact.email}} - Email address
  • {{conversation.id}} - Conversation ID
  • {{agent.name}} - Assigned agent name
  • {{current_date}} - Current date
  • {{current_time}} - Current time
Custom Variables:
  • Store user inputs from bot
  • Data from API responses
  • Calculated values
  • Integration responses
Variable Operations:
  • String concatenation
  • Math operations
  • Date formatting
  • Conditional values

Testing and Debugging

Test Bot Flows:
  • Simulate conversations
  • Test all decision paths
  • Verify integrations (in test mode)
  • Check variable substitution
  • Validate data entry
  • No real messages sent

Integration Examples

Lead Qualification Bot

1

Greet Customer

Send welcome message when conversation starts
2

Collect Information

Ask for name, email, company, and needs
3

Qualify Lead

Use decision logic to score lead (budget, timeline, authority)
4

Create Deal

If qualified, create deal in appropriate funnel stage
5

Route Conversation

Assign to sales team or support based on qualification
6

Sync to CRM

Push data to HubSpot or other CRM

RD Station Marketing Integration

Automatic Event Tracking:
  • Send conversion events when contacts are updated via bot
  • Create contacts in RD Station Marketing
  • Map custom fields between systems
  • Track customer journey
  • Trigger RD Station automations

HubSpot Integration

Available via Bot Actions:
  • Create/update HubSpot contacts
  • Create/update deals
  • Manage custom objects
  • Field mapping configuration
  • Two-way sync
HubSpot App:
  • View Kinbox data in HubSpot
  • Trigger bots from HubSpot
  • Apply tags
  • Create contacts
  • Assign conversations

API Management

List Contacts

Manage contacts used in automations

Manage Campaigns

Create automated campaigns via API

Webhooks

Receive automation events in real-time

Custom Fields

Access custom field data for automations

Best Practices

1

Start Simple

Begin with basic flows and add complexity gradually
2

Test Thoroughly

Use the simulator to test all conversation paths
3

Plan for Errors

Add fallback options and error handling
4

Keep It Conversational

Write natural, friendly messages that sound human
5

Monitor Performance

Review execution logs and optimize based on data
6

Provide Exit Options

Always give customers a way to reach a human agent
Common Pitfalls:
  • Infinite loops with “Consider Last Message” enabled
  • Missing fallback paths in decision logic
  • Not testing integration actions before deployment
  • Overly complex flows that confuse users
Pro Tip: Clone successful bots and scenarios to use as templates for new automations. This saves time and ensures consistency.

Build docs developers (and LLMs) love