Overview
Distribution Channels define where and how your AI assistants are deployed. Each channel type has specific metadata and configuration options that control its behavior and integration.Metadata Structure
When creating or updating a distribution channel (assistant), include thedistributionChannel object in the metadata field:
Channel Types
Chat
Integration with B-Bot Chat AppprofileImage: URL to assistant profile pictureabilities: Array of ability objects/stringstemplates: Array of template objects/stringsdescription: Assistant description shown in chat
Embed
Embeddable widget for websites and appsprofileImage: URL to assistant profile picturebubbleIcon: URL to custom chat bubble icon (optional, uses default if not set)headerIcon: Lucide icon name for embed headerabilities: Array of ability objects/stringstemplates: Array of template objects/stringsdescription: Assistant description shown in embed
API
Direct integration via REST API endpointsTasks
Internal task distribution system- When created, the assistant ID is automatically linked to the expert’s
task_assistant_idfield - Used for automated task routing and execution within the B-Bot ecosystem
Template
Share as public expert template for others to installcategory: Template category (see categories below)featured: Request featured status (requires admin approval)usage_count: Number of times template has been installed (auto-managed)
- Sales & Marketing
- Customer Support
- Development
- Finance & Accounting
- HR & Recruitment
- Content Creation
- Project Management
- Data Analysis
- Education
- Other
- App credentials are removed when template is shared
- Users must connect their own app credentials when installing
- Knowledge containers are copied to the installing user’s expert
Coming Soon
The following channel types are planned for future releases: Twilio - SMS and messaging integrationComplete Example
Here’s a complete example of creating a Chat distribution channel with all metadata:Filtering by Distribution Channel
When fetching distribution channels via the public endpoints, the API automatically filters assistants based on theirdistributionChannel.type metadata:
Included Types: Chat, Embed, Template
Assistants without a distributionChannel metadata field will not be included in public endpoints. This ensures legacy assistants don’t automatically appear in public-facing applications.
Best Practices
- Always specify a distribution channel type when creating new assistants intended for public use
- Use meaningful categories for Template channels to help users discover your expert
- Include profile images and descriptions for Chat and Embed channels to provide better user experience
- Test embed customizations (bubbleIcon, headerIcon) before deploying to production
- Request featured status carefully - only for high-quality, well-tested templates