Connect your systems to conversations and events
QualiBot exposes application, platform, public and widget APIs alongside webhooks and access tokens, so technical teams can build connected customer operations around real conversation data.
Application, platform, public and widget surfaces
Every surface below is available to technical teams building a channel, connector or workflow around QualiBot.
Six principles for deciding where an integration belongs
Use the QualiBot API for platform objects
Conversations, contacts, teams and account configuration.
Use webhooks for events
Get notified the moment something changes, without polling.
Use custom HTTP tools for simple GET or POST actions
A single request-response call Brain can make during a conversation.
Use MCP when Brain needs a reusable toolset or file relay
A discoverable set of tools shared across conversations, with image or PDF delivery.
Use a custom channel when the source is a communication surface
Build an API inbox for a proprietary app or channel.
Keep sensitive system logic outside the model prompt
Authentication, credentials and business rules stay in your API, webhook handler or middleware layer.
Notify your systems the moment something changes
A webhook fires from the same event types that can trigger an automation rule:
Call a webhook as an automation action, or build your own event-driven integration around these conversation events.
Custom channels and custom HTTP tools
Custom channels
Create an API inbox and use the same API and webhook model to connect a proprietary app or communication channel. Attachments move through the same shared message pipeline used by every native channel.
Custom HTTP tools
GET and POST requests, bearer, basic and API-key authentication, Liquid-templated URLs and request bodies, response templating and safe HTTPS calls — configured once and available account-wide.
Before you integrate
Is there a limit on API requests?
The API is built for standard integration and automation workloads — talk to our team to confirm the right approach for your expected request volume.
Should I use the API or build a custom channel?
Use the Application and Platform APIs for conversation, contact and account objects. A custom channel is the right approach only when the source is itself a communication surface your customers use directly.
Can webhooks and MCP tools work together?
Yes — webhooks notify your systems of conversation events, while MCP or custom HTTP tools let Brain call your systems from inside the conversation itself.
Where should sensitive logic live?
Outside the model prompt. Keep authentication, credentials and business rules in your API, webhook handler or middleware layer, not inside Brain's instructions.
Build against one stable customer workflow first
Tell us the object, the event or the action you need, and we'll map it to the right API, webhook, custom tool or MCP connector.