Skip to main content
Jan 9, 2026

Inbox

Workflow status in conversation list: The inbox conversation list now shows workflow execution status.When a workflow is running for a conversation, you’ll see its current state: Running, Waiting, Handoff, or Failed. This helps you quickly identify conversations where workflows are active or need attention.
Jan 4, 2026

Workflows

App integration tools: AI agent steps can now call pre-configured app integrations as tools.Connect to HubSpot, Slack, Google Sheets, Notion, Airtable, and 2,700+ other apps via Pipedream. Attach integrations to agent steps and let the agent invoke them during conversations.Each tool has:
  • Name: Tool identifier the agent calls
  • Description: Tells the agent when to use this tool
  • App integration: Select a pre-configured integration
The agent provides runtime values for fields marked as “Passed by agent” in the integration config. Pre-configured values are sent automatically.
Jan 3, 2026

Workflows

AI agent function tools: AI agent steps can now call your custom functions as tools during execution.When configuring an AI agent step in the workflow builder, you can now attach function tools that the agent can invoke when needed. The agent receives:
  • Function name and description
  • Input schema (JSON Schema)
  • Full workflow execution context
  • Recent flow events and WhatsApp conversation history (if applicable)
Your function returns data that can update workflow variables (vars) for use in subsequent steps.This enables agents to:
  • Look up data from external APIs
  • Perform calculations or transformations
  • Query databases or search systems
  • Integrate with any external service
Ask about file tool: New built-in tool for analyzing files.Agents can now use ask_about_file to answer questions about PDFs, images, and Office documents (.docx, .xlsx, .pptx). Get file URLs from WhatsApp messages via get_whatsapp_context, then call the tool with your question.Limits: 30MB max, legacy formats (.doc/.xls/.ppt) need conversion to modern format.

Inbox

Message replies and reactions: Inbox now displays emoji reactions and reply context for WhatsApp messages.When viewing conversation threads, you’ll now see:
  • Emoji reactions on individual messages
  • Reply indicators showing which message is being replied to
  • Sender name and preview text for replied-to messages
You can also send replies with context from the inbox by replying to specific messages.
Jan 2, 2026

Kapso Agent

API mode with webhook management: Kapso Agent can now configure and manage webhooks through chat.The API mode (formerly “debugging”) now includes:
  • Create, update, and delete webhooks through natural language
  • Test webhook deliveries and view recent delivery logs
  • Configure project-level and phone-number-level webhooks
  • Set up buffering, custom headers, and retry policies
Ask the agent to “create a webhook for new messages” or “list my webhooks” from any page. The agent will guide you through configuration and validate your setup.Mobile improvements:
  • Floating action button for quick agent access on mobile
  • Full-screen mobile sheet interface
  • Improved responsiveness across all screen sizes
Dec 31, 2025

API changes

Location request interactive message: New interactive message type to request user’s location.Send location_request_message interactive type to display a “Send Location” button. Users can share their current location with one tap.
{
  "type": "interactive",
  "interactive": {
    "type": "location_request_message",
    "body": {
      "text": "Please share your location"
    },
    "action": {
      "name": "send_location"
    }
  }
}
Now available in:
  • WhatsApp API (REST and TypeScript SDK)
  • Workflow builder (Send Interactive step)
See the location request guide for details.
Dec 30, 2025

Features

WhatsApp Ads tracking (CTWA): New tracking and analytics for Click-to-WhatsApp campaigns.When users start conversations through Meta ads or click-to-WhatsApp buttons, Kapso now automatically captures referral data including:
  • Ad headline, body, and media
  • Campaign source and click ID (ctwa_clid)
  • Custom reference parameters
View all referrals in the new “Ads (CTWA)” section under your WhatsApp project. Filter by date range and export to CSV for deeper analysis.Conversations with referral data now show a “CTWA” badge in the inbox for quick identification.
Dec 30, 2025

API changes

WhatsApp AUTHENTICATION templates: Fixed and improved support for OTP authentication templates.Changes:
  • ONE_TAP autofill: Now uses supported_apps array format (replaces deprecated package_name/signature_hash fields)
  • ZERO_TAP: Added support for no-button OTP auto-read
  • Button text: OTP buttons no longer accept text field (Meta generates button text)
  • Validation: Added proper validation for AUTHENTICATION template structure
{
  "type": "OTP",
  "otp_type": "ONE_TAP",
  "supported_apps": [
    {
      "package_name": "com.example.app",
      "signature_hash": "K8a%2FAINcGX7"
    }
  ]
}
See the Authentication templates guide for complete documentation.
Dec 28, 2025

Kapso Agent

Global agent with mode switching: Kapso Agent is now available across your entire dashboard and can switch between specialized modes.Available modes:
  • auto - General assistant with documentation access (default)
  • debugging - Health checks, error analysis, message troubleshooting
  • whatsapp_templates - Template creation, submission to Meta, sending messages
  • whatsapp_flow - WhatsApp Flows JSON editing, data endpoints
The agent automatically detects your current page and adjusts its context. Use the mode selector in the chat sidebar or let the agent switch modes based on your request.
Dec 27, 2025

Kapso Agent

Debug mode: Kapso Agent can now help you diagnose WhatsApp integration issues directly from the dashboard.Available debugging tools:
  • get_project_overview - Health snapshot with connected numbers, plan status, 24h activity
  • check_whatsapp_health - Token validity, messaging health, webhook status
  • get_project_errors - Recent errors from message delivery, API calls, webhooks
  • get_api_logs - External API call logs with status codes and response times
  • get_webhook_deliveries - Webhook delivery attempts to your endpoints
  • get_recent_messages - Recent WhatsApp messages with status
  • get_message_details - Full message lifecycle including delivery errors
  • lookup_conversation - Find conversations by phone number
Access debug mode from the Logs page or Messages page in your project dashboard.
Dec 24, 2024

API changes

Update workflow execution status: New PATCH endpoint to manually control workflow lifecycle.
PATCH /workflow_executions/{execution_id}
{
  "workflow_execution": {
    "status": "ended"
  }
}
Allowed transitions: ended, handoff, waiting. Use this to end workflows from external triggers, transfer to human agents, or pause executions programmatically.
Dec 23, 2025

Workflows

Observer mode chat: Agent steps now support interactive chat when running in observer mode (outbound messages disabled).New observer_prompt_mode setting:
  • interactive_chat (default) - Chat with the agent via the Workflow Chat sidebar in the inbox
  • analysis_only - Agent runs non-interactively, no chat interface
Use interactive mode for workflows that need human review or operator input. The Workflow Chat sidebar appears in the inbox when viewing conversations with active observer-mode executions.
Dec 22, 2024 - 17:40

Workflows

Send data to WhatsApp Flows: The send interactive step now supports passing dynamic data to WhatsApp Flows via flow_action_payload.
{
  "node_type": "send_interactive",
  "config": {
    "interactive_type": "flow",
    "body_text": "Complete checkout",
    "flow_id": "123456789012345",
    "flow_cta": "Continue",
    "flow_action": "navigate",
    "flow_action_payload": {
      "screen": "CHECKOUT",
      "data": {
        "phone_number": "{{context.phone_number}}",
        "cart_total": "{{vars.total}}"
      }
    }
  }
}
Variables in flow_action_payload are automatically substituted from the workflow context. Useful for pre-filling forms, passing user data, or customizing the flow experience based on conversation state.
Dec 16, 2025 - 21:00

API changes

Resume workflow with variables: The resume endpoint now accepts optional variables parameter to update execution context when resuming a waiting workflow.
POST /workflow_executions/{id}/resume
{
  "message": {
    "data": "yes, proceed"
  },
  "variables": {
    "estado": "retomado",
    "user_choice": "confirmed"
  }
}
Variables are merged into the execution context’s vars section. Existing variables with the same key are overwritten. Useful for capturing user responses or updating workflow state when resuming from a wait step.
Dec 16, 2025 - 14:45

Workflows

Call workflow step: New step type for executing workflows as subroutines.
{
  "node_type": "call",
  "config": {
    "workflow_id": "abc123",
    "save_error_to": "validation_error"
  }
}
Parent workflow pauses while child executes. Variables automatically merge back on completion. Includes recursion protection (max depth 10) and cycle detection. Use for reusable validation, multi-step processes, and conditional sub-workflows.
Dec 15, 2025 - 12:00

API changes

Template sync pagination: Fixed template sync to retrieve all templates from Meta. Previously, sync would only fetch the first 100 templates when you had more than 100 approved templates in your WhatsApp Business Account.If you have more than 100 templates, re-run sync to import all templates:
POST /whatsapp_templates/sync
This fix ensures complete template synchronization regardless of template count.
Dec 14, 2025 - 19:50

Workflows

Template parameters: Send Template nodes now support Meta’s native components format for template parameters.
{
  "parameters": [
    {
      "type": "BODY",
      "parameters": [
        { "type": "text", "text": "{{user_name}}" },
        { "type": "text", "text": "{{order_id}}" }
      ]
    }
  ]
}
Use this format for multi-component templates (header, body, buttons) and named parameters. Legacy array format still supported.
Dec 13, 2025 - 18:35

Webhooks

Status history: message.kapso.statuses now includes ordered history of raw Meta status events.
{
  "message": {
    "kapso": {
      "status": "failed",
      "statuses": [
        { "status": "sent", "timestamp": "1700000000", ... },
        { "status": "delivered", "timestamp": "1700000005", ... },
        { "status": "failed", "timestamp": "1700000010", "errors": [...] }
      ]
    }
  }
}
Track full message lifecycle and understand failure causes. Array only appears when status events exist.
Dec 12, 2025 - 16:00

API changes

Workflow execution ID: POST /workflows/{id}/executions now returns an id field in addition to tracking_id. Use the execution ID to retrieve full execution details or resume waiting executions.
{
  "data": {
    "message": "Workflow execution initiated",
    "workflow_id": "uuid",
    "id": "uuid",
    "tracking_id": "uuid"
  }
}
The id field is the execution identifier you can use with:
  • GET /workflow_executions/{id} - Retrieve full execution details
  • POST /workflow_executions/{id}/resume - Resume waiting executions
Dec 9, 2025 - 14:00

WhatsApp Flows

Build interactive forms that run natively inside WhatsApp. Users tap through screens, fill out fields, and submit data - all without leaving the chat.
  • Static flows - Define all content in Flow JSON, no server required
  • Dynamic flows - Fetch data at runtime using Kapso Functions as your data endpoint
  • Automatic encryption - Kapso handles Meta’s encryption requirements
  • Response collection - Receive completions via webhooks or view in dashboard
Use cases: lead capture, appointment booking, surveys, order forms, customer intake.

WhatsApp Flows docs

Get started with WhatsApp Flows
Dec 8, 2025 - 14:00

Inbox

Browser notifications - Enable desktop notifications to get alerted when new messages arrive.

Workflows

Execution webhooks - Get notified when workflow executions require human intervention or fail.New project webhook events:
  • workflow.execution.handoff - Workflow handed off to human agent
  • workflow.execution.failed - Workflow execution failed
Configure in Project → Webhooks → Project webhooks. See webhook event types for payload structures.
Dec 5, 2025 - 18:00

API changes

New endpoint: GET /whatsapp/conversations/{id}/flow_executions - List workflow executions for a WhatsApp conversation. Filter by status and paginate with page/per_page.
{
  "data": [
    {
      "id": "uuid",
      "status": "running",
      "tracking_id": "uuid",
      "whatsapp_conversation_id": "uuid",
      "started_at": "2025-12-05T17:20:00Z",
      "last_event_at": "2025-12-05T17:25:00Z",
      "ended_at": null,
      "workflow": { "id": "uuid", "name": "Order Support", "status": "active" },
      "current_step": { "identifier": "wait_response", "stepable_type": "FlowWaitStep" }
    }
  ],
  "meta": { "page": 1, "per_page": 20, "total_pages": 1, "total_count": 1 }
}
Pagination update: Workflow execution list endpoints now include pagination in response body (meta object) in addition to headers.
Nov 30, 2025 - 15:00

Workflows

Agent steps: MCP server URLs and headers now support variable substitution:
https://api.example.com/mcp/{{system.customer.external_customer_id}}
Authorization: Bearer ${ENV:MCP_API_KEY}
Supported: {{vars.*}}, {{system.*}}, {{context.*}}, ${ENV:KEY}
Nov 29, 2025 - 17:00

Workflows

New system.customer context - WhatsApp-triggered workflows now automatically include customer data when the WhatsApp config is linked to a Customer:
{{system.customer.id}}                    # Customer UUID
{{system.customer.external_customer_id}}  # Your external ID
{{system.customer.name}}                  # Customer name
Nov 27, 2025 - 15:00

Webhooks

New fields in message.kapso:
  • content - LLM-ready text representation of any message type (includes caption, file info, and transcript for audio)
  • transcript - Speech-to-text transcription for audio messages with shape { text: "..." }
Nov 27, 2025 - 11:00

API changes

Workflow execution responses now include whatsapp_conversation_id to link executions to their WhatsApp conversation.
{
  "id": "uuid",
  "status": "running|waiting|completed|failed|stopped|handoff",
  "tracking_id": "custom-tracking-id",
  "whatsapp_conversation_id": "uuid",
  "started_at": "2025-11-27T10:00:00Z",
  "last_event_at": "2025-11-27T10:05:00Z",
  "ended_at": null,
  "workflow": {
    "id": "uuid",
    "name": "My Workflow"
  },
  "current_step": {
    "id": "uuid",
    "stepable_type": "FlowAgentStep"
  }
}
Available in list, show, and resume endpoints. You can also filter executions by whatsapp_conversation_id in the list endpoint.

Workflows

New features
  • Duplicate flows - Clone existing flows via the canvas UI
  • Wait step save_response_to - Save user response to a custom variable
  • Failure email notifications - Automatic alerts when flow executions fail
Fixes
  • Handle non-JSON webhook bodies in flow webhooks
  • Fix edge case where AI returns strings with backslash characters

Functions

Function logs - Debug your serverless functions with built-in logging. View logs filtered by invocation, time range, and request ID.

Billing & projects

  • Multiple projects - Create up to 6 projects
  • Free digital phone number - Free plan now includes a digital phone number

UI/UX

  • Mobile inbox - Improved mobile experience
  • Triggers UI - Improved design for workflow triggers