Botpress

Breadth through a published integration catalog with authenticated action. The Hub supplies installable integrations maintained by Botpress and by third parties, with HubSpot, Notion, Jira and Calendly named in the platform navigation and a full catalog behind it, and agents call those systems through action cards and an Execute Code card.

The vendor's own framing is that a resolution coordinates several systems in one motion, updating the record, triggering the next step and closing the loop, changing a plan or updating billing details. The Enterprise page states the platform is as flexible as code, with custom JavaScript injected to integrate business systems.

Sourcebotpress.com/hubread 2026-09-05

The Autonomous Node runs on LLMz, a versioned autonomous engine that decides which cards to execute and in what order, iterating until it reaches a final decision, while Standard Nodes hold deterministic paths, so one bot mixes reasoning-driven and rule-based execution across multiple workflows. Agents can be composed with a Vision Agent for image input and hand off to other agents or to a person mid-flow.

Sourcebotpress.com/docs/studio/introductionread 2026-09-05

A maintained retrieval structure the customer curates and scopes. Knowledge Bases are a named Studio object that define the information an agent can access, accepting websites crawled by the platform, documents, custom text and Tables, indexed automatically on ingest, with segmented data management so different bases serve different purposes and per-node toggling of which bases an autonomous node may use. A Search Knowledge card performs retrieval inside the node, a Knowledge Agent ships in the prebuilt agent library, and Botpress publishes guidance on optimizing files for retrieval.

Sourcebotpress.com/academy-lesson/studio-ui-knowledge-baseread 2026-09-05

Human Handoff is a first-class platform capability with its own place in the feature navigation and its own quickstart step, Configure Human Handoff, and a HITL Agent ships in the Studio's prebuilt agent library so escalation is a component a builder drops in rather than a pattern they assemble. A Policy Agent sits in the same library, constraining behavior against defined rules, and builder Instructions govern what the autonomous node may do, with published guidance on preventing fabricated answers. Access control over the agent is a documented quickstart step alongside it.

Sourcebotpress.com/docs/studio/get-started/manage-your-agent/edit-appearanceread 2026-09-05

SOC 2 certification and GDPR compliance are stated on the vendor's own site alongside third-party penetration testing by KPMG, with named customer-facing controls covering roles and role-based access, SSO, audit logs and workspace controls; a DPA is available from the Plus tier and a HIPAA BAA on Enterprise. The SOC 2 report type is not specified, and Botpress links a Trust Center from its site footer.

Sourcebotpress.comread 2026-09-05

Production surfaces are a Conversations tab holding conversation history, a Logs tab recording a deployed bot's activities, events, errors and actions with date filtering and custom console logging, and audit logs on the enterprise tier.

The reasoning-level view, which shows an Autonomous Node's input, output and iteration steps, lives in the Studio emulator, which explicitly does not save conversations, and Botpress's own production debugging guide recommends duplicating the bot and inserting text cards or log statements rather than reading a native trace. Iteration data reaches production only through a separate Improvement integration built for feedback.

Sourcebotpress.com/docs/debugging-bot-behavior-in-productionread 2026-09-05

The agent development kit documents a state layer with three declared scopes: bot state persisting across all users and conversations, user state persisting across all conversations for a given user, and conversation state for a single conversation, each defined as a typed schema in the agent config and read or written through the runtime. Any user or conversation can be loaded by id from anywhere in the agent to read and write its state and tags, so the store is addressable and separable per customer.

Sourcebotpress.com/docs/adk/conversations/stateread 2026-09-05

Custom data residency is listed on the Enterprise tier, but the hosting region for Botpress Cloud, and whether a buyer can choose it, is not stated. Self-hosting belongs to the older open-source v12 lineage rather than the current cloud platform and does not apply to Botpress Cloud. 2026-09-05

A vendor-supplied catalog plus a named agent library. The Hub carries production-ready templates for customer support, appointment scheduling and lead qualification, including a Kitchen Sink template demonstrating user data loading, workflow routing and live agent handoff, adopted by customizing instructions and swapping in a knowledge base. Alongside it the Studio documentation publishes a set of prebuilt Agents a builder drops into a bot: Summary, Personality, Policy, Translator, Knowledge, HITL, Vision and Analytics.

Sourcebotpress.com/hubread 2026-09-05

Channels are a first-class platform surface with its own navigation section, covering webchat, WhatsApp, Instagram, Messenger and Slack among others, with voice available through a maintained Twilio Voice integration that lets a bot take a phone call, and one build reaching all of them. The agent also initiates rather than only receiving: Triggers are a documented Studio concept, a Fixed Schedule card runs work on a timetable, and the documentation covers sending reminders into conversations.

Sourcebotpress.com/integrations/twilio-voiceread 2026-09-05

Default LLMs are set per bot in Bot Settings and can be overridden on an individual Autonomous Node through advanced settings, separately for response generation and for the RAG model used against knowledge bases, with the LLMz autonomous engine versioned independently and described as written to stay agnostic to variance between models.

Sourcebotpress.com/docs/studio/concepts/bot-settingsread 2026-09-05

The platform is callable from outside and extensible in code through several documented surfaces: a public API Reference in the top-level navigation, a Botpress Cloud API, an Agent Development Kit published as its own documentation set alongside Studio, Integrations, Desk and Webchat, Hooks for custom code, an Execute Code card inside the autonomous node, and Import and Export for moving bots programmatically. Botpress also publishes first-party Model Context Protocol material tying MCP tool access to the Autonomous Node.

Sourcebotpress.com/docs/studio/get-started/manage-your-agent/edit-appearanceread 2026-09-05

The Emulator supports real-time conversation testing with an inspect window exposing an Autonomous Node's input, output and iteration steps, alongside an Event Debugger, version history and an Improvement integration that collects feedback on production iterations. These are manual inspect-and-fix loops; no test suite, regression harness, scored evaluation or pass rate is documented, and the emulator neither saves conversations nor counts toward usage, so there is nothing to compare runs against.

Sourcebotpress.com/academy-lesson/studio-ui-emulatorread 2026-09-05

Botpress offers no browser control, hosted session or computer use in the platform or its documentation. The route out is stated positively and it is programmatic: agents act through Hub integrations, action cards, an Execute Code card and API calls, and reach people through channel surfaces. A Vision Agent ships in the prebuilt agent library, which reads images rather than operating an interface.

Sourcebotpress.com/hubread 2026-09-05