Channels & Integrations
A channel is a communication surface CraftBot uses to send and receive messages. Today, the platform ships with WhatsApp Cloud API direct integration — no BSP (Business Solution Provider) middleman required.
Supported channels
| Channel | Status |
|---|---|
| WhatsApp Cloud API (Meta-direct) | ✅ GA |
| Outbound email (M365 / Gmail / Generic SMTP) | ✅ GA |
| Web widget | 🔜 Roadmap |
| Mobile SDK | 🔜 Roadmap |
| Provider-agnostic BSP (Twilio, Infobip, 360dialog) | 🔒 Blocked on BSP selection |
Architecture
CraftBot uses a ChannelAdapter abstraction. Each supported channel implements the same contract:
- Inbound: webhook receiver normalises the channel-specific payload into CraftBot’s canonical message format.
- Outbound: send-message API translates canonical messages back to the channel’s wire format.
- Templates: HSM template management (where the channel supports it).
- Status callbacks: delivery / read receipts pushed back to the conversation timeline.
This means recipes, the inbox, and analytics are channel-agnostic — they speak only the canonical format.
Pages in this section
- WhatsApp Cloud API — provisioning, configuration, and operating a WhatsApp number.
- Webhook setup — verifying the webhook endpoint with Meta.
- Message templates — HSM templates: design, submission, approval, and use.
- Email servers — outbound mailboxes for auth, notifications, and report delivery.
Last updated on