Skip to content
ChatfuelSDK
Get started

Chatfuel runs on its own SDK

The company that makes the SDK is its first customer. Parts of the new Chatfuel dashboard are built from the modules the wizard installs, and a separate Chatfuel app the wizard scaffolded runs deployed.

Get startedVisit chatfuel.com

The platform underneath

Chatfuel is an official Meta Partner and a WhatsApp Business Solution Provider. Every scaffolded app runs on the same infrastructure these numbers run through.

2015
Founded
7M+
Businesses since 2015
1B+
Messages sent monthly
150,000+
Businesses running today

How the SDK came out of the product

  1. 01

    It began as the product, not an SDK

    Chatfuel spent a decade building its bot platform — the channels, the API, the infrastructure under a billion messages a month. None of it was written to be shared.

  2. 02

    The new dashboard was built as modules

    Rebuilding the dashboard meant rebuilding its surfaces — inbox, CRM, flows, knowledge base — as self-contained React modules over the production GraphQL schema. Parts of the new dashboard are those modules, running in the product today.

  3. 03

    A module that clean does not care whose app it is in

    Each module needs the schema, a token and a place to render — nothing that belongs to Chatfuel alone. What the company assembled for itself, any team could assemble for themselves.

  4. 04

    So the modules became the SDK

    The wizard writes the same module trees into an app of your own, wired to your bot on the same infrastructure. Nothing was rewritten for the public version, and nothing is held back — the repository is MIT.

  5. 05

    Chatfuel runs the path it ships

    A separate Chatfuel app scaffolded by the wizard runs deployed, the way yours will be. The first customer of the SDK was the company that built it.

The modules, surface for surface

The label is where it lives in Chatfuel; the description is the module you install. Two are additions of the SDK — the product does not need them, your deployment does.

NameIn the SDK
In the dashboard
Automations tabThe AI Agent module: how the bot behaves, configured per scope — the same tab, setting for setting.
FlowsThe Flow Builder module: flows, blocks on the canvas, every element type.
Knowledge base pageThe Knowledge Base module: the sources the AI answers from, managed the way the product page manages them.
CoworkerThe Copilot module: the AI assistant the bot builder chats with, behind a manual-approval gate.
Live chatThe Inbox module: the conversation list, the thread, take-over and close-to-flow, live.
ContactsThe Contacts module: the bot’s contact directory and the CRM built on it.
DealsThe Deals module: board, table and forecast over the sales stage.
BookingsThe Bookings module: calendar, appointments, staff and services over the same bookings.
Instagram publishingThe Publishing module: feed posts, Reels, Stories and carousels to the connected account.
Ads optimizationThe Ads Optimization module: conversion events from click-to-WhatsApp ads, reported back to Meta.
Additions of the SDK
AccountsYour customers sign up to you, and every account gets a bot of its own.
AdminWorkspaces and bots from inside the app, behind a password.

What holds the claim up

The dashboard’s schema, commit for commit

The SDK bundles the schema the Chatfuel dashboard runs on. When the product moves, the SDK refreshes from it.

One design system with chatfuel.com

The design tokens carry the same values as Chatfuel’s own site. A scaffolded app and the platform read as one product.

The same token boundary

A Chatfuel token can read and change every bot in an account, so it never reaches the browser. The proxy that enforces this is part of every app the wizard writes — Chatfuel’s own included.

MIT, in the open

The modules, the schema and the wizard are public in one MIT repository. What Chatfuel builds on, you can read.

Build on the platform Chatfuel builds on

npx @chatfuel/wizard
Get startedRead the source